From: Wei Fang <wei.fang@nxp.com>
To: richardcochran@gmail.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, vladimir.oltean@nxp.com,
xiaoning.wang@nxp.com, Frank.Li@nxp.com, yangbo.lu@nxp.com,
christophe.leroy@csgroup.eu
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org, imx@lists.linux.dev
Subject: [PATCH v2 net-next 0/3] ptp: add pulse signal loopback support for debugging
Date: Fri, 5 Sep 2025 11:07:08 +0800 [thread overview]
Message-ID: <20250905030711.1509648-1-wei.fang@nxp.com> (raw)
Some PTP devices support looping back the periodic pulse signal for
debugging. For example, the PTP device of QorIQ platform and the NETC v4
Timer has the ability to loop back the pulse signal and record the extts
events for the loopback signal. So we can make sure that the pulse
intervals and their phase alignment are correct from the perspective of
the emitting PHC's time base. In addition, we can use this loopback
feature as a built-in extts event generator when we have no external
equipment which does that. Therefore, add the generic debugfs interfaces
to the ptp_clock driver. The first two patch are separated from the
previous patch set [1]. The third patch is new added.
[1]: https://lore.kernel.org/imx/20250827063332.1217664-1-wei.fang@nxp.com/ #patch 3 and 9
---
v2 changes:
1. The value of "enable" is restricted to 0 or 1.
2. Fix the typo: covert --> convert
3. Improve the cover-letter
---
Wei Fang (3):
ptp: add debugfs interfaces to loop back the periodic output signal
ptp: netc: add the periodic output signal loopback support
ptp: qoriq: convert to use generic interfaces to set loopback mode
MAINTAINERS | 1 -
drivers/ptp/Kconfig | 2 +-
drivers/ptp/Makefile | 4 +-
drivers/ptp/ptp_clock.c | 69 +++++++++++++++++++++
drivers/ptp/ptp_netc.c | 25 ++++++++
drivers/ptp/ptp_qoriq.c | 24 +++++++-
drivers/ptp/ptp_qoriq_debugfs.c | 101 -------------------------------
include/linux/fsl/ptp_qoriq.h | 10 ---
include/linux/ptp_clock_kernel.h | 10 +++
9 files changed, 128 insertions(+), 118 deletions(-)
delete mode 100644 drivers/ptp/ptp_qoriq_debugfs.c
--
2.34.1
next reply other threads:[~2025-09-05 3:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 3:07 Wei Fang [this message]
2025-09-05 3:07 ` [PATCH v2 net-next 1/3] ptp: add debugfs interfaces to loop back the periodic output signal Wei Fang
2025-09-05 3:07 ` [PATCH v2 net-next 2/3] ptp: netc: add the periodic output signal loopback support Wei Fang
2025-09-05 3:07 ` [PATCH v2 net-next 3/3] ptp: qoriq: convert to use generic interfaces to set loopback mode Wei Fang
2025-09-10 2:40 ` [PATCH v2 net-next 0/3] ptp: add pulse signal loopback support for debugging patchwork-bot+netdevbpf
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=20250905030711.1509648-1-wei.fang@nxp.com \
--to=wei.fang@nxp.com \
--cc=Frank.Li@nxp.com \
--cc=andrew+netdev@lunn.ch \
--cc=christophe.leroy@csgroup.eu \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=imx@lists.linux.dev \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=vladimir.oltean@nxp.com \
--cc=xiaoning.wang@nxp.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;
as well as URLs for NNTP newsgroup(s).