From: Wen Gu <guwen@linux.alibaba.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
tglx@kernel.org, tglx@linutronix.de, richardcochran@gmail.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, mani@kernel.org,
imran.shaik@oss.qualcomm.com, vladimir.oltean@nxp.com,
wei.fang@nxp.com, xiaoning.wang@nxp.com,
jonathan.lemon@gmail.com, vadim.fedorenko@linux.dev,
yangbo.lu@nxp.com, svens@linux.ibm.com, nick.shi@broadcom.com,
ajay.kaher@broadcom.com, alexey.makhalov@broadcom.com,
bcm-kernel-feedback-list@broadcom.com,
linux-fpga@vger.kernel.org, imx@lists.linux.dev,
linux-s390@vger.kernel.org, dust.li@linux.alibaba.com,
xuanzhuo@linux.alibaba.com, taniya.das@oss.qualcomm.com
Subject: Re: [RFC v2 0/2] ptp: Move non-NIC PHC drivers from netdev to clock/timekeeping maintainership
Date: Mon, 9 Mar 2026 10:28:21 +0800 [thread overview]
Message-ID: <6397594f-eb3f-4207-9c20-b0f7e409054c@linux.alibaba.com> (raw)
In-Reply-To: <20260305184110.13e79837@kernel.org>
On 2026/3/6 10:41, Jakub Kicinski wrote:
> On Fri, 27 Feb 2026 20:25:11 +0800 Wen Gu wrote:
>> As mentioned in RFC v1, the use cases for drivers in the emulated PHC category
>> are expected to be quite diverse, and not limited to the virtualization/guest
>> time sync use case. For example, existing drivers such as ptp_ocp [1] and
>> upcoming ones such as mhi_phc [2] are not related to virtualization use cases.
>
> ptp_ocp is a real PCIe device with an atomic clock. mhi_phc is some
> qualcomm fw-defined thing, so more closely mapping what you're doing.
> ptp_ocp should probably stay under netdev, we maintain DPLL drivers,
> too. Main thing we/I don't want to deal with is all the corporate NIH
> virtualization excreta.
OK. ptp_ocp will be kept under netdev in the next version.
next prev parent reply other threads:[~2026-03-09 2:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 8:19 [RFC v2 0/2] ptp: Move non-NIC PHC drivers from netdev to clock/timekeeping maintainership Wen Gu
2026-02-27 8:19 ` [RFC v2 1/2] ptp: split clock drivers into two subdirectories Wen Gu
2026-02-27 8:19 ` [RFC v2 2/2] MAINTAINERS: update PTP maintainer entries after directory split Wen Gu
2026-02-27 10:25 ` [RFC v2 0/2] ptp: Move non-NIC PHC drivers from netdev to clock/timekeeping maintainership David Woodhouse
2026-02-27 12:25 ` Wen Gu
2026-03-06 2:41 ` Jakub Kicinski
2026-03-09 2:28 ` Wen Gu [this message]
2026-03-17 2:12 ` Wen Gu
2026-03-09 6:54 ` 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=6397594f-eb3f-4207-9c20-b0f7e409054c@linux.alibaba.com \
--to=guwen@linux.alibaba.com \
--cc=ajay.kaher@broadcom.com \
--cc=alexey.makhalov@broadcom.com \
--cc=andrew+netdev@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=dust.li@linux.alibaba.com \
--cc=dwmw2@infradead.org \
--cc=edumazet@google.com \
--cc=imran.shaik@oss.qualcomm.com \
--cc=imx@lists.linux.dev \
--cc=jonathan.lemon@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mani@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=taniya.das@oss.qualcomm.com \
--cc=tglx@kernel.org \
--cc=tglx@linutronix.de \
--cc=vadim.fedorenko@linux.dev \
--cc=vladimir.oltean@nxp.com \
--cc=wei.fang@nxp.com \
--cc=xiaoning.wang@nxp.com \
--cc=xuanzhuo@linux.alibaba.com \
--cc=yangbo.lu@nxp.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