From: Peng Fan <peng.fan@oss.nxp.com>
To: Frank.Li@oss.nxp.com
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
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 2/6] async_tx: use dmaengine_get_dma_device() instead of chan->device->dev
Date: Thu, 15 Oct 2026 19:10:42 +0800 [thread overview]
Message-ID: <atC0si+P094XwMXo@shlinux89> (raw)
In-Reply-To: <20261014-async_tx_dma-v1-2-35790d01e190@nxp.com>
On Wed, Oct 14, 2026 at 03:43:46PM -0400, Frank.Li@oss.nxp.com wrote:
>From: Frank Li <Frank.Li@nxp.com>
>
>Replace direct dma_chan::device::dev access with the proper
>dmaengine_get_dma_device() for consumer API.
>
>chan->device->dev is not always the device used for DMA mapping. Some DMA
>engines support per-channel IOMMU mappings, so different channels may use
>different DMA devices. dmaengine_get_dma_device() returns the correct
>device for each channel.
>
>Prepare for making the DMA engine provider data structures private. DMA
>consumers should not access DMA engine internals directly.
>
>Signed-off-by: Frank Li <Frank.Li@nxp.com>
Reviewed-by: Peng Fan <peng.fan@nxp.com>
next prev parent reply other threads:[~2026-10-15 11:06 UTC|newest]
Thread overview: 13+ 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-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 [this message]
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 18:26 ` [PATCH 0/6] async_tx: use DMA Engine APIs Dave Jiang
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=atC0si+P094XwMXo@shlinux89 \
--to=peng.fan@oss.nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.