From: Michael Chan <michael.chan@broadcom.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, kuba@kernel.org, gospo@broadcom.com,
richardcochran@gmail.com, pavan.chebbi@broadcom.com,
edwin.peer@broadcom.com
Subject: [PATCH net-next v2 0/7] bnxt_en: Add hardware PTP timestamping support on 575XX devices
Date: Sun, 27 Jun 2021 13:19:43 -0400 [thread overview]
Message-ID: <1624814390-1300-1-git-send-email-michael.chan@broadcom.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1587 bytes --]
Add PTP RX and TX hardware timestamp support on 575XX devices. These
devices use the two-step method to implement the IEEE-1588 timestamping
support.
v2: Add spinlock to serialize access to the timecounter.
Use .do_aux_work() for the periodic timer reading and to get the TX
timestamp from the firmware.
Propagate error code from ptp_clock_register().
Make the 64-bit timer access safe on 32-bit CPUs.
Read PHC using direct register access.
Michael Chan (4):
bnxt_en: Update firmware interface to 1.10.2.47
bnxt_en: Get PTP hardware capability from firmware
bnxt_en: Add PTP clock APIs, ioctls, and ethtool methods
bnxt_en: Enable hardware PTP support
Pavan Chebbi (3):
bnxt_en: Get the full 48-bit hardware timestamp periodically
bnxt_en: Get the RX packet timestamp
bnxt_en: Transmit and retrieve packet timestamps
drivers/net/ethernet/broadcom/Kconfig | 1 +
drivers/net/ethernet/broadcom/bnxt/Makefile | 2 +-
drivers/net/ethernet/broadcom/bnxt/bnxt.c | 134 +++-
drivers/net/ethernet/broadcom/bnxt/bnxt.h | 10 +-
.../net/ethernet/broadcom/bnxt/bnxt_ethtool.c | 34 +
drivers/net/ethernet/broadcom/bnxt/bnxt_hsi.h | 667 ++++++++++++++++--
drivers/net/ethernet/broadcom/bnxt/bnxt_ptp.c | 473 +++++++++++++
drivers/net/ethernet/broadcom/bnxt/bnxt_ptp.h | 81 +++
.../net/ethernet/broadcom/bnxt/bnxt_sriov.c | 4 +-
9 files changed, 1355 insertions(+), 51 deletions(-)
create mode 100644 drivers/net/ethernet/broadcom/bnxt/bnxt_ptp.c
create mode 100644 drivers/net/ethernet/broadcom/bnxt/bnxt_ptp.h
--
2.18.1
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4209 bytes --]
next reply other threads:[~2021-06-27 17:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-27 17:19 Michael Chan [this message]
2021-06-27 17:19 ` [PATCH net-next v2 1/7] bnxt_en: Update firmware interface to 1.10.2.47 Michael Chan
2021-06-27 17:19 ` [PATCH net-next v2 2/7] bnxt_en: Get PTP hardware capability from firmware Michael Chan
2021-06-27 17:19 ` [PATCH net-next v2 3/7] bnxt_en: Add PTP clock APIs, ioctls, and ethtool methods Michael Chan
2021-06-27 17:19 ` [PATCH net-next v2 4/7] bnxt_en: Get the full 48-bit hardware timestamp periodically Michael Chan
2021-06-27 17:19 ` [PATCH net-next v2 5/7] bnxt_en: Get the RX packet timestamp Michael Chan
2021-06-27 17:19 ` [PATCH net-next v2 6/7] bnxt_en: Transmit and retrieve packet timestamps Michael Chan
2021-06-27 17:19 ` [PATCH net-next v2 7/7] bnxt_en: Enable hardware PTP support Michael Chan
2021-06-28 20:50 ` [PATCH net-next v2 0/7] bnxt_en: Add hardware PTP timestamping support on 575XX devices 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=1624814390-1300-1-git-send-email-michael.chan@broadcom.com \
--to=michael.chan@broadcom.com \
--cc=davem@davemloft.net \
--cc=edwin.peer@broadcom.com \
--cc=gospo@broadcom.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pavan.chebbi@broadcom.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;
as well as URLs for NNTP newsgroup(s).