From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
Richard Cochran <richardcochran@gmail.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Michael Chan <michael.chan@broadcom.com>,
Pavan Chebbi <pavan.chebbi@broadcom.com>,
Tariq Toukan <tariqt@nvidia.com>,
Saeed Mahameed <saeedm@nvidia.com>,
Mark Bloch <mbloch@nvidia.com>,
Vadim Fedorenko <vadim.fedorenko@linux.dev>
Cc: netdev@vger.kernel.org
Subject: [PATCH net-next 0/4] convert 3 drivers to ndo_hwtstamp API
Date: Mon, 22 Sep 2025 16:51:14 +0000 [thread overview]
Message-ID: <20250922165118.10057-1-vadim.fedorenko@linux.dev> (raw)
Convert tg3, bnxt_en and mlx5 to use ndo_hwtstamp API. These 3 drivers
were chosen because I have access to the HW and is able to test the
changes. Also there is a selftest provided to validated that the driver
correctly sets up timestamp configuration, according to what is exposed
as supported by the hardware. Selftest allows driver to fallback to some
wider scope of RX timestamping, i.e. it allows the driver to set up
ptpv2-event filter when ptpv2-l2-event is requested.
Vadim Fedorenko (4):
tg3: convert to ndo_hwtstamp_get() and ndo_hwtstamp_set()
bnxt_en: convert to ndo_hwtstamp_get() and ndo_hwtstamp_set()
mlx5: convert to ndo_hwtstamp_get() and ndo_hwtstamp_set()
selftests: drv-net: add HW timestamping tests
drivers/net/ethernet/broadcom/bnxt/bnxt.c | 8 +-
drivers/net/ethernet/broadcom/bnxt/bnxt_ptp.c | 35 ++++-----
drivers/net/ethernet/broadcom/bnxt/bnxt_ptp.h | 7 +-
drivers/net/ethernet/broadcom/tg3.c | 66 +++++++---------
drivers/net/ethernet/mellanox/mlx5/core/en.h | 13 ++--
.../net/ethernet/mellanox/mlx5/core/en/ptp.h | 2 +-
.../net/ethernet/mellanox/mlx5/core/en/trap.h | 2 +-
.../net/ethernet/mellanox/mlx5/core/en/txrx.h | 2 +-
.../net/ethernet/mellanox/mlx5/core/en_main.c | 47 +++++-------
.../net/ethernet/mellanox/mlx5/core/en_rx.c | 2 +-
.../ethernet/mellanox/mlx5/core/ipoib/ipoib.c | 17 +----
.../ethernet/mellanox/mlx5/core/ipoib/ipoib.h | 1 -
.../mellanox/mlx5/core/ipoib/ipoib_vlan.c | 9 +--
.../ethernet/mellanox/mlx5/core/lib/clock.h | 14 ++--
.../selftests/drivers/net/hw/nic_timestamp.py | 75 +++++++++++++++++++
15 files changed, 167 insertions(+), 133 deletions(-)
create mode 100755 tools/testing/selftests/drivers/net/hw/nic_timestamp.py
--
2.47.3
next reply other threads:[~2025-09-22 17:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 16:51 Vadim Fedorenko [this message]
2025-09-22 16:51 ` [PATCH net-next 1/4] tg3: convert to ndo_hwtstamp_get() and ndo_hwtstamp_set() Vadim Fedorenko
2025-09-22 22:15 ` Michael Chan
2025-09-23 3:47 ` Pavan Chebbi
2025-09-22 16:51 ` [PATCH net-next 2/4] bnxt_en: " Vadim Fedorenko
2025-09-22 22:17 ` Michael Chan
2025-09-23 3:48 ` Pavan Chebbi
2025-09-22 16:51 ` [PATCH net-next 3/4] mlx5: " Vadim Fedorenko
2025-09-23 17:44 ` Carolina Jubran
2025-09-23 20:48 ` Vadim Fedorenko
2025-09-22 16:51 ` [PATCH net-next 4/4] selftests: drv-net: add HW timestamping tests Vadim Fedorenko
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=20250922165118.10057-1-vadim.fedorenko@linux.dev \
--to=vadim.fedorenko@linux.dev \
--cc=andrew+netdev@lunn.ch \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=mbloch@nvidia.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.com \
--cc=richardcochran@gmail.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.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).