public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
From: Mohammad Shuab Siddique <mohammad-shuab.siddique@broadcom.com>
To: dev@dpdk.org
Cc: kishore.padmanabha@broadcom.com,
	Mohammad Shuab Siddique <root@nic1-cos.dhcp.broadcom.net>,
	stable@dpdk.org
Subject: [PATCH 4/4] net/bnxt: add ptp_cfg struct support for Thor 2 VFs
Date: Mon,  2 Mar 2026 10:12:36 -0700	[thread overview]
Message-ID: <20260302171236.98625-5-Mohammad-Shuab.Siddique@broadcom.com> (raw)
In-Reply-To: <20260302171236.98625-1-Mohammad-Shuab.Siddique@broadcom.com>

From: Mohammad Shuab Siddique <root@nic1-cos.dhcp.broadcom.net>

Modified ptp_cfg initialization to create the struct for Thor 2 VFs,
enabling RX/TX timestamp support. VFs on pre-Thor 2 devices remain
unaffected.

Previously, VFs lacked timestamp support, causing "RX/TX timestamp
registers not valid" errors in testpmd ieee1588 fwd mode.

RelnoteHeadline: Add PTP timestamp support for Thor 2 VFs
RelnoteDescChg: DPDK driver now creates ptp_cfg struct for Thor 2 VFs,
enabling PTP timestamp functionality in ieee1588 forwarding mode
RelnoteIssueDesc: RX/TX timestamp registers were not valid for VFs,
causing ieee1588 forwarding mode to fail on Thor 2 VFs
RelnoteVisibility: Default

Cc: stable@dpdk.org

Signed-off-by: Mohammad Shuab Siddique <root@nic1-cos.dhcp.broadcom.net>
---
 drivers/net/bnxt/bnxt_hwrm.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/net/bnxt/bnxt_hwrm.c b/drivers/net/bnxt/bnxt_hwrm.c
index 0cef22b5ec..3632bebbd6 100644
--- a/drivers/net/bnxt/bnxt_hwrm.c
+++ b/drivers/net/bnxt/bnxt_hwrm.c
@@ -1258,7 +1258,7 @@ static int __bnxt_hwrm_func_qcaps(struct bnxt *bp)
 	 * sends another hwrm msg.
 	 */
 	if (flags & HWRM_FUNC_QCAPS_OUTPUT_FLAGS_PTP_SUPPORTED) {
-		if (BNXT_CHIP_P5(bp) || BNXT_PF(bp)) {
+		if (BNXT_CHIP_P5_P7(bp) || BNXT_PF(bp)) {
 			bp->flags |= BNXT_FLAG_PTP_SUPPORTED;
 			PMD_DRV_LOG_LINE(DEBUG, "PTP SUPPORTED");
 			HWRM_UNLOCK();
-- 
2.47.3


  parent reply	other threads:[~2026-03-02 17:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-02 17:12 [PATCH 0/4] net/bnxt: PTP support series Mohammad Shuab Siddique
2026-03-02 17:12 ` [PATCH 1/4] net/bnxt: support handling PTP frames in Rx Mohammad Shuab Siddique
2026-03-02 17:12 ` [PATCH 2/4] net/bnxt: pass Rx timestamp in mbuf Mohammad Shuab Siddique
2026-03-02 17:12 ` [PATCH 3/4] net/bnxt: support timestamp parsing in Tx Mohammad Shuab Siddique
2026-03-02 17:12 ` Mohammad Shuab Siddique [this message]
2026-03-02 17:26   ` [PATCH v2 4/4] net/bnxt: add ptp_cfg struct support for Thor 2 VFs Mohammad Shuab Siddique
2026-03-11 18:29 ` [PATCH 0/4] net/bnxt: PTP support series Thomas Monjalon

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=20260302171236.98625-5-Mohammad-Shuab.Siddique@broadcom.com \
    --to=mohammad-shuab.siddique@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=kishore.padmanabha@broadcom.com \
    --cc=root@nic1-cos.dhcp.broadcom.net \
    --cc=stable@dpdk.org \
    /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