From: Thierry Reding <thierry.reding@gmail.com>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
Peter Robinson <pbrobinson@redhat.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] arm64: tegra: Fix ethernet phy-mode for Jetson Xavier
Date: Wed, 6 May 2020 01:12:05 +0200 [thread overview]
Message-ID: <20200505231205.GA2682073@ulmo> (raw)
In-Reply-To: <20200501072756.25348-1-jonathanh@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 951 bytes --]
On Fri, May 01, 2020 at 08:27:56AM +0100, Jon Hunter wrote:
> The 'phy-mode' property is currently defined as 'rgmii' for Jetson
> Xavier. This indicates that the RGMII RX and TX delays are set by the
> MAC and the internal delays set by the PHY are not used.
>
> If the Marvell PHY driver is enabled, such that it is used and not the
> generic PHY, ethernet failures are seen (DHCP is failing to obtain an
> IP address) and this is caused because the Marvell PHY driver is
> disabling the internal RX and TX delays. For Jetson Xavier the internal
> PHY RX and TX delay should be used and so fix this by setting the
> 'phy-mode' to 'rgmii-id' and not 'rgmii'.
>
> Cc: stable@vger.kernel.org
>
> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
> ---
> arch/arm64/boot/dts/nvidia/tegra194-p2888.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Added a Fixes: tag and applied to for-5.8/arm64/dt, thanks.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-05-05 23:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 7:27 [PATCH] arm64: tegra: Fix ethernet phy-mode for Jetson Xavier Jon Hunter
2020-05-05 23:12 ` Thierry Reding [this message]
2020-05-06 23:42 ` Sasha Levin
2020-05-07 10:05 ` Thierry Reding
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=20200505231205.GA2682073@ulmo \
--to=thierry.reding@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-tegra@vger.kernel.org \
--cc=pbrobinson@redhat.com \
--cc=stable@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).