From: Richard Cochran <richardcochran@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: "Allan W. Nielsen" <allan.nielsen@microchip.com>,
Horatiu Vultur <horatiu.vultur@microchip.com>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, hkallweit1@gmail.com,
linux@armlinux.org.uk, Divya.Koppera@microchip.com,
davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
UNGLinuxDriver@microchip.com
Subject: Re: [PATCH net v2 0/3] net: phy: micrel: Remove latencies support lan8814
Date: Sat, 2 Apr 2022 06:43:09 -0700 [thread overview]
Message-ID: <20220402134309.GA19675@hoboy.vegasvil.org> (raw)
In-Reply-To: <YkcOjlR++GwLWyT5@lunn.ch>
On Fri, Apr 01, 2022 at 04:39:10PM +0200, Andrew Lunn wrote:
> Are you also saying that ptp4l needs to read the values from the
> driver, calculate the differ from the defaults, and then apply that
> difference to the correction specified in the configuration file it
> will apply in userspace?
Personally I wouldn't bother with that. At the end of day, users who
care about sub-microsecond performance will need to calibrate their
particular setup. The output of the calibration will be the system
delay asymmetry correction. That number will be applied in ONE place,
namely the user space PTP stack. Breaking it up into little bits is
just extra work for no benefit.
That is why I'm against any of this driver nonsense. The only purpose
of putting values in to the driver is to unpleasantly surprise the end
users after kernel upgrade.
If this driver defaults + run time query/setting stuff goes mainline,
I'll never use it.
> Does the PTP API enforce mutual exclusion for a device? Can there be
> multiple applications running on an interface, some which assume the
> hardware is configured to perform corrections and some which will
> apply the correction in user space?
There is no mutual exclusion at the kernel API. The main hindrance is
the SIOCSHWTSTAMP ioctl which is at the device level. The setting
applies system wide and is a root caps operation. There is the "Get"
variant that allows co-operation but does not enforce it.
Thanks,
Richard
next prev parent reply other threads:[~2022-04-02 13:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 11:05 [PATCH net v2 0/3] net: phy: micrel: Remove latencies support lan8814 Horatiu Vultur
2022-04-01 11:05 ` [PATCH net v2 1/3] dt-bindings: net: micrel: Revert latency support and timestamping check Horatiu Vultur
2022-04-01 11:05 ` [PATCH net v2 2/3] net: phy: micrel: Remove latency from driver Horatiu Vultur
2022-04-01 11:05 ` [PATCH net v2 3/3] net: phy: micrel: Remove DT option lan8814,ignore-ts Horatiu Vultur
2022-04-01 12:57 ` [PATCH net v2 0/3] net: phy: micrel: Remove latencies support lan8814 Andrew Lunn
2022-04-01 14:11 ` Allan W. Nielsen
2022-04-01 14:39 ` Andrew Lunn
2022-04-02 13:43 ` Richard Cochran [this message]
2022-04-01 14:43 ` Russell King (Oracle)
2022-04-04 12:00 ` patchwork-bot+netdevbpf
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=20220402134309.GA19675@hoboy.vegasvil.org \
--to=richardcochran@gmail.com \
--cc=Divya.Koppera@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=allan.nielsen@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=hkallweit1@gmail.com \
--cc=horatiu.vultur@microchip.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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).