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>
Subject: [PATCH 6/6] async_tx: Mark as Deprecated in Kconfig
Date: Wed, 14 Oct 2026 15:43:50 -0400 [thread overview]
Message-ID: <20261014-async_tx_dma-v1-6-35790d01e190@nxp.com> (raw)
In-Reply-To: <20261014-async_tx_dma-v1-0-35790d01e190@nxp.com>
From: Frank Li <Frank.Li@nxp.com>
The async_tx framework was introduced to support asynchronous RAID
memory operations and DMA offload engines that were common at the time.
Today, adoption is limited, most clients use DMAEngine interfaces
directly, and the framework's dependency-chaining and software fallback
features provide little value for new users.
Maintaining async_tx adds an extra abstraction layer and ongoing
maintenance burden while serving a shrinking set of users. Deprecate the
framework and discourage new users in favor of direct DMAEngine APIs.
Signed-off-by: Frank Li <Frank.Li@nxp.com>
---
crypto/async_tx/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/crypto/async_tx/Kconfig b/crypto/async_tx/Kconfig
index 89bafa2efc300..02d472fc7a476 100644
--- a/crypto/async_tx/Kconfig
+++ b/crypto/async_tx/Kconfig
@@ -1,6 +1,6 @@
# SPDX-License-Identifier: GPL-2.0
config ASYNC_CORE
- tristate
+ tristate "Async tx core (DEPRECATED)"
config ASYNC_MEMCPY
tristate
--
2.43.0
prev parent reply other threads:[~2026-10-14 19:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 19:43 [PATCH 0/6] async_tx: use DMA Engine APIs 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-14 19:43 ` [PATCH 2/6] async_tx: use dmaengine_get_dma_device() instead of chan->device->dev Frank.Li
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-14 19:43 ` [PATCH 4/6] async_tx: convert to dmaengine_is_*_aligned() helpers Frank.Li
2026-10-14 19:43 ` [PATCH 5/6] async_tx: replace open-coded cap_mask accesses with dmaengine_has_cap() Frank.Li
2026-10-14 19:43 ` Frank.Li [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=20261014-async_tx_dma-v1-6-35790d01e190@nxp.com \
--to=frank.li@oss.nxp.com \
--cc=Frank.Li@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®