[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cc6e3f7c-1a64-4a9d-8389-0b3e58120481@kernel.org>
Date: Wed, 27 Aug 2025 14:15:05 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Wei Fang <wei.fang@....com>, robh@...nel.org, krzk+dt@...nel.org,
conor+dt@...nel.org, richardcochran@...il.com, claudiu.manoil@....com,
vladimir.oltean@....com, xiaoning.wang@....com, andrew+netdev@...n.ch,
davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, vadim.fedorenko@...ux.dev, Frank.Li@....com,
shawnguo@...nel.org
Cc: fushi.peng@....com, devicetree@...r.kernel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, imx@...ts.linux.dev
Subject: Re: [PATCH v6 net-next 01/17] dt-bindings: ptp: add NETC Timer PTP
clock
On 27/08/2025 08:33, Wei Fang wrote:
> NXP NETC (Ethernet Controller) is a multi-function PCIe Root Complex
> Integrated Endpoint (RCiEP), the Timer is one of its functions which
> provides current time with nanosecond resolution, precise periodic
> pulse, pulse on timeout (alarm), and time capture on external pulse
> support. And also supports time synchronization as required for IEEE
> 1588 and IEEE 802.1AS-2020. So add device tree binding doc for the PTP
> clock based on NETC Timer.
>
> NETC Timer has three reference clock sources, but the clock mux is inside
> the IP. Therefore, the driver will parse the clock name to select the
> desired clock source. If the clocks property is not present, NETC Timer
> will use the system clock of NETC IP as its reference clock. Because the
> Timer is a PCIe function of NETC IP, the system clock of NETC is always
> available to the Timer.
>
> Signed-off-by: Wei Fang <wei.fang@....com>
> Reviewed-by: Frank Li <Frank.Li@....com>
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Best regards,
Krzysztof
Powered by blists - more mailing lists