From: patchwork-bot+netdevbpf@kernel.org
To: Paritosh Dixit <paritoshd@nvidia.com>
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,
thierry.reding@gmail.com, jonathanh@nvidia.com,
vbhadram@nvidia.com, ruppala@nvidia.com, netdev@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH V2] net: stmmac: dwmac-tegra: Fix link bring-up sequence
Date: Tue, 15 Oct 2024 10:50:31 +0000 [thread overview]
Message-ID: <172898943126.1114309.13560475408965156147.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241010142908.602712-1-paritoshd@nvidia.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Thu, 10 Oct 2024 10:29:08 -0400 you wrote:
> The Tegra MGBE driver sometimes fails to initialize, reporting the
> following error, and as a result, it is unable to acquire an IP
> address with DHCP:
>
> tegra-mgbe 6800000.ethernet: timeout waiting for link to become ready
>
> As per the recommendation from the Tegra hardware design team, fix this
> issue by:
> - clearing the PHY_RDY bit before setting the CDR_RESET bit and then
> setting PHY_RDY bit before clearing CDR_RESET bit. This ensures valid
> data is present at UPHY RX inputs before starting the CDR lock.
> - adding the required delays when bringing up the UPHY lane. Note we
> need to use delays here because there is no alternative, such as
> polling, for these cases. Using the usleep_range() instead of ndelay()
> as sleeping is preferred over busy wait loop.
>
> [...]
Here is the summary with links:
- [V2] net: stmmac: dwmac-tegra: Fix link bring-up sequence
https://git.kernel.org/netdev/net/c/1cff6ff302f5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-10-15 10:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 14:29 [PATCH V2] net: stmmac: dwmac-tegra: Fix link bring-up sequence Paritosh Dixit
2024-10-15 10:50 ` patchwork-bot+netdevbpf [this message]
2024-10-15 11:06 ` Jon Hunter
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=172898943126.1114309.13560475408965156147.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=joabreu@synopsys.com \
--cc=jonathanh@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paritoshd@nvidia.com \
--cc=ruppala@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=vbhadram@nvidia.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).