DPDK patches and discussions
 help / color / mirror / Atom feed
From: <pbhagavatula@marvell.com>
To: <jerinj@marvell.com>
Cc: <vattunuru@marvell.com>, <g.singh@nxp.com>,
	<sachin.saxena@nxp.com>, <hemant.agrawal@nxp.com>,
	<fengchengwen@huawei.com>, <bruce.richardson@intel.com>,
	<kevin.laatz@intel.com>, <conor.walsh@intel.com>,
	<gmuthukrishn@marvell.com>, <vvelumuri@marvell.com>,
	<anatoly.burakov@intel.com>, <dev@dpdk.org>,
	Pavan Nikhilesh <pbhagavatula@marvell.com>
Subject: [PATCH] doc: announce DMA configuration structure changes
Date: Wed, 16 Apr 2025 16:35:41 +0530	[thread overview]
Message-ID: <20250416110541.10358-1-pbhagavatula@marvell.com> (raw)

From: Pavan Nikhilesh <pbhagavatula@marvell.com>

Deprecate rte_dma_conf structure to allow for a more flexible
configuration of DMA devices.
The new structure will have a flags field instead of multiple
boolean fields for each feature.

Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
---
 doc/guides/rel_notes/deprecation.rst | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 36489f6e68..854db96c08 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -142,3 +142,9 @@ Deprecation Notices
 * bus/vmbus: Starting DPDK 25.11, all the vmbus API defined in
   ``drivers/bus/vmbus/rte_bus_vmbus.h`` will become internal to DPDK.
   Those API functions are used internally by DPDK core and netvsc PMD.
+
+* dmadev: The ``rte_dma_conf`` structure is updated to include a new field
+  ``rte_dma_conf::flags`` that should be used to configure dmadev features.
+  The existing field ``rte_dma_conf::enable_silent`` is removed and replaced
+  with the new flag ``RTE_DMA_CFG_FLAG_SILENT``, to configure silent mode
+  the flag should be set in ``rte_dma_conf::flags`` during device configuration.
-- 
2.43.0


                 reply	other threads:[~2025-04-16 11:06 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=20250416110541.10358-1-pbhagavatula@marvell.com \
    --to=pbhagavatula@marvell.com \
    --cc=anatoly.burakov@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=conor.walsh@intel.com \
    --cc=dev@dpdk.org \
    --cc=fengchengwen@huawei.com \
    --cc=g.singh@nxp.com \
    --cc=gmuthukrishn@marvell.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=jerinj@marvell.com \
    --cc=kevin.laatz@intel.com \
    --cc=sachin.saxena@nxp.com \
    --cc=vattunuru@marvell.com \
    --cc=vvelumuri@marvell.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).