From: Michael Chan <michael.chan@broadcom.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, pavan.chebbi@broadcom.com,
andrew.gospodarek@broadcom.com, jiri@resnulli.us,
richardcochran@gmail.com
Subject: [PATCH net-next 0/2] bnxt_en: Support configurable PTP TX timeout
Date: Wed, 28 Feb 2024 23:02:00 -0800 [thread overview]
Message-ID: <20240229070202.107488-1-michael.chan@broadcom.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 982 bytes --]
The driver needs to call firmware to retrieve the PTP hardware TX
timestamp for PTP packets. The PTP packet is timestamped by hardware
right before packet transmission on the wire. So there is variable
delay on when the timestamp is available. The current fixed timeout
value of 1 msec passed to the firmware may not be long enough on
busy networks.
Add a devlink driver runtime parameter to allow the user to configure
this timeout value. Increase the default to 1 second and allow a
maximum of 5 seconds.
Pavan Chebbi (2):
bnxt_en: Introduce devlink runtime driver param to set ptp tx timeout
bnxt_en: Retry for TX timestamp from FW until timeout specified
Documentation/networking/devlink/bnxt.rst | 7 ++++
.../net/ethernet/broadcom/bnxt/bnxt_devlink.c | 42 +++++++++++++++++++
drivers/net/ethernet/broadcom/bnxt/bnxt_ptp.c | 20 +++++++--
drivers/net/ethernet/broadcom/bnxt/bnxt_ptp.h | 7 +++-
4 files changed, 72 insertions(+), 4 deletions(-)
--
2.30.1
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4209 bytes --]
next reply other threads:[~2024-02-29 7:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 7:02 Michael Chan [this message]
2024-02-29 7:02 ` [PATCH net-next 1/2] bnxt_en: Introduce devlink runtime driver param to set ptp tx timeout Michael Chan
2024-02-29 9:27 ` Vadim Fedorenko
2024-02-29 17:11 ` Jiri Pirko
2024-02-29 17:30 ` Jakub Kicinski
2024-02-29 21:22 ` Vadim Fedorenko
2024-03-01 1:49 ` Jakub Kicinski
2024-03-01 7:39 ` Pavan Chebbi
2024-03-01 17:18 ` Jakub Kicinski
2024-03-07 3:50 ` Pavan Chebbi
2024-03-07 4:19 ` Jakub Kicinski
2024-03-01 11:34 ` Jiri Pirko
2024-02-29 7:02 ` [PATCH net-next 2/2] bnxt_en: Retry for TX timestamp from FW until timeout specified Michael Chan
2024-02-29 9:23 ` Vadim Fedorenko
2024-02-29 16:43 ` Michael Chan
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=20240229070202.107488-1-michael.chan@broadcom.com \
--to=michael.chan@broadcom.com \
--cc=andrew.gospodarek@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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).