[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87495044-59a3-49ed-b00c-01a7e9a23f6b@linux.dev>
Date: Mon, 12 Jan 2026 14:52:30 +0000
From: Vadim Fedorenko <vadim.fedorenko@...ux.dev>
To: Andrew Lunn <andrew@...n.ch>
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
On 12/01/2026 13:24, Andrew Lunn wrote:
>>> 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
I would go with "emulating" then.
>
> Andrew
Powered by blists - more mailing lists