public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: "Rob Herring (Arm)" <robh@kernel.org>
Cc: Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Paolo Abeni <pabeni@redhat.com>,
	Thierry Reding <thierry.reding@gmail.com>,
	"David S . Miller" <davem@davemloft.net>,
	netdev@vger.kernel.org, devicetree@vger.kernel.org,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	linux-tegra@vger.kernel.org
Subject: Re: [PATCH V2 2/3] dt-bindings: net: Fix Tegra234 MGBE PTP clock
Date: Wed, 25 Mar 2026 06:18:07 +0000	[thread overview]
Message-ID: <5e0a6a5a-dded-449d-8789-e2a5e0a169e8@nvidia.com> (raw)
In-Reply-To: <177439307874.2078673.11304788250514370726.robh@kernel.org>


On 24/03/2026 22:57, Rob Herring (Arm) wrote:
> 
> On Tue, 24 Mar 2026 12:16:30 +0000, 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:
>>
>>   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
>> MGBE driver still supports the legacy 'ptp-ref' clock name and so
>> older/existing device-trees will still work, but given that this
>> is not the correct name, there is no point to advertise this in the
>> binding.
>>
>> Fixes: 189c2e5c7669 ("dt-bindings: net: Add Tegra234 MGBE")
>> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
>> ---
>>   Documentation/devicetree/bindings/net/nvidia,tegra234-mgbe.yaml | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
> 
> My bot found errors running 'make dt_binding_check' on your patch:
> 
> yamllint warnings/errors:
> 
> dtschema/dtc warnings/errors:
> /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/net/nvidia,tegra234-mgbe.example.dtb: ethernet@6800000 (nvidia,tegra234-mgbe): clock-names:3: 'ptp_ref' was expected
> 	from schema $id: http://devicetree.org/schemas/net/nvidia,tegra234-mgbe.yaml

Yes this is expected until patch 3/3 is applied.

Jon

-- 
nvpublic


  reply	other threads:[~2026-03-25  6:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-24 12:16 [PATCH V2 0/3] net: stmmac: Fix Tegra234 MGBE clock Jon Hunter
2026-03-24 12:16 ` [PATCH V2 1/3] net: stmmac: Fix PTP ref clock for Tegra234 Jon Hunter
2026-03-24 12:16 ` [PATCH V2 2/3] dt-bindings: net: Fix Tegra234 MGBE PTP clock Jon Hunter
2026-03-24 22:57   ` Rob Herring (Arm)
2026-03-25  6:18     ` Jon Hunter [this message]
2026-03-25 13:41       ` Jon Hunter
2026-03-24 12:16 ` [PATCH V2 3/3] arm64: tegra: " 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=5e0a6a5a-dded-449d-8789-e2a5e0a169e8@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=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