From: Jon Hunter <jonathanh@nvidia.com>
To: Revanth Kumar Uppala <ruppala@nvidia.com>, f.fainelli@gmail.com
Cc: andrew@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, linux-tegra@vger.kernel.org,
linux@armlinux.org.uk, netdev@vger.kernel.org, olteanv@gmail.com,
pabeni@redhat.com, thierry.reding@gmail.com, vbhadram@nvidia.com,
Thierry Reding <treding@nvidia.com>
Subject: Re: [PATCH 2/2] net: stmmac: tegra: Add MGBE support
Date: Fri, 18 Nov 2022 09:28:38 +0000 [thread overview]
Message-ID: <662fd424-7f9a-eba1-a223-902e8e463021@nvidia.com> (raw)
In-Reply-To: <20221118075744.49442-2-ruppala@nvidia.com>
On 18/11/2022 07:57, Revanth Kumar Uppala wrote:
> From: Bhadram Varka <vbhadram@nvidia.com>
>
> Add support for the Multi-Gigabit Ethernet (MGBE/XPCS) IP found on
> NVIDIA Tegra234 SoCs.
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> Signed-off-by: Bhadram Varka <vbhadram@nvidia.com>
> Co-developed-by: Revanth Kumar Uppala <ruppala@nvidia.com>
> Signed-off-by: Revanth Kumar Uppala <ruppala@nvidia.com>
> ---
This should have been marked as 'V5'. If we need to resend please let us
know. We are also missing what has been changed since the last version.
I know that in this version the following changes were made:
1. Reduce time spent polling for the RX link to be ready
2. Propagate the errors when bringing up the link fails.
3. Added suspend/resume support
4. Ensure clocks are disabled again on probe/resume failure
Otherwise ...
Reviewed-by: Jon Hunter <jonathanh@nvidia.com>
Tested-by: Jon Hunter <jonathanh@nvidia.com>
Thanks
Jon
--
nvpublic
next prev parent reply other threads:[~2022-11-18 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 7:57 [PATCH 1/2] net: stmmac: Power up SERDES after the PHY link Revanth Kumar Uppala
2022-11-18 7:57 ` [PATCH 2/2] net: stmmac: tegra: Add MGBE support Revanth Kumar Uppala
2022-11-18 9:28 ` Jon Hunter [this message]
2022-11-22 9:58 ` Paolo Abeni
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=662fd424-7f9a-eba1-a223-902e8e463021@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=ruppala@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=treding@nvidia.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