From: Nicolas Chautru <nicolas.chautru@intel.com>
To: dev@dpdk.org, maxime.coquelin@redhat.com
Cc: hemant.agrawal@nxp.com, david.marchand@redhat.com,
hernan.vargas@intel.com,
Nicolas Chautru <nicolas.chautru@intel.com>
Subject: [PATCH v1 0/7] VRB2 BBDEV PMD introduction
Date: Tue, 19 Sep 2023 01:21:29 +0000 [thread overview]
Message-ID: <20230919012136.2818396-1-nicolas.chautru@intel.com> (raw)
This serie includes includes changes to the VRB BBDEV PMD for 23.11.
This relies on the previous serie that Maxime is about to apply
(https://patches.dpdk.org/project/dpdk/list/?series=28544).
I did not include documentationa just yet but I will in next revision.
This allows the VRB unified driver to support the new VRB2
implementation variant on GNR-D.
This also include minor change to the dev_info to expose FFT version
flexibility to expose information to the application on what is
configured dynamically on the device.
Nicolas Chautru (7):
bbdev: add FFT version member in driver info
baseband/acc: add FFT version in the VRM PMD
baseband/acc: remove the 4G SO capability for VRB1
baseband/acc: allocate FCW memory separately
baseband/acc: add support for MLD operation
baseband/acc: introduce the new VRB2 variant
baseband/acc: add configure helper for VRB2
drivers/baseband/acc/acc100_pmd.h | 2 +
drivers/baseband/acc/acc_common.h | 97 +-
drivers/baseband/acc/rte_acc100_pmd.c | 10 +-
drivers/baseband/acc/rte_vrb_pmd.c | 1967 ++++++++++++++++++++++---
drivers/baseband/acc/vrb1_pf_enum.h | 17 +-
drivers/baseband/acc/vrb2_pf_enum.h | 124 ++
drivers/baseband/acc/vrb2_vf_enum.h | 121 ++
drivers/baseband/acc/vrb_cfg.h | 16 +
drivers/baseband/acc/vrb_pmd.h | 173 ++-
lib/bbdev/rte_bbdev.h | 2 +
10 files changed, 2297 insertions(+), 232 deletions(-)
create mode 100644 drivers/baseband/acc/vrb2_pf_enum.h
create mode 100644 drivers/baseband/acc/vrb2_vf_enum.h
--
2.34.1
next reply other threads:[~2023-09-19 1:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 1:21 Nicolas Chautru [this message]
2023-09-19 1:21 ` [PATCH v1 1/7] bbdev: add FFT version member in driver info Nicolas Chautru
2023-09-19 9:55 ` Maxime Coquelin
2023-09-19 20:51 ` Chautru, Nicolas
2023-09-22 8:14 ` Maxime Coquelin
2023-09-22 16:41 ` Chautru, Nicolas
2023-09-26 10:00 ` Maxime Coquelin
2023-09-27 23:50 ` Chautru, Nicolas
2023-09-28 8:27 ` Maxime Coquelin
2023-09-28 16:33 ` Chautru, Nicolas
2023-10-03 11:46 ` Maxime Coquelin
2023-09-19 1:21 ` [PATCH v1 2/7] baseband/acc: add FFT version in the VRM PMD Nicolas Chautru
2023-09-19 1:21 ` [PATCH v1 3/7] baseband/acc: remove the 4G SO capability for VRB1 Nicolas Chautru
2023-09-19 15:20 ` David Marchand
2023-09-19 20:32 ` Chautru, Nicolas
2023-09-21 7:13 ` David Marchand
2023-09-21 17:18 ` Chautru, Nicolas
2023-09-27 7:08 ` Maxime Coquelin
2023-09-27 7:32 ` Maxime Coquelin
2023-09-19 1:21 ` [PATCH v1 4/7] baseband/acc: allocate FCW memory separately Nicolas Chautru
2023-09-19 1:21 ` [PATCH v1 5/7] baseband/acc: add support for MLD operation Nicolas Chautru
2023-09-19 1:21 ` [PATCH v1 6/7] baseband/acc: introduce the new VRB2 variant Nicolas Chautru
2023-09-19 1:21 ` [PATCH v1 7/7] baseband/acc: add configure helper for VRB2 Nicolas Chautru
2023-09-21 7:25 ` [PATCH v1 0/7] VRB2 BBDEV PMD introduction David Marchand
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=20230919012136.2818396-1-nicolas.chautru@intel.com \
--to=nicolas.chautru@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=hernan.vargas@intel.com \
--cc=maxime.coquelin@redhat.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).