From: Nicolas Chautru <nicolas.chautru@intel.com>
To: dev@dpdk.org, gakhil@marvell.com, maxime.coquelin@redhat.com,
thomas@monjalon.net
Cc: hemant.agrawal@nxp.com, hernan.vargas@intel.com, g.singh@nxp.com,
david.marchand@redhat.com,
Nicolas Chautru <nicolas.chautru@intel.com>
Subject: [RFC 0/1] baseband PMD API
Date: Thu, 13 Oct 2022 18:42:04 -0700 [thread overview]
Message-ID: <20221014014205.38074-1-nicolas.chautru@intel.com> (raw)
Option to move PMD API into bbdev API.
For discussion only, not yet sure this is the
right way to go.
Nicolas Chautru (1):
bbdev: device PF initialization helper through bbdev API
app/test-bbdev/test_bbdev_perf.c | 10 +-
drivers/baseband/acc/acc100_pmd.h | 1 -
drivers/baseband/acc/acc200_cfg.h | 32 --
drivers/baseband/acc/acc200_pmd.h | 1 -
drivers/baseband/acc/meson.build | 2 +-
drivers/baseband/acc/rte_acc100_pmd.c | 308 +++++++++---------
drivers/baseband/acc/rte_acc200_pmd.c | 256 +++++++--------
drivers/baseband/acc/rte_acc_cfg.h | 49 ---
drivers/baseband/acc/rte_acc_common_cfg.h | 15 +-
drivers/baseband/acc/version.map | 6 -
.../fpga_5gnr_fec/rte_fpga_5gnr_fec.c | 206 ++++++------
.../fpga_5gnr_fec/rte_pmd_fpga_5gnr_fec.h | 35 +-
drivers/baseband/fpga_5gnr_fec/version.map | 7 -
drivers/baseband/fpga_lte_fec/fpga_lte_fec.c | 202 ++++++------
drivers/baseband/fpga_lte_fec/fpga_lte_fec.h | 35 +-
drivers/baseband/fpga_lte_fec/version.map | 7 -
lib/bbdev/rte_bbdev.c | 20 ++
lib/bbdev/rte_bbdev.h | 17 +
lib/bbdev/rte_bbdev_pmd.h | 10 +
lib/bbdev/version.map | 1 +
20 files changed, 535 insertions(+), 685 deletions(-)
delete mode 100644 drivers/baseband/acc/acc200_cfg.h
delete mode 100644 drivers/baseband/acc/rte_acc_cfg.h
--
2.37.1
next reply other threads:[~2022-10-14 1:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 1:42 Nicolas Chautru [this message]
2022-10-14 1:42 ` [RFC 1/1] bbdev: device PF initialization helper through bbdev API Nicolas Chautru
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=20221014014205.38074-1-nicolas.chautru@intel.com \
--to=nicolas.chautru@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=g.singh@nxp.com \
--cc=gakhil@marvell.com \
--cc=hemant.agrawal@nxp.com \
--cc=hernan.vargas@intel.com \
--cc=maxime.coquelin@redhat.com \
--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).