From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out30-119.freemail.mail.aliyun.com (out30-119.freemail.mail.aliyun.com [115.124.30.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 192FE18DF9D; Wed, 18 Mar 2026 07:33:35 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=115.124.30.119 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773819219; cv=none; b=pFZDxLJ2EHCRFaWTN1oYUEomJxJPLiLdhvOhssAQKqN/qJ3UOtXRtLcMXvNFH4+VBPHvQMzfftqSIR7V6b3FNQci1YWyJ5A19iO6AWHsmCp1r8Qy4/RwXozoL7KAE48U7Rf2lf2V+al7kgZUQ11MFHLt00HjV/VwWFQX1kBIZwQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773819219; c=relaxed/simple; bh=t5F2TCGPw+OsdAgO3uUtYnUtl5l/McGQbP9PGs58Yyo=; h=From:To:Cc:Subject:Date:Message-Id:MIME-Version; b=pC3R81PFLuvMmHLfsRY+M9lB4YuwZRDK+H02Zy5h+c4M0GH5zF2EcZWPWnj1Kp+6HRyzxcjrshd6ZueCqfsxwBv8VRSmvt/jtBoh3cAlrlkcrL6M3VezT36OLVFJxVhaa2VSiyn2XdRatt25Pr8X/7Ev3HWTpEGnGdoJAC7V0QA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.alibaba.com; spf=pass smtp.mailfrom=linux.alibaba.com; dkim=pass (1024-bit key) header.d=linux.alibaba.com header.i=@linux.alibaba.com header.b=GzziO0q2; arc=none smtp.client-ip=115.124.30.119 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.alibaba.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.alibaba.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.alibaba.com header.i=@linux.alibaba.com header.b="GzziO0q2" DKIM-Signature:v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.alibaba.com; s=default; t=1773819213; h=From:To:Subject:Date:Message-Id:MIME-Version; bh=iWphu+L5zUeNeeTpm0magbZ/yJ23C4KHG95YHYtp+NM=; b=GzziO0q2DWiJWSjLe1i7IXuHgmoAJwH38yHsCKejVKlqFPrZB9PGrWCBA7R7e/lXzOspsmzJws24MEPCa3JLID5fGGxQLXAZyiIwnjeioI6KhGoZW4esDo/ZQeWx+Bztct575MkGoESCeZbwU0mvR/tGCAx6yjt64/myLqG0LWQ= X-Alimail-AntiSpam:AC=PASS;BC=-1|-1;BR=01201311R111e4;CH=green;DM=||false|;DS=||;FP=0|-1|-1|-1|0|-1|-1|-1;HT=maildocker-contentspam033045133197;MF=guwen@linux.alibaba.com;NM=1;PH=DS;RN=35;SR=0;TI=SMTPD_---0X.DZlmH_1773819210; Received: from localhost(mailfrom:guwen@linux.alibaba.com fp:SMTPD_---0X.DZlmH_1773819210 cluster:ay36) by smtp.aliyun-inc.com; Wed, 18 Mar 2026 15:33:31 +0800 From: Wen Gu To: tglx@kernel.org, tglx@linutronix.de, richardcochran@gmail.com, andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com, kuba@kernel.org, pabeni@redhat.com, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, jstultz@google.com, anna-maria@linutronix.de, frederic@kernel.org, daniel.lezcano@kernel.org, sboyd@kernel.org Cc: 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, dwmw2@infradead.org, 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, mani@kernel.org, imran.shaik@oss.qualcomm.com, taniya.das@oss.qualcomm.com Subject: [PATCH 0/2] ptp: split non-NIC PHC drivers into the clock/timekeeping maintenance domain Date: Wed, 18 Mar 2026 15:33:28 +0800 Message-Id: <20260318073330.115808-1-guwen@linux.alibaba.com> X-Mailer: git-send-email 2.32.0.3.g01195cf9f Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Hi all, This series follows the discussion in RFC v1 and RFC v2 [1-2]. # Background The PTP Hardware Clock (PHC) interface (/dev/ptpX and the standard PTP_* ioctls) was originally introduced for IEEE 1588 / network oriented clock drivers. Over time, it has also become a common userspace API for many non-NIC high-precision clock implementations (virtualization/platform/architecture provided clocks) [3-7], and more are expected to appear [8-9]. During the review of these incoming non IEEE 1588 based PHC drivers, concerns were raised that such "non-NIC" clocks may not be a good fit for the netdev maintainership model [10], where PTP/PHC drivers are currently maintained. This leaves an unclear upstream home and maintainership model for this class of drivers. # Proposal This series proposes moving PHC drivers that expose a high-precision clock to userspace via the existing PTP interface (/dev/ptpX + standard PTP_* ioctls), but are not tied to the traditional NIC/IEEE 1588 packet timestamping pipeline, out of the netdev maintenance domain and into the clock/timekeeping maintenance domain. As discussed in [1-2], this series makes the separation explicit by splitting drivers/ptp/ into the following groups. This structure provides clearer ownership and long-term maintenance boundaries: - drivers/ptp/ : PTP core infrastructure and userspace ABI (ptp_clock.c, ptp_chardev.c, ptp_sysfs.c, ptp_vclock.c, etc.) remain here. - drivers/ptp/ieee1588/ : network / IEEE 1588 oriented PTP drivers. - drivers/ptp/emulated/ : non IEEE 1588 PTP drivers. They are typically platform/architecture/virtualization/special hardware provided high-precision time sources. Patch 1 performs the refactor: move drivers and split Kconfig/Makefiles accordingly, without intended functional changes. Patch 2 updates MAINTAINERS to match the new layout and adds a dedicated entry for drivers/ptp/emulated/, moving review and ownership routing for this class of drivers away from the netdev maintainership. No userspace ABI changes are intended, this is a refactor and maintenance metadata update only. # Changes since RFC v2: - Keep ptp_ocp under the IEEE1588/network-oriented PTP drivers as suggested by Jakub. - Following the model used by NTP related code, this series lists tip.git (timers/core) as the integration tree for emulated PTP clocks in the MAINTAINERS entry. Guidance from clock/timekeeping maintainers (Thomas Gleixner, John Stultz, Anna-Maria Behnsen, Frederic Weisbecker, Daniel Lezcano, Stephen Boyd) on whether this is the appropriate workflow for this class of drivers would be appreciated. - Continue listing ourselves as maintainers for now as a fallback contact point. In the long term it would be preferable for this area to be maintained by clock/timekeeping experts, and suggestions are welcome. Thanks for any input. Regards. [1] https://lore.kernel.org/all/0afe19db-9c7f-4228-9fc2-f7b34c4bc227@linux.alibaba.com/ [2] https://lore.kernel.org/all/20260227081934.96865-1-guwen@linux.alibaba.com/ [3] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a0e136d436ded817c0aade72efdefa56a00b4e5e [4] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7d10001e20e46ad6ad95622164686bc2cbfc9802 [5] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2d7de7a3010d713fb89b7ba99e6fdc14475ad106 [6] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3716a49a81ba19dda7202633a68b28564ba95eb5 [7] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9a17125a18f9ae1e1233a8e2d919059445b9d6fd [8] https://lore.kernel.org/netdev/20251030121314.56729-1-guwen@linux.alibaba.com/ [9] https://lore.kernel.org/mhi/20250818-tsc_time_sync-v1-0-2747710693ba@oss.qualcomm.com/ [10] https://lore.kernel.org/netdev/20251127083610.6b66a728@kernel.org/ Wen Gu (2): ptp: split clock drivers into two subdirectories MAINTAINERS: update PTP maintainer entries after directory split MAINTAINERS | 38 ++- drivers/ptp/Kconfig | 255 ++----------------- drivers/ptp/Makefile | 27 +- drivers/ptp/emulated/Kconfig | 61 +++++ drivers/ptp/emulated/Makefile | 11 + drivers/ptp/{ => emulated}/ptp_kvm_arm.c | 0 drivers/ptp/{ => emulated}/ptp_kvm_common.c | 0 drivers/ptp/{ => emulated}/ptp_kvm_x86.c | 0 drivers/ptp/{ => emulated}/ptp_s390.c | 0 drivers/ptp/{ => emulated}/ptp_vmclock.c | 0 drivers/ptp/{ => emulated}/ptp_vmw.c | 0 drivers/ptp/ieee1588/Kconfig | 179 +++++++++++++ drivers/ptp/ieee1588/Makefile | 16 ++ drivers/ptp/{ => ieee1588}/ptp_clockmatrix.c | 0 drivers/ptp/{ => ieee1588}/ptp_clockmatrix.h | 0 drivers/ptp/{ => ieee1588}/ptp_dfl_tod.c | 0 drivers/ptp/{ => ieee1588}/ptp_dte.c | 0 drivers/ptp/{ => ieee1588}/ptp_fc3.c | 0 drivers/ptp/{ => ieee1588}/ptp_fc3.h | 0 drivers/ptp/{ => ieee1588}/ptp_idt82p33.c | 0 drivers/ptp/{ => ieee1588}/ptp_idt82p33.h | 0 drivers/ptp/{ => ieee1588}/ptp_ines.c | 0 drivers/ptp/{ => ieee1588}/ptp_mock.c | 0 drivers/ptp/{ => ieee1588}/ptp_netc.c | 0 drivers/ptp/{ => ieee1588}/ptp_ocp.c | 0 drivers/ptp/{ => ieee1588}/ptp_pch.c | 0 drivers/ptp/{ => ieee1588}/ptp_qoriq.c | 0 27 files changed, 322 insertions(+), 265 deletions(-) create mode 100644 drivers/ptp/emulated/Kconfig create mode 100644 drivers/ptp/emulated/Makefile rename drivers/ptp/{ => emulated}/ptp_kvm_arm.c (100%) rename drivers/ptp/{ => emulated}/ptp_kvm_common.c (100%) rename drivers/ptp/{ => emulated}/ptp_kvm_x86.c (100%) rename drivers/ptp/{ => emulated}/ptp_s390.c (100%) rename drivers/ptp/{ => emulated}/ptp_vmclock.c (100%) rename drivers/ptp/{ => emulated}/ptp_vmw.c (100%) create mode 100644 drivers/ptp/ieee1588/Kconfig create mode 100644 drivers/ptp/ieee1588/Makefile rename drivers/ptp/{ => ieee1588}/ptp_clockmatrix.c (100%) rename drivers/ptp/{ => ieee1588}/ptp_clockmatrix.h (100%) rename drivers/ptp/{ => ieee1588}/ptp_dfl_tod.c (100%) rename drivers/ptp/{ => ieee1588}/ptp_dte.c (100%) rename drivers/ptp/{ => ieee1588}/ptp_fc3.c (100%) rename drivers/ptp/{ => ieee1588}/ptp_fc3.h (100%) rename drivers/ptp/{ => ieee1588}/ptp_idt82p33.c (100%) rename drivers/ptp/{ => ieee1588}/ptp_idt82p33.h (100%) rename drivers/ptp/{ => ieee1588}/ptp_ines.c (100%) rename drivers/ptp/{ => ieee1588}/ptp_mock.c (100%) rename drivers/ptp/{ => ieee1588}/ptp_netc.c (100%) rename drivers/ptp/{ => ieee1588}/ptp_ocp.c (100%) rename drivers/ptp/{ => ieee1588}/ptp_pch.c (100%) rename drivers/ptp/{ => ieee1588}/ptp_qoriq.c (100%) -- 2.43.5