From: Raslan Darawsheh <rasland@nvidia.com>
To: <thomas@monjalon.net>
Cc: <dev@dpdk.org>
Subject: [PATCH] common/mlx5: add BlueField-4 DPU
Date: Tue, 11 Nov 2025 14:16:28 +0200 [thread overview]
Message-ID: <20251111121628.75282-1-rasland@nvidia.com> (raw)
This adds the BlueField-4 device ID to the list of
supported NVIDIA devices that run the mlx5 drivers.
The device is still in development stage.
Signed-off-by: Raslan Darawsheh <rasland@nvidia.com>
---
drivers/common/mlx5/mlx5_common.h | 1 +
drivers/crypto/mlx5/mlx5_crypto.c | 4 ++++
drivers/net/mlx5/mlx5.c | 4 ++++
3 files changed, 9 insertions(+)
diff --git a/drivers/common/mlx5/mlx5_common.h b/drivers/common/mlx5/mlx5_common.h
index bd8b5add24..6f82b8d8b5 100644
--- a/drivers/common/mlx5/mlx5_common.h
+++ b/drivers/common/mlx5/mlx5_common.h
@@ -155,6 +155,7 @@ enum {
PCI_DEVICE_ID_MELLANOX_BLUEFIELD3 = 0Xa2dc,
PCI_DEVICE_ID_MELLANOX_CONNECTX8 = 0x1023,
PCI_DEVICE_ID_MELLANOX_CONNECTX9 = 0x1025,
+ PCI_DEVICE_ID_MELLANOX_BLUEFIELD4 = 0Xa2df,
};
/* Maximum number of simultaneous unicast MAC addresses. */
diff --git a/drivers/crypto/mlx5/mlx5_crypto.c b/drivers/crypto/mlx5/mlx5_crypto.c
index 2699253d87..240e8bb858 100644
--- a/drivers/crypto/mlx5/mlx5_crypto.c
+++ b/drivers/crypto/mlx5/mlx5_crypto.c
@@ -491,6 +491,10 @@ static const struct rte_pci_id mlx5_crypto_pci_id_map[] = {
RTE_PCI_DEVICE(PCI_VENDOR_ID_MELLANOX,
PCI_DEVICE_ID_MELLANOX_CONNECTX9)
},
+ {
+ RTE_PCI_DEVICE(PCI_VENDOR_ID_MELLANOX,
+ PCI_DEVICE_ID_MELLANOX_BLUEFIELD4)
+ },
{
.vendor_id = 0
}
diff --git a/drivers/net/mlx5/mlx5.c b/drivers/net/mlx5/mlx5.c
index 666216c21a..bdb2f57fb7 100644
--- a/drivers/net/mlx5/mlx5.c
+++ b/drivers/net/mlx5/mlx5.c
@@ -3819,6 +3819,10 @@ static const struct rte_pci_id mlx5_pci_id_map[] = {
RTE_PCI_DEVICE(PCI_VENDOR_ID_MELLANOX,
PCI_DEVICE_ID_MELLANOX_CONNECTX9)
},
+ {
+ RTE_PCI_DEVICE(PCI_VENDOR_ID_MELLANOX,
+ PCI_DEVICE_ID_MELLANOX_BLUEFIELD4)
+ },
{
.vendor_id = 0
}
--
2.50.1 (Apple Git-155)
reply other threads:[~2025-11-11 12:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20251111121628.75282-1-rasland@nvidia.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).