linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Bernd Edlinger <bernd.edlinger@hotmail.de>
Cc: alexandre.torgue@foss.st.com, joabreu@synopsys.com,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, 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, jiri@nvidia.com,
	akpm@linux-foundation.org, fancer.lancer@gmail.com
Subject: Re: [PATCH net v3] net: stmmac: Wait a bit for the reset to take effect
Date: Wed, 24 Jan 2024 20:30:26 +0000	[thread overview]
Message-ID: <170612822646.416.13224306306608084186.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <AS8P193MB1285A810BD78C111E7F6AA34E4752@AS8P193MB1285.EURP193.PROD.OUTLOOK.COM>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Mon, 22 Jan 2024 19:19:09 +0100 you 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?
> 
> [...]

Here is the summary with links:
  - [net,v3] net: stmmac: Wait a bit for the reset to take effect
    https://git.kernel.org/netdev/net/c/a5f5eee282a0

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      parent reply	other threads:[~2024-01-24 20:30 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
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 [this message]

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=170612822646.416.13224306306608084186.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --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=fancer.lancer@gmail.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 \
    --cc=pabeni@redhat.com \
    /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).