From: Jon Hunter <jonathanh@nvidia.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>
Cc: netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH V3 2/3] dt-bindings: net: Fix Tegra234 MGBE PTP clock
Date: Wed, 25 Mar 2026 14:26:16 +0000 [thread overview]
Message-ID: <188ef2a5-cd3d-4fde-943a-17d805d79ac1@nvidia.com> (raw)
In-Reply-To: <5a0d431e-785c-4aef-8282-2a921865bb9e@kernel.org>
On 25/03/2026 14:09, Krzysztof Kozlowski wrote:
> On 25/03/2026 15:07, Krzysztof Kozlowski wrote:
>> On 25/03/2026 14:58, Jon Hunter wrote:
>>> The PTP clock for the Tegra234 MGBE device is incorrectly named
>>> 'ptp-ref' and should be 'ptp_ref'. This is causing the following
>>> warning to be observed on Tegra234 platforms that use this device:
>
> ^^^^^^^^^^^^^ Tegra234 (see further)
>>>
>>> ERR KERN tegra-mgbe 6800000.ethernet eth0: Invalid PTP clock rate
>>> WARNING KERN tegra-mgbe 6800000.ethernet eth0: PTP init failed
>>>
>>> Although this constitutes an ABI breakage in the binding for this
>>> device, PTP support has clearly never worked and so fix this now
>>> so we can correct the device-tree for this device. Note that the
>>
>> I don't understand that explanation.
>>
>> Driver dwmac-tegra.c: ptp-ref
>> Binding: ptp-ref
>> DTS: ptp-ref
>>
>> but you say that nothing was working correctly?
>>
>> Judging by these three - driver+binding+dts - obvious fix is no fix
>> because everything was fine, so please clarify the exact problem.
>
> Correction - I missed in grep - there are ptp_ref users: tegra186 and
> tegra194, but how tegra234 could not work if it has correctly in DTS
> ptp-ref?
The problem lies in
drivers/net/ethernet/stmicro/stmmac/stmmac_platform.c which uses the
name 'ptp_ref' which does not match 'ptp-ref'. This is where the warning
is coming from. So basic ethernet does work, but stmmac_platform.c
driver is complaining that the PTP clock is not found.
Yes Tegra186 and Tegra194 are not impacted by this, only Tegra234.
Jon
--
nvpublic
next prev parent reply other threads:[~2026-03-25 14:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 13:58 [PATCH V3 0/3] net: stmmac: Fix Tegra234 MGBE clock Jon Hunter
2026-03-25 13:58 ` [PATCH V3 1/3] net: stmmac: Fix PTP ref clock for Tegra234 Jon Hunter
2026-03-26 8:32 ` Krzysztof Kozlowski
2026-03-25 13:58 ` [PATCH V3 2/3] dt-bindings: net: Fix Tegra234 MGBE PTP clock Jon Hunter
2026-03-25 14:07 ` Krzysztof Kozlowski
2026-03-25 14:09 ` Krzysztof Kozlowski
2026-03-25 14:26 ` Jon Hunter [this message]
2026-03-26 8:30 ` Krzysztof Kozlowski
2026-03-25 13:58 ` [PATCH V3 3/3] arm64: tegra: " Jon Hunter
2026-03-26 8:30 ` Krzysztof Kozlowski
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=188ef2a5-cd3d-4fde-943a-17d805d79ac1@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.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