From: Wen Gu <guwen@linux.alibaba.com>
To: richardcochran@gmail.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com
Cc: xuanzhuo@linux.alibaba.com, dust.li@linux.alibaba.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
guwen@linux.alibaba.com
Subject: [PATCH net-next v5 0/2] ptp: Alibaba CIPU PTP clock driver
Date: Thu, 30 Oct 2025 20:13:12 +0800 [thread overview]
Message-ID: <20251030121314.56729-1-guwen@linux.alibaba.com> (raw)
This adds a driver for Alibaba CIPU PTP clock.
The CIPU, an underlying infrastructure of Alibaba Cloud, synchronizes
time with atomic clocks via the network and provides microsecond or
sub-microsecond precision timestamps for VMs and bare metals on cloud.
User space processes, such as chrony, running in VMs or on bare metals
can get the high precision time through the ptp device exposed by this
driver.
In addition, this driver exposes sysfs files for obtaining device
attributes and event statistics, as described in the documentation.
---
v5->v4:
- add documentation describing sysfs files.
v4->v3:
https://lore.kernel.org/netdev/20250812115321.9179-1-guwen@linux.alibaba.com/
- use disable_* variant helpers as suggested by Paolo.
- minor nit: make PTP_CIPU_REG macro one line.
v3->v2:
https://lore.kernel.org/netdev/20250717075734.62296-1-guwen@linux.alibaba.com/
- follow the sysfs convention of one value per file;
- rename enum constants for brevity;
- improve macros for printing;
- add more comments;
v2->v1:
https://lore.kernel.org/netdev/20250627072921.52754-1-guwen@linux.alibaba.com/
- add Kconfig dependency on CONFIG_PCI to fix kernel test
robot's complaint.
v1:
https://lore.kernel.org/netdev/20250625132549.93614-1-guwen@linux.alibaba.com/
Wen Gu (2):
ptp: introduce Alibaba CIPU PHC driver
ptp: add sysfs documentation for Alibaba CIPU PHC driver
.../ABI/testing/sysfs-ptp-devices-cipu | 227 +++++
MAINTAINERS | 8 +
drivers/ptp/Kconfig | 12 +
drivers/ptp/Makefile | 1 +
drivers/ptp/ptp_cipu.c | 946 ++++++++++++++++++
5 files changed, 1194 insertions(+)
create mode 100644 Documentation/ABI/testing/sysfs-ptp-devices-cipu
create mode 100644 drivers/ptp/ptp_cipu.c
--
2.43.5
next reply other threads:[~2025-10-30 12:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 12:13 Wen Gu [this message]
2025-10-30 12:13 ` [PATCH net-next v5 1/2] ptp: introduce Alibaba CIPU PHC driver Wen Gu
2025-10-31 23:58 ` Jakub Kicinski
2025-11-05 10:22 ` Wen Gu
2025-11-06 0:24 ` Jakub Kicinski
2025-11-27 5:48 ` Wen Gu
2025-11-27 16:36 ` Jakub Kicinski
2025-11-28 6:22 ` Wen Gu
2025-11-28 18:24 ` Jakub Kicinski
2025-12-01 6:04 ` Wen Gu
2025-12-12 6:50 ` Wen Gu
2025-12-12 22:50 ` Jakub Kicinski
2025-12-14 14:03 ` Wen Gu
2025-12-16 21:58 ` Jakub Kicinski
2025-12-17 12:40 ` Wen Gu
2025-12-22 7:18 ` Wen Gu
2026-01-02 19:51 ` Jakub Kicinski
2026-01-04 6:11 ` Wen Gu
2026-01-09 9:25 ` David Woodhouse
2026-01-12 3:45 ` Wen Gu
2025-12-18 12:28 ` David Woodhouse
2025-12-22 12:44 ` Wen Gu
2025-10-30 12:13 ` [PATCH net-next v5 2/2] ptp: add sysfs documentation for " 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=20251030121314.56729-1-guwen@linux.alibaba.com \
--to=guwen@linux.alibaba.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dust.li@linux.alibaba.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--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
all inboxes | Powered by JetHome®