From: Frank.Li@oss.nxp.com
To: Vinod Koul <vkoul@kernel.org>, Frank Li <Frank.Li@kernel.org>,
Dan Williams <djbw@kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>
Cc: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org, imx@lists.linux.dev,
Frank Li <Frank.Li@nxp.com>, Frank Li <frank.li@nxp.com>
Subject: [PATCH 0/3] dmaengine: Add dmaengine_prep_dma_pq(_val)() API to avoid call DMA Engine callback directly
Date: Mon, 21 Sep 2026 19:09:02 -0400 [thread overview]
Message-ID: <20260921-dmaengine_prep_dma_pq-v1-0-9563ed448260@nxp.com> (raw)
Add dmaengine_prep_dma_pq(_val)() APIs to avoid call DMA Engine callback
directly. Prepare to make dmaengine provider private.
Use dma_async_issue_pending() replace call callback.
Assisted-by: LLM
Signed-off-by: Frank Li <Frank.Li@nxp.com>
---
Frank Li (3):
dmaengine: add dmaengine_prep_dma_pq(_val)() API
async_tx: use dmaengine_prep_dma_pq(_val)() instead of direct callback
async_tx: use dma_async_issue_pending() instead of direct callback
crypto/async_tx/async_pq.c | 22 +++++++++++-----------
crypto/async_tx/async_raid6_recov.c | 8 ++++----
include/linux/async_tx.h | 8 ++------
include/linux/dmaengine.h | 25 +++++++++++++++++++++++++
4 files changed, 42 insertions(+), 21 deletions(-)
---
base-commit: 5c4d4169604b335c38bbc79bc1fc03042981fc6f
change-id: 20260921-dmaengine_prep_dma_pq-7eba91a609ed
Best regards,
--
Frank Li <Frank.Li@nxp.com>
next reply other threads:[~2026-09-21 23:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 23:09 Frank.Li [this message]
2026-09-21 23:09 ` [PATCH 1/3] dmaengine: add dmaengine_prep_dma_pq(_val)() API Frank.Li
2026-09-21 23:09 ` [PATCH 2/3] async_tx: use dmaengine_prep_dma_pq(_val)() instead of direct callback Frank.Li
2026-09-21 23:09 ` [PATCH 3/3] async_tx: use dma_async_issue_pending() " 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=20260921-dmaengine_prep_dma_pq-v1-0-9563ed448260@nxp.com \
--to=frank.li@oss.nxp.com \
--cc=Frank.Li@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=davem@davemloft.net \
--cc=djbw@kernel.org \
--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®