[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220313024646.GC29538@hoboy.vegasvil.org>
Date: Sat, 12 Mar 2022 18:46:46 -0800
From: Richard Cochran <richardcochran@...il.com>
To: Andrew Lunn <andrew@...n.ch>
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
On Sat, Mar 12, 2022 at 09:04:31PM +0100, Andrew Lunn wrote:
> Do these get passed to the kernel so the hardware can act on them, or
> are they used purely in userspace by ptp4l?
user space only.
> 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?
Any hard coded defaults in the kernel are a nuisance.
I mean, do you want user space to say,
"okay, so I know the correct value is X. But the drivers may offer
random values according to kernel version. So, I'll read out the
driver value Y, and then apply X-Y."
Insanity.
(not to mention that this fails for older kernels without the proposed
interface)
Thanks,
Richard
Powered by blists - more mailing lists