From: Shepard Siegel <shepard.siegel@atomicrules.com>
To: ed.czeck@atomicrules.com
Cc: dev@dpdk.org, Shepard Siegel <shepard.siegel@atomicrules.com>
Subject: [PATCH 2/2] net/ark: add new ark PCIe device
Date: Mon, 13 Feb 2023 14:58:25 -0500 [thread overview]
Message-ID: <20230213195825.2934483-2-shepard.siegel@atomicrules.com> (raw)
In-Reply-To: <20230213195825.2934483-1-shepard.siegel@atomicrules.com>
This patch adds the Arkville FX2 to known PCIe device list
Update documentation and release notes.
Signed-off-by: Shepard Siegel <shepard.siegel@atomicrules.com>
---
doc/guides/nics/ark.rst | 3 ++-
doc/guides/rel_notes/release_23_03.rst | 4 ++++
drivers/net/ark/ark_ethdev.c | 1 +
3 files changed, 7 insertions(+), 1 deletion(-)
diff --git a/doc/guides/nics/ark.rst b/doc/guides/nics/ark.rst
index 14fedbf252..81a37c161f 100644
--- a/doc/guides/nics/ark.rst
+++ b/doc/guides/nics/ark.rst
@@ -306,6 +306,7 @@ ARK PMD supports the following Arkville RTL PCIe instances including:
* ``1d6c:101c`` - AR-ARK-SRIOV-VF [Arkville Virtual Function]
* ``1d6c:101e`` - AR-ARKA-FX1 [Arkville 64B DPDK Data Mover for Agilex R-Tile]
* ``1d6c:101f`` - AR-TK242 [2x100GbE Packet Capture Device]
+* ``1d6c:1022`` - AR-ARKA-FX2 [Arkville 128B DPDK Data Mover for Agilex]
Arkville RTL Core Configurations
--------------------------------
@@ -318,6 +319,7 @@ interfaces for both AMD/Xilinx and Intel FPGAs.
* ARK-FX0 - 256-bit 32B datapath (PCIe Gen3, Gen4)
* ARK-FX1 - 512-bit 64B datapath (PCIe Gen3, Gen4, Gen5)
+* ARK-FX2 - 1024-bit 128B datapath (PCIe Gen5x16 Only)
DPDK and Arkville Firmware Versioning
-------------------------------------
@@ -350,7 +352,6 @@ Supported Features
------------------
* Dynamic ARK PMD extensions
-* Dynamic per-queue MBUF (re)sizing up to 32KB
* SR-IOV, VF-based queue-segregation
* Multiple receive and transmit queues
* Jumbo frames up to 9K
diff --git a/doc/guides/rel_notes/release_23_03.rst b/doc/guides/rel_notes/release_23_03.rst
index 7527c6d57f..7941b22c8a 100644
--- a/doc/guides/rel_notes/release_23_03.rst
+++ b/doc/guides/rel_notes/release_23_03.rst
@@ -72,6 +72,10 @@ New Features
* Added multi-process support.
+* **Updated Atomic Rules ark driver.**
+
+ * Added Arkville FX2 device supporting PCIe Gen5x16
+
* **Updated Corigine nfp driver.**
* Added support for meter options.
diff --git a/drivers/net/ark/ark_ethdev.c b/drivers/net/ark/ark_ethdev.c
index c654a229f7..b2995427c8 100644
--- a/drivers/net/ark/ark_ethdev.c
+++ b/drivers/net/ark/ark_ethdev.c
@@ -99,6 +99,7 @@ static const struct rte_pci_id pci_id_ark_map[] = {
{RTE_PCI_DEVICE(AR_VENDOR_ID, 0x101c)},
{RTE_PCI_DEVICE(AR_VENDOR_ID, 0x101e)},
{RTE_PCI_DEVICE(AR_VENDOR_ID, 0x101f)},
+ {RTE_PCI_DEVICE(AR_VENDOR_ID, 0x1022)},
{.vendor_id = 0, /* sentinel */ },
};
--
2.25.1
next prev parent reply other threads:[~2023-02-13 19:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 14:14 [PATCH 1/2] net/ark: add new device to PCIe allowlist Shepard Siegel
2023-02-11 14:14 ` [PATCH 2/2] doc: update ark guide to include new PCIe device Shepard Siegel
2023-02-13 13:46 ` [PATCH 1/2] net/ark: add new device to PCIe allowlist Ferruh Yigit
2023-02-13 15:02 ` Shepard Siegel
2023-02-13 14:58 ` [PATCH 1/4] doc: clarify the existing net/ark guide Shepard Siegel
2023-02-13 14:58 ` [PATCH 2/4] net/ark: add new device to PCIe allowlist Shepard Siegel
2023-02-13 15:51 ` Ferruh Yigit
2023-02-13 17:12 ` Shepard Siegel
2023-02-13 14:58 ` [PATCH 3/4] doc: update ark guide to include new PCIe device Shepard Siegel
2023-02-13 14:58 ` [PATCH 4/4] doc: update Release Notes Shepard Siegel
2023-02-13 15:46 ` [PATCH 1/4] doc: clarify the existing net/ark guide Ferruh Yigit
2023-02-13 17:09 ` Shepard Siegel
2023-02-13 17:23 ` Ferruh Yigit
2023-02-13 17:31 ` Shepard Siegel
2023-02-13 22:58 ` Ferruh Yigit
2023-02-13 19:58 ` [PATCH 1/2] " Shepard Siegel
2023-02-13 19:58 ` Shepard Siegel [this message]
2023-02-13 23:39 ` [PATCH 2/2] net/ark: add new ark PCIe device Ferruh Yigit
2023-02-13 23:39 ` [PATCH 1/2] doc: clarify the existing net/ark guide Ferruh Yigit
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=20230213195825.2934483-2-shepard.siegel@atomicrules.com \
--to=shepard.siegel@atomicrules.com \
--cc=dev@dpdk.org \
--cc=ed.czeck@atomicrules.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).