linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Devesh Sharma <devesh.sharma@broadcom.com>
To: dledford@redhat.com, jgg@mellanox.com, leonro@mellanox.com
Cc: nmoreychaisemartin@suse.com, linux-rdma@vger.kernel.org,
	Luke Starrett <luke.starrett@broadcom.com>,
	Devesh Sharma <devesh.sharma@broadcom.com>
Subject: [PATCH rdma-core 2/2] bnxt_re/lib: Recognize additional 5750x device ID's
Date: Wed, 27 Nov 2019 05:43:35 -0500	[thread overview]
Message-ID: <1574851415-4407-3-git-send-email-devesh.sharma@broadcom.com> (raw)
In-Reply-To: <1574851415-4407-1-git-send-email-devesh.sharma@broadcom.com>

From: Luke Starrett <luke.starrett@broadcom.com>

BCM5750x family includes 57504 and 57502. Until recently the chip_num
register always conveyed 0x1750 (57508). Recent devices properly
reflect the SKU in the chip_num register. Update Phase5 checks to
reflect this.

Signed-off-by: Luke Starrett <luke.starrett@broadcom.com>
Signed-off-by: Devesh Sharma <devesh.sharma@broadcom.com>
---
 providers/bnxt_re/main.c | 6 ++++--
 providers/bnxt_re/main.h | 5 ++++-
 2 files changed, 8 insertions(+), 3 deletions(-)

diff --git a/providers/bnxt_re/main.c b/providers/bnxt_re/main.c
index e290a07..803eff7 100644
--- a/providers/bnxt_re/main.c
+++ b/providers/bnxt_re/main.c
@@ -75,7 +75,7 @@ static const struct verbs_match_ent cna_table[] = {
 	CNA(BROADCOM, 0x16EF),  /* BCM57416 NPAR */
 	CNA(BROADCOM, 0x16F0),  /* BCM58730 */
 	CNA(BROADCOM, 0x16F1),  /* BCM57452 */
-	CNA(BROADCOM, 0x1750),	/* BCM57500 */
+	CNA(BROADCOM, 0x1750),	/* BCM57508 */
 	CNA(BROADCOM, 0x1751),	/* BCM57504 */
 	CNA(BROADCOM, 0x1752),	/* BCM57502 */
 	CNA(BROADCOM, 0x1803),	/* BCM57508 NPAR */
@@ -118,7 +118,9 @@ static const struct verbs_context_ops bnxt_re_cntx_ops = {
 
 bool bnxt_re_is_chip_gen_p5(struct bnxt_re_chip_ctx *cctx)
 {
-	return cctx->chip_num == CHIP_NUM_57500;
+	return (cctx->chip_num == CHIP_NUM_57508 ||
+		cctx->chip_num == CHIP_NUM_57504 ||
+		cctx->chip_num == CHIP_NUM_57502);
 }
 
 /* Context Init functions */
diff --git a/providers/bnxt_re/main.h b/providers/bnxt_re/main.h
index be57349..368297e 100644
--- a/providers/bnxt_re/main.h
+++ b/providers/bnxt_re/main.h
@@ -56,7 +56,10 @@
 
 #define BNXT_RE_UD_QP_HW_STALL	0x400000
 
-#define CHIP_NUM_57500		0x1750
+#define CHIP_NUM_57508		0x1750
+#define CHIP_NUM_57504		0x1751
+#define CHIP_NUM_57502		0x1752
+
 struct bnxt_re_chip_ctx {
 	__u16 chip_num;
 	__u8 chip_rev;
-- 
1.8.3.1


      parent reply	other threads:[~2019-11-27 10:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-27 10:43 [PATCH rdma-core 0/2] bnxt_re/lib: libbnxt_re bug fixes Devesh Sharma
2019-11-27 10:43 ` [PATCH rdma-core 1/2] bnxt_re/lib: Add remaining pci ids for gen P5 devices Devesh Sharma
2019-11-27 10:43 ` Devesh Sharma [this message]

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=1574851415-4407-3-git-send-email-devesh.sharma@broadcom.com \
    --to=devesh.sharma@broadcom.com \
    --cc=dledford@redhat.com \
    --cc=jgg@mellanox.com \
    --cc=leonro@mellanox.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=luke.starrett@broadcom.com \
    --cc=nmoreychaisemartin@suse.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).