From: Andrew Lunn <andrew@lunn.ch>
To: Richard Cochran <richardcochran@gmail.com>
Cc: Woojung.Huh@microchip.com, linux@armlinux.org.uk,
Horatiu.Vultur@microchip.com, Divya.Koppera@microchip.com,
netdev@vger.kernel.org, hkallweit1@gmail.com,
davem@davemloft.net, kuba@kernel.org, robh+dt@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
UNGLinuxDriver@microchip.com, Madhuri.Sripada@microchip.com,
Manohar.Puri@microchip.com
Subject: Re: [PATCH net-next 2/3] dt-bindings: net: micrel: Configure latency values and timestamping check for LAN8814 phy
Date: Sun, 13 Mar 2022 16:07:24 +0100 [thread overview]
Message-ID: <Yi4IrO4Qcm1KVMaa@lunn.ch> (raw)
In-Reply-To: <20220313024646.GC29538@hoboy.vegasvil.org>
On Sat, Mar 12, 2022 at 06:46:46PM -0800, Richard Cochran wrote:
> 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.
No, i would not suggests that at all.
You quoted the man page and it says the default it zero. If there was
an API to ask the driver what correction it is doing, and an API to
offload the delay correction to the hardware, i would simply remove
the comment about the default being zero. If these calls return
-EOPNOTSUPP, then user space stays the same, and does actually use a
default of 0. If offload is supported, you can show the user the
current absolute values, and allow the user to set the absolute
values.
Anyway, it is clear you don't want the driver doing any correction, so
lets stop this discussion.
Andrew
next prev parent reply other threads:[~2022-03-13 15:07 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 9:34 [PATCH net-next 0/3] Add support for 1588 in LAN8814 Divya Koppera
2022-03-04 9:34 ` [PATCH net-next 1/3] net: phy: micrel: Fix concurrent register access Divya Koppera
2022-03-04 9:34 ` [PATCH net-next 2/3] dt-bindings: net: micrel: Configure latency values and timestamping check for LAN8814 phy Divya Koppera
2022-03-04 12:50 ` Andrew Lunn
2022-03-04 13:55 ` Richard Cochran
2022-03-07 5:02 ` Divya.Koppera
2022-03-07 4:40 ` Divya.Koppera
2022-03-07 13:08 ` Andrew Lunn
2022-03-08 10:05 ` Divya.Koppera
2022-03-08 13:54 ` Andrew Lunn
2022-03-08 14:54 ` Richard Cochran
2022-03-08 15:43 ` Horatiu Vultur
2022-03-08 18:10 ` Andrew Lunn
2022-03-08 22:14 ` Horatiu Vultur
2022-03-08 23:36 ` Andrew Lunn
2022-03-09 1:46 ` Richard Cochran
2022-03-09 1:58 ` Richard Cochran
2022-03-09 13:24 ` Horatiu Vultur
2022-03-09 14:55 ` Russell King (Oracle)
2022-03-09 19:52 ` Richard Cochran
2022-03-11 14:28 ` Horatiu Vultur
2022-03-11 15:08 ` Richard Cochran
2022-03-12 19:36 ` Allan W. Nielsen
2022-03-13 2:41 ` Richard Cochran
2022-03-13 4:04 ` Richard Cochran
2022-03-11 15:21 ` Woojung.Huh
2022-03-12 2:48 ` Richard Cochran
2022-03-12 20:04 ` Andrew Lunn
2022-03-13 2:46 ` Richard Cochran
2022-03-13 15:07 ` Andrew Lunn [this message]
2022-03-13 19:37 ` Allan W. Nielsen
2022-03-13 20:03 ` Richard Cochran
2022-03-13 20:07 ` Richard Cochran
2022-03-11 14:07 ` Horatiu Vultur
2022-03-07 21:33 ` Rob Herring
2022-03-04 9:34 ` [PATCH net-next 3/3] net: phy: micrel: 1588 support " Divya Koppera
2022-03-04 13:06 ` Andrew Lunn
2022-03-07 4:58 ` Divya.Koppera
2022-03-07 13:19 ` Andrew Lunn
2022-03-04 13:46 ` Kurt Kanzenbach
2022-03-04 13:57 ` Richard Cochran
2022-03-04 12:50 ` [PATCH net-next 0/3] Add support for 1588 in LAN8814 patchwork-bot+netdevbpf
2022-03-04 13:06 ` Andrew Lunn
2022-03-04 13:21 ` David Miller
2022-03-04 13:47 ` Andrew Lunn
2022-03-04 14:37 ` David Miller
2022-03-04 14:06 ` Richard Cochran
2022-03-04 14:17 ` Andrew Lunn
2022-03-04 15:42 ` Richard Cochran
2022-03-17 12:16 ` Michael Walle
2022-03-17 14:05 ` Allan W. Nielsen
2022-03-17 14:38 ` Andrew Lunn
2022-03-17 19:30 ` Allan W. Nielsen
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=Yi4IrO4Qcm1KVMaa@lunn.ch \
--to=andrew@lunn.ch \
--cc=Divya.Koppera@microchip.com \
--cc=Horatiu.Vultur@microchip.com \
--cc=Madhuri.Sripada@microchip.com \
--cc=Manohar.Puri@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=Woojung.Huh@microchip.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=robh+dt@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).