From: Richard Cochran <richardcochran@gmail.com>
To: Wen Gu <guwen@linux.alibaba.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"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>,
Sven Schnelle <svens@linux.ibm.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 20:21:29 -0800 [thread overview]
Message-ID: <aWXISRWpkW-oHyUw@hoboy.vegasvil.org> (raw)
In-Reply-To: <0afe19db-9c7f-4228-9fc2-f7b34c4bc227@linux.alibaba.com>
On Fri, Jan 09, 2026 at 10:56:56AM +0800, Wen Gu wrote:
> Introducing a new clock type or a new userspace API (e.g. /dev/XXX) would
> require widespread userspace changes, duplicated tooling, and long-term
> fragmentation. This RFC is explicitly NOT proposing a new userspace API.
Actually I disagree.
The PHC devices appear to user space as clockid_t.
The API for these works seamlessly and interchangeably with SYS-V clock IDs.
The path that is opened, whether /dev/ptpX or some new /dev/hwclkX etc
is a trivial detail that adds no burden to user space.
Thanks,
Richard
next prev parent reply other threads:[~2026-01-13 4:21 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
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 [this message]
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=aWXISRWpkW-oHyUw@hoboy.vegasvil.org \
--to=richardcochran@gmail.com \
--cc=andrew+netdev@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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox