From: Dave Jiang <dave.jiang@intel.com>
To: Frank.Li@oss.nxp.com, 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>
Subject: Re: [PATCH 0/6] async_tx: use DMA Engine APIs
Date: Thu, 15 Oct 2026 11:26:38 -0700 [thread overview]
Message-ID: <959bd30e-f8b8-4beb-bd2e-5195bf5e9ad5@intel.com> (raw)
In-Reply-To: <20261014-async_tx_dma-v1-0-35790d01e190@nxp.com>
On 10/14/26 12:43 PM, Frank.Li@oss.nxp.com wrote:
> 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
>
> Signed-off-by: Frank Li <Frank.Li@nxp.com>
For the series:
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
> ---
> Frank Li (6):
> 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 | 19 ++++----------
> crypto/async_tx/async_xor.c | 50 +++++++++++++++++--------------------
> include/linux/async_tx.h | 8 ++----
> 7 files changed, 65 insertions(+), 86 deletions(-)
> ---
> base-commit: 547cb54c6fd39a610130c0beb2d85489bc914ea7
> change-id: 20261014-async_tx_dma-4f69bf80176f
>
> Best regards,
> --
> Frank Li <Frank.Li@nxp.com>
>
>
prev parent reply other threads:[~2026-10-15 18:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 19:43 Frank.Li
2026-10-14 19:43 ` [PATCH 1/6] async_tx: replace direct ->device_prep*() calls with standard DMA engine API Frank.Li
2026-10-15 11:09 ` Peng Fan
2026-10-14 19:43 ` [PATCH 2/6] async_tx: use dmaengine_get_dma_device() instead of chan->device->dev Frank.Li
2026-10-15 11:10 ` Peng Fan
2026-10-14 19:43 ` [PATCH 3/6] async_tx: use dmaengine_prep_dma_(pq|pq_val|interrupt|xor) instead of direct callback Frank.Li
2026-10-15 11:11 ` Peng Fan
2026-10-14 19:43 ` [PATCH 4/6] async_tx: convert to dmaengine_is_*_aligned() helpers Frank.Li
2026-10-15 11:11 ` Peng Fan
2026-10-14 19:43 ` [PATCH 5/6] async_tx: replace open-coded cap_mask accesses with dmaengine_has_cap() Frank.Li
2026-10-15 11:12 ` Peng Fan
2026-10-14 19:43 ` [PATCH 6/6] async_tx: Mark as Deprecated in Kconfig Frank.Li
2026-10-15 20:51 ` Eric Biggers
2026-10-15 21:17 ` Frank Li
2026-10-15 18:26 ` Dave Jiang [this message]
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=959bd30e-f8b8-4beb-bd2e-5195bf5e9ad5@intel.com \
--to=dave.jiang@intel.com \
--cc=Frank.Li@nxp.com \
--cc=Frank.Li@oss.nxp.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=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®