From: Pankaj Gupta <pagupta@vmware.com>
To: jbehrens@vmware.com, yongwang@vmware.com
Cc: dev@dpdk.org, pagupta@vmware.com
Subject: [PATCH v3 1/8] net/vmxnet3: add V5 support
Date: Wed, 4 May 2022 21:08:39 -0400 [thread overview]
Message-ID: <20220505010846.25788-2-pagupta@vmware.com> (raw)
In-Reply-To: <20220505010846.25788-1-pagupta@vmware.com>
Add VMXNET3 v5 support
Tested, using testpmd, for different hardware version on ESXi 7.0 Update 2.
Signed-off-by: Pankaj Gupta <pagupta@vmware.com>
Reviewed-by: Jochen Behrens <jbehrens@vmware.com>
---
drivers/net/vmxnet3/vmxnet3_ethdev.c | 7 +++++--
drivers/net/vmxnet3/vmxnet3_ethdev.h | 2 ++
2 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/drivers/net/vmxnet3/vmxnet3_ethdev.c b/drivers/net/vmxnet3/vmxnet3_ethdev.c
index d1ef1cad08..a7e1e5fef5 100644
--- a/drivers/net/vmxnet3/vmxnet3_ethdev.c
+++ b/drivers/net/vmxnet3/vmxnet3_ethdev.c
@@ -316,9 +316,12 @@ eth_vmxnet3_dev_init(struct rte_eth_dev *eth_dev)
/* Check h/w version compatibility with driver. */
ver = VMXNET3_READ_BAR1_REG(hw, VMXNET3_REG_VRRS);
- PMD_INIT_LOG(DEBUG, "Hardware version : %d", ver);
- if (ver & (1 << VMXNET3_REV_4)) {
+ if (ver & (1 << VMXNET3_REV_5)) {
+ VMXNET3_WRITE_BAR1_REG(hw, VMXNET3_REG_VRRS,
+ 1 << VMXNET3_REV_5);
+ hw->version = VMXNET3_REV_5 + 1;
+ } else if (ver & (1 << VMXNET3_REV_4)) {
VMXNET3_WRITE_BAR1_REG(hw, VMXNET3_REG_VRRS,
1 << VMXNET3_REV_4);
hw->version = VMXNET3_REV_4 + 1;
diff --git a/drivers/net/vmxnet3/vmxnet3_ethdev.h b/drivers/net/vmxnet3/vmxnet3_ethdev.h
index ef858ac951..7ec3b2e1f0 100644
--- a/drivers/net/vmxnet3/vmxnet3_ethdev.h
+++ b/drivers/net/vmxnet3/vmxnet3_ethdev.h
@@ -124,11 +124,13 @@ struct vmxnet3_hw {
UPT1_RxStats snapshot_rx_stats[VMXNET3_MAX_RX_QUEUES];
};
+#define VMXNET3_REV_5 4 /* Vmxnet3 Rev. 5 */
#define VMXNET3_REV_4 3 /* Vmxnet3 Rev. 4 */
#define VMXNET3_REV_3 2 /* Vmxnet3 Rev. 3 */
#define VMXNET3_REV_2 1 /* Vmxnet3 Rev. 2 */
#define VMXNET3_REV_1 0 /* Vmxnet3 Rev. 1 */
+#define VMXNET3_VERSION_GE_5(hw) ((hw)->version >= VMXNET3_REV_5 + 1)
#define VMXNET3_VERSION_GE_4(hw) ((hw)->version >= VMXNET3_REV_4 + 1)
#define VMXNET3_VERSION_GE_3(hw) ((hw)->version >= VMXNET3_REV_3 + 1)
#define VMXNET3_VERSION_GE_2(hw) ((hw)->version >= VMXNET3_REV_2 + 1)
--
2.17.1
next prev parent reply other threads:[~2022-05-05 1:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 1:08 [PATCH v3 0/8] vmxnet3 version V5 and V6 Pankaj Gupta
2022-05-05 1:08 ` Pankaj Gupta [this message]
2022-05-05 1:08 ` [PATCH v3 2/8] net/vmxnet3: implement reta query and reta update Pankaj Gupta
2022-05-05 1:08 ` [PATCH v3 3/8] net/vmxnet3: add Rx queue usage count utility Pankaj Gupta
2022-05-05 1:08 ` [PATCH v3 4/8] net/vmxnet3: report HW version on FW version get Pankaj Gupta
2022-05-05 1:08 ` [PATCH v3 5/8] net/vmxnet3: version 6 Pankaj Gupta
2022-05-05 1:08 ` [PATCH v3 6/8] net/vmxnet3: advertise RETA size in device info Pankaj Gupta
2022-05-05 1:08 ` [PATCH v3 7/8] net/vmxnet3: set packet type for fragmented packet Pankaj Gupta
2022-05-05 1:08 ` [PATCH v3 8/8] net/vmxnet3: fix merge error in initialization for rxDataRing feature Pankaj Gupta
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=20220505010846.25788-2-pagupta@vmware.com \
--to=pagupta@vmware.com \
--cc=dev@dpdk.org \
--cc=jbehrens@vmware.com \
--cc=yongwang@vmware.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).