[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20230306095515.20e819d1@kernel.org>
Date: Mon, 6 Mar 2023 09:55:15 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Andrew Lunn <andrew@...n.ch>
Cc: "Russell King (Oracle)" <linux@...linux.org.uk>,
Köry Maincent <kory.maincent@...tlin.com>,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
linux-omap@...r.kernel.org, Michael Walle <michael@...le.cc>,
Richard Cochran <richardcochran@...il.com>,
thomas.petazzoni@...tlin.com, Jay Vosburgh <j.vosburgh@...il.com>,
Veaceslav Falico <vfalico@...il.com>,
Andy Gospodarek <andy@...yhouse.net>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Paolo Abeni <pabeni@...hat.com>,
Joakim Zhang <qiangqing.zhang@....com>,
Vladimir Oltean <vladimir.oltean@....com>,
Claudiu Manoil <claudiu.manoil@....com>,
Alexandre Belloni <alexandre.belloni@...tlin.com>,
UNGLinuxDriver@...rochip.com,
Grygorii Strashko <grygorii.strashko@...com>,
Heiner Kallweit <hkallweit1@...il.com>,
Minghao Chi <chi.minghao@....com.cn>,
Jie Wang <wangjie125@...wei.com>,
Guangbin Huang <huangguangbin2@...wei.com>,
Wolfram Sang <wsa+renesas@...g-engineering.com>,
Wang Yufen <wangyufen@...wei.com>,
Alexandru Tachici <alexandru.tachici@...log.com>,
Oleksij Rempel <linux@...pel-privat.de>
Subject: Re: [PATCH v2 3/4] net: Let the active time stamping layer be
selectable.
On Sat, 4 Mar 2023 20:46:05 +0100 Andrew Lunn wrote:
> > Since the ioctl is to do with requesting what we want the timestamping
> > layer to be doing with packets, putting it in ptp_clock_info makes
> > very little sense.
>
> So there does not appear to be an object to represent a time stamper?
>
> Should one be added? It looks like it needs two ops hwtstamp_set() and
> hwtstamp_get(). It would then be registered with the ptp core. And
> then the rest of what i said would apply...
IMHO time stamper is very much part of the netdev. I attribute the lack
of clarity palatially to the fact that (for reasons unknown) we still
lug the request as a raw IOCTL/ifreq. Rather than converting it to an
NDO/phydev op in the core.. Also can't think of a reason why modeling
it as a separate object would be useful?
Powered by blists - more mailing lists