From: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
To: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
intel-wired-lan@lists.osuosl.org
Cc: anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, richardcochran@gmail.com,
Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
Subject: [PATCH net-next v3 0/2] ptp: add control over HW timestamp latch point
Date: Wed, 6 Nov 2024 02:07:54 +0100 [thread overview]
Message-ID: <20241106010756.1588973-1-arkadiusz.kubalewski@intel.com> (raw)
HW support of ptp/timesync solutions in network PHY chips can be
achieved with two different approaches, the timestamp maybe latched
either in the beginning or after the Start of Frame Delimiter (SFD) [1].
Allow ptp device drivers to provide user with control over the timestamp
latch point.
[1] https://www.ieee802.org/3/cx/public/april20/tse_3cx_01_0420.pdf
v3:
- move new enum ptp_ts_point to uapi ptp_clock.h and add NONE value to
indicate that the timestamp latch point was not provided by the HW,
allow further changes to ethtool netlink interface exstensions.
Arkadiusz Kubalewski (2):
ptp: add control over HW timestamp latch point
ice: ptp: add control over HW timestamp latch point
Documentation/ABI/testing/sysfs-ptp | 12 +++++
drivers/net/ethernet/intel/ice/ice_ptp.c | 44 +++++++++++++++
drivers/net/ethernet/intel/ice/ice_ptp_hw.c | 60 +++++++++++++++++++++
drivers/net/ethernet/intel/ice/ice_ptp_hw.h | 2 +
drivers/ptp/ptp_sysfs.c | 44 +++++++++++++++
include/linux/ptp_clock_kernel.h | 12 +++++
include/uapi/linux/ptp_clock.h | 18 +++++++
7 files changed, 192 insertions(+)
base-commit: 0452a2d8b8b98a5b1a9139c1a9ed98bccee356cc
--
2.38.1
next reply other threads:[~2024-11-06 1:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 1:07 Arkadiusz Kubalewski [this message]
2024-11-06 1:07 ` [PATCH net-next v3 1/2] " Arkadiusz Kubalewski
2024-11-06 2:04 ` Jakub Kicinski
2024-11-07 9:01 ` Kubalewski, Arkadiusz
2024-11-07 17:54 ` Richard Cochran
2024-11-06 17:45 ` Andrew Lunn
2024-11-07 9:14 ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2024-11-06 1:07 ` [PATCH net-next v3 2/2] ice: " Arkadiusz Kubalewski
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=20241106010756.1588973-1-arkadiusz.kubalewski@intel.com \
--to=arkadiusz.kubalewski@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=richardcochran@gmail.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®