DPDK patches and discussions
 help / color / mirror / Atom feed
From: Nicolas Chautru <nicolas.chautru@intel.com>
To: dev@dpdk.org, gakhil@marvell.com, nipun.gupta@nxp.com, trix@redhat.com
Cc: thomas@monjalon.net, mingshan.zhang@intel.com,
	arun.joshi@intel.com, hemant.agrawal@nxp.com,
	david.marchand@redhat.com,
	Nicolas Chautru <nicolas.chautru@intel.com>
Subject: [dpdk-dev] [PATCH v9] bbdev: add device info related to data endianness assumption
Date: Wed,  6 Oct 2021 13:58:48 -0700	[thread overview]
Message-ID: <1633553929-58670-1-git-send-email-nicolas.chautru@intel.com> (raw)

Suggesting this bbdev api change attached to address the requirement for the new
bbdev PMD from this serie : https://patches.dpdk.org/project/dpdk/patch/20211006113112.11163-2-nipun.gupta@nxp.com/
Nipin, please review and you can use this one in case that is okay with you.
This is defined as an enum and default values set in existing PMDs.

Nicolas Chautru (1):
  bbdev: add device info related to data endianness assumption

 doc/guides/rel_notes/release_21_11.rst             | 1 +
 drivers/baseband/acc100/rte_acc100_pmd.c           | 1 +
 drivers/baseband/fpga_5gnr_fec/rte_fpga_5gnr_fec.c | 1 +
 drivers/baseband/fpga_lte_fec/fpga_lte_fec.c       | 1 +
 drivers/baseband/turbo_sw/bbdev_turbo_software.c   | 1 +
 lib/bbdev/rte_bbdev.h                              | 8 ++++++++
 6 files changed, 13 insertions(+)

-- 
1.8.3.1


             reply	other threads:[~2021-10-06 20:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-06 20:58 Nicolas Chautru [this message]
2021-10-06 20:58 ` Nicolas Chautru
2021-10-07 12:01   ` Tom Rix
2021-10-07 15:19     ` Chautru, Nicolas
2021-10-07 13:13   ` [dpdk-dev] [EXT] " Akhil Goyal
2021-10-07 15:41     ` Chautru, Nicolas
2021-10-07 16:49       ` Nipun Gupta
2021-10-07 18:58         ` Chautru, Nicolas
2021-10-08  4:34           ` Nipun Gupta
2021-10-07  2:22 ` [dpdk-dev] " Nipun 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=1633553929-58670-1-git-send-email-nicolas.chautru@intel.com \
    --to=nicolas.chautru@intel.com \
    --cc=arun.joshi@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=mingshan.zhang@intel.com \
    --cc=nipun.gupta@nxp.com \
    --cc=thomas@monjalon.net \
    --cc=trix@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).