[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y1KVka41Kza3IOXx@hoboy.vegasvil.org>
Date: Fri, 21 Oct 2022 05:50:26 -0700
From: Richard Cochran <richardcochran@...il.com>
To: Sarath Babu Naidu Gaddam <sarath.babu.naidu.gaddam@....com>
Cc: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, netdev@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
yangbo.lu@....com, radhey.shyam.pandey@....com,
anirudha.sarangi@....com, harini.katakam@....com, git@....com
Subject: Re: [PATCH net-next V2] dt-bindings: net: ethernet-controller: Add
ptp-hardware-clock
On Thu, Oct 20, 2022 at 11:41:10PM -0600, Sarath Babu Naidu Gaddam wrote:
> There is currently no standard property to pass PTP device index
> information to ethernet driver when they are independent.
>
> ptp-hardware-clock property will contain phandle to PTP clock node.
>
> Freescale driver currently has this implementation but it will be
> good to agree on a generic (optional) property name to link to PTP
> phandle to Ethernet node. In future or any current ethernet driver
> wants to use this method of reading the PHC index,they can simply use
> this generic name and point their own PTP clock node, instead of
> creating separate property names in each ethernet driver DT node.
>
> axiethernet driver uses this method when PTP support is integrated.
>
> Example:
> fman0: fman@...0000 {
> ptp-hardware-clock = <&ptp_timer0>;
> }
>
> ptp_timer0: ptp-timer@...e000 {
> compatible = "fsl,fman-ptp-timer";
> reg = <0x0 0x1afe000 0x0 0x1000>;
> }
>
> Signed-off-by: Sarath Babu Naidu Gaddam <sarath.babu.naidu.gaddam@....com>
Acked-by: Richard Cochran <richardcochran@...il.com>
Powered by blists - more mailing lists