[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yiz8z3UPqNANa5zA@lunn.ch>
Date: Sat, 12 Mar 2022 21:04:31 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Richard Cochran <richardcochran@...il.com>
Cc: Woojung.Huh@...rochip.com, linux@...linux.org.uk,
Horatiu.Vultur@...rochip.com, Divya.Koppera@...rochip.com,
netdev@...r.kernel.org, hkallweit1@...il.com, davem@...emloft.net,
kuba@...nel.org, robh+dt@...nel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, UNGLinuxDriver@...rochip.com,
Madhuri.Sripada@...rochip.com, Manohar.Puri@...rochip.com
Subject: Re: [PATCH net-next 2/3] dt-bindings: net: micrel: Configure latency
values and timestamping check for LAN8814 phy
> PTP4l(8) System Manager's Manual PTP4l(8)
>
> NAME
> ptp4l - PTP Boundary/Ordinary/Transparent Clock
>
> ...
>
> egressLatency
> Specifies the difference in nanoseconds between the actual
> transmission time at the reference plane and the reported trans‐
> mit time stamp. This value will be added to egress time stamps
> obtained from the hardware. The default is 0.
>
> ingressLatency
> Specifies the difference in nanoseconds between the reported re‐
> ceive time stamp and the actual reception time at reference
> plane. This value will be subtracted from ingress time stamps
> obtained from the hardware. The default is 0.
>
Hi Richard
Do these get passed to the kernel so the hardware can act on them, or
are they used purely in userspace by ptp4l?
If they has passed to the kernel, could we provide a getter as well as
a setter, so the defaults hard coded in the driver can be read back?
Andrew
Powered by blists - more mailing lists