[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7be41f07-50ab-4363-8a53-dcdda63b9147@lunn.ch>
Date: Mon, 12 Jan 2026 14:24:56 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Vadim Fedorenko <vadim.fedorenko@...ux.dev>
Cc: Sven Schnelle <svens@...ux.ibm.com>, Wen Gu <guwen@...ux.alibaba.com>,
Thomas Gleixner <tglx@...utronix.de>,
Richard Cochran <richardcochran@...il.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Jakub Kicinski <kuba@...nel.org>,
Dust Li <dust.li@...ux.alibaba.com>,
Xuan Zhuo <xuanzhuo@...ux.alibaba.com>,
Andrew Lunn <andrew+netdev@...n.ch>,
David Woodhouse <dwmw2@...radead.org>,
virtualization@...ts.linux.dev, Nick Shi <nick.shi@...adcom.com>,
Paolo Abeni <pabeni@...hat.com>, linux-clk@...r.kernel.org
Subject: Re: [RFC] Defining a home/maintenance model for non-NIC PHC devices
using the /dev/ptpX API
> > drivers/ptp/core - API as written above
> > drivers/ptp/virtual - all PtP drivers somehow emulating a PtP clock
> > (like the ptp_s390 driver)
> > drivers/ptp/net - all NIC related drivers.
> >
>
>
> Well, drivers/ptp/virtual is not really good, because some drivers are
> for physical devices exporting PTP interface, but without NIC.
If the lack of a NIC is the differentiating property:
> > drivers/ptp/net - all NIC related drivers.
> > drivers/ptp/netless - all related drivers which are not associated to a NIC.
Or
> > drivers/ptp/emulating - all drivers emulating a PtP clock
Andrew
Powered by blists - more mailing lists