From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Sven Schnelle <svens@linux.ibm.com>,
Wen Gu <guwen@linux.alibaba.com>,
Thomas Gleixner <tglx@linutronix.de>,
Richard Cochran <richardcochran@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
Dust Li <dust.li@linux.alibaba.com>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
David Woodhouse <dwmw2@infradead.org>,
virtualization@lists.linux.dev, Nick Shi <nick.shi@broadcom.com>,
Paolo Abeni <pabeni@redhat.com>,
linux-clk@vger.kernel.org
Subject: Re: [RFC] Defining a home/maintenance model for non-NIC PHC devices using the /dev/ptpX API
Date: Mon, 12 Jan 2026 14:52:30 +0000 [thread overview]
Message-ID: <87495044-59a3-49ed-b00c-01a7e9a23f6b@linux.dev> (raw)
In-Reply-To: <7be41f07-50ab-4363-8a53-dcdda63b9147@lunn.ch>
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
next prev parent reply other threads:[~2026-01-12 14:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 2:56 [RFC] Defining a home/maintenance model for non-NIC PHC devices using the /dev/ptpX API Wen Gu
2026-01-12 8:04 ` David Woodhouse
2026-01-14 9:06 ` Wen Gu
2026-01-12 11:00 ` Sven Schnelle
2026-01-12 12:15 ` Vadim Fedorenko
2026-01-12 13:24 ` Andrew Lunn
2026-01-12 14:52 ` Vadim Fedorenko [this message]
2026-01-14 9:13 ` Wen Gu
2026-01-14 10:50 ` Vadim Fedorenko
2026-01-14 12:45 ` Wen Gu
2026-01-13 4:21 ` Richard Cochran
2026-01-14 9:16 ` Wen Gu
2026-01-19 14:48 ` Manivannan Sadhasivam
2026-01-21 14:20 ` Wen Gu
2026-01-21 14:29 ` Wen Gu
2026-02-19 9:29 ` Imran Shaik
2026-02-25 1:45 ` Wen Gu
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=87495044-59a3-49ed-b00c-01a7e9a23f6b@linux.dev \
--to=vadim.fedorenko@linux.dev \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=dust.li@linux.alibaba.com \
--cc=dwmw2@infradead.org \
--cc=guwen@linux.alibaba.com \
--cc=kuba@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nick.shi@broadcom.com \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=svens@linux.ibm.com \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.