From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Michael Chan <michael.chan@broadcom.com>,
Pavan Chebbi <pavan.chebbi@broadcom.com>,
Jakub Kicinski <kuba@kernel.org>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Richard Cochran <richardcochran@gmail.com>,
netdev@vger.kernel.org,
Vadim Fedorenko <vadim.fedorenko@linux.dev>
Subject: [PATCH net-next] bnxt_en: support PPS in/out on all pins
Date: Thu, 16 Oct 2025 22:23:17 +0000 [thread overview]
Message-ID: <20251016222317.3512207-1-vadim.fedorenko@linux.dev> (raw)
n_ext_ts and n_per_out from ptp_clock_caps are checked as a max number
of pins rather than max number of active pins.
supported_extts_flags and supported_perout_flags have to be added as
well to make the driver complaint with the latest API.
Signed-off-by: Vadim Fedorenko <vadim.fedorenko@linux.dev>
---
drivers/net/ethernet/broadcom/bnxt/bnxt_ptp.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/net/ethernet/broadcom/bnxt/bnxt_ptp.c b/drivers/net/ethernet/broadcom/bnxt/bnxt_ptp.c
index db81cf6d5289..c9b7df669415 100644
--- a/drivers/net/ethernet/broadcom/bnxt/bnxt_ptp.c
+++ b/drivers/net/ethernet/broadcom/bnxt/bnxt_ptp.c
@@ -965,10 +965,12 @@ static int bnxt_ptp_pps_init(struct bnxt *bp)
hwrm_req_drop(bp, req);
/* Only 1 each of ext_ts and per_out pins is available in HW */
- ptp_info->n_ext_ts = 1;
- ptp_info->n_per_out = 1;
+ ptp_info->n_ext_ts = pps_info->num_pins;
+ ptp_info->n_per_out = pps_info->num_pins;
ptp_info->pps = 1;
ptp_info->verify = bnxt_ptp_verify;
+ ptp_info->supported_extts_flags = PTP_RISING_EDGE | PTP_STRICT_FLAGS;
+ ptp_info->supported_perout_flags = PTP_PEROUT_DUTY_CYCLE;
return 0;
}
--
2.47.3
next reply other threads:[~2025-10-16 22:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 22:23 Vadim Fedorenko [this message]
2025-10-17 3:45 ` [PATCH net-next] bnxt_en: support PPS in/out on all pins Pavan Chebbi
2025-10-17 8:51 ` Vadim Fedorenko
2025-10-17 9:15 ` Pavan Chebbi
2025-10-17 10:40 ` Vadim Fedorenko
2025-10-17 14:08 ` Pavan Chebbi
2025-10-17 16:39 ` 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=20251016222317.3512207-1-vadim.fedorenko@linux.dev \
--to=vadim.fedorenko@linux.dev \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=michael.chan@broadcom.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.