From: Frank.Li@oss.nxp.com
To: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
dmaengine@vger.kernel.org, imx@lists.linux.dev,
vkoul@kernel.org, Frank Li <Frank.Li@nxp.com>,
Peng Fan <peng.fan@nxp.com>, Dave Jiang <dave.jiang@intel.com>
Subject: [PATCH v2 0/7] async_tx: use DMA Engine APIs
Date: Tue, 03 Nov 2026 14:52:31 -0500 [thread overview]
Message-ID: <20261103-async_tx_dma-v2-0-3afc7c59362c@nxp.com> (raw)
Use DMA Engine APIs to prepare make dma_device private.
Last patch mark async_tx as deprecated.
Depend on below two patches
https://lore.kernel.org/imx/20261014190337.1718622-1-Frank.Li@oss.nxp.com/T/#u
base on https://git.kernel.org/pub/scm/linux/kernel/git/vkoul/dmaengine.git/
branch: next
Remove whole async_tx RFC patch at
https://lore.kernel.org/linux-crypto/20261015-asycn_tx_remove-v1-0-056a7085e0a1@nxp.com/
Signed-off-by: Frank Li <Frank.Li@nxp.com>
---
Changes in v2:
- Add patch to call dmaengine_set_callback()
- collect david and peng fan's review by tags
- Link to v1: https://patch.msgid.link/20261014-async_tx_dma-v1-0-35790d01e190@nxp.com
---
Frank Li (7):
async_tx: use dmaengine_desc_set_callback()
async_tx: replace direct ->device_prep*() calls with standard DMA engine API
async_tx: use dmaengine_get_dma_device() instead of chan->device->dev
async_tx: use dmaengine_prep_dma_(pq|pq_val|interrupt|xor) instead of direct callback
async_tx: convert to dmaengine_is_*_aligned() helpers
async_tx: replace open-coded cap_mask accesses with dmaengine_has_cap()
async_tx: Mark as Deprecated in Kconfig
crypto/async_tx/Kconfig | 2 +-
crypto/async_tx/async_memcpy.c | 14 +++++------
crypto/async_tx/async_pq.c | 44 ++++++++++++++++----------------
crypto/async_tx/async_raid6_recov.c | 14 +++++------
crypto/async_tx/async_tx.c | 25 ++++++-------------
crypto/async_tx/async_xor.c | 50 +++++++++++++++++--------------------
include/linux/async_tx.h | 8 ++----
7 files changed, 67 insertions(+), 90 deletions(-)
---
base-commit: a2313814224c3944419186b273c8a29e7c8c37db
change-id: 20261014-async_tx_dma-4f69bf80176f
Best regards,
--
Frank Li <Frank.Li@nxp.com>
next reply other threads:[~2026-11-03 19:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 19:52 Frank.Li [this message]
2026-11-03 19:52 ` [PATCH v2 1/7] async_tx: use dmaengine_desc_set_callback() Frank.Li
2026-11-03 19:52 ` [PATCH v2 2/7] async_tx: replace direct ->device_prep*() calls with standard DMA engine API Frank.Li
2026-11-03 19:52 ` [PATCH v2 3/7] async_tx: use dmaengine_get_dma_device() instead of chan->device->dev Frank.Li
2026-11-03 19:52 ` [PATCH v2 4/7] async_tx: use dmaengine_prep_dma_(pq|pq_val|interrupt|xor) instead of direct callback Frank.Li
2026-11-03 19:52 ` [PATCH v2 5/7] async_tx: convert to dmaengine_is_*_aligned() helpers Frank.Li
2026-11-03 19:52 ` [PATCH v2 6/7] async_tx: replace open-coded cap_mask accesses with dmaengine_has_cap() Frank.Li
2026-11-03 19:52 ` [PATCH v2 7/7] async_tx: Mark as Deprecated in Kconfig Frank.Li
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=20261103-async_tx_dma-v2-0-3afc7c59362c@nxp.com \
--to=frank.li@oss.nxp.com \
--cc=Frank.Li@nxp.com \
--cc=dave.jiang@intel.com \
--cc=davem@davemloft.net \
--cc=dmaengine@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=imx@lists.linux.dev \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=vkoul@kernel.org \
/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
all inboxes | Powered by JetHome®