From: Paolo Abeni <pabeni@redhat.com>
To: Bernd Edlinger <bernd.edlinger@hotmail.de>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Jose Abreu <joabreu@synopsys.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jiri Pirko <jiri@nvidia.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v2] net: stmmac: Wait a bit for the reset to take effect
Date: Tue, 16 Jan 2024 13:22:26 +0100 [thread overview]
Message-ID: <f5ddf800df95cdce32637d41bc1539aed0a7b6f3.camel@redhat.com> (raw)
In-Reply-To: <AS8P193MB1285EEAFE30C0DE7B201D33CE46C2@AS8P193MB1285.EURP193.PROD.OUTLOOK.COM>
On Mon, 2024-01-15 at 20:21 +0100, Bernd Edlinger wrote:
> otherwise the synopsys_id value may be read out wrong,
> because the GMAC_VERSION register might still be in reset
> state, for at least 1 us after the reset is de-asserted.
>
> Add a wait for 10 us before continuing to be on the safe side.
>
> > From what have you got that delay value?
>
> Just try and error, with very old linux versions and old gcc versions
> the synopsys_id was read out correctly most of the time (but not always),
> with recent linux versions and recnet gcc versions it was read out
> wrongly most of the time, but again not always.
> I don't have access to the VHDL code in question, so I cannot
> tell why it takes so long to get the correct values, I also do not
> have more than a few hardware samples, so I cannot tell how long
> this timeout must be in worst case.
> Experimentally I can tell that the register is read several times
> as zero immediately after the reset is de-asserted, also adding several
> no-ops is not enough, adding a printk is enough, also udelay(1) seems to
> be enough but I tried that not very often, and I have not access to many
> hardware samples to be 100% sure about the necessary delay.
> And since the udelay here is only executed once per device instance,
> it seems acceptable to delay the boot for 10 us.
>
> BTW: my hardware's synopsys id is 0x37.
>
> Signed-off-by: Bernd Edlinger <bernd.edlinger@hotmail.de>
>
> Reviewed-by: Jiri Pirko <jiri@nvidia.com>
Please have a better look at the process documentation.
No empty lines are allowed in the tag area.
A fixes tag is requires, something alike:
Fixes: <blamed commit hash> ("<blamed commit title>")
A bisection is not strictly required, you just need to be reasonably
confident about the the culprit.
You need to include the relevant target tree into the subj prefix (in
this case 'net').
Please include in the recipients list the persons that provided
feedback on previous release (Serge is missing).
I'm unsure why/how Andrew landed in the recipients list!?!
Cheers,
Paolo
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-01-16 12:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 6:01 [PATCH] net: stmmac: Wait a bit for the reset to take effect Bernd Edlinger
2023-10-30 11:55 ` Jiri Pirko
2023-10-31 10:32 ` Serge Semin
2023-10-31 16:10 ` Bernd Edlinger
2023-11-02 12:03 ` Serge Semin
2023-11-02 11:25 ` Paolo Abeni
2023-11-03 10:45 ` Bernd Edlinger
2024-01-15 19:21 ` [PATCH v2] " Bernd Edlinger
2024-01-16 12:22 ` Paolo Abeni [this message]
2024-01-17 16:36 ` Bernd Edlinger
2024-01-19 10:27 ` Bernd Edlinger
2024-01-19 11:42 ` Paolo Abeni
2024-01-16 22:35 ` Andrew Lunn
2024-01-17 16:48 ` Bernd Edlinger
2024-01-17 16:55 ` Jose Abreu
2024-01-19 7:15 ` Bernd Edlinger
2024-01-19 10:38 ` Jose Abreu
2024-01-22 6:41 ` Bernd Edlinger
2024-01-22 15:44 ` Jose Abreu
2024-01-22 18:19 ` [PATCH net v3] " Bernd Edlinger
2024-01-24 13:31 ` Serge Semin
2024-01-24 20:30 ` patchwork-bot+netdevbpf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f5ddf800df95cdce32637d41bc1539aed0a7b6f3.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alexandre.torgue@foss.st.com \
--cc=bernd.edlinger@hotmail.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jiri@nvidia.com \
--cc=joabreu@synopsys.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).