From: Miquel Raynal <miquel.raynal@bootlin.com>
To: "Vignesh Raghavendra" <vigneshr@ti.com>,
"Tudor Ambarus" <tudor.ambarus@linaro.org>,
"Richard Weinberger" <richard@nod.at>,
"Keguang Zhang" <keguang.zhang@gmail.com>,
"Vladimir Zapolskiy" <vz@mleia.com>,
"Piotr Wojtaszczyk" <piotr.wojtaszczyk@timesys.com>,
"Niravkumar L Rabara" <niravkumarlaxmidas.rabara@altera.com>,
"Alok Tiwari" <alok.a.tiwari@oracle.com>,
"Chen Ni" <nichen@iscas.ac.cn>,
"Runyu Xiao" <runyu.xiao@seu.edu.cn>,
"Frank Li" <Frank.Li@nxp.com>,
"Pengpeng Hou" <pengpeng@iscas.ac.cn>,
"Haotian Zhang" <vulab@iscas.ac.cn>,
"Johan Hovold" <johan@kernel.org>,
"Uwe Kleine-König (The Capable Hub)"
<u.kleine-koenig@baylibre.com>, "Rosen Penev" <rosenp@gmail.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-mips@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Frank.Li@oss.nxp.com
Cc: imx@lists.linux.dev, vkoul@kernel.org
Subject: Re: [PATCH 1/1] mtd: use dmaengine_get_dma_device() instead of chan->device->dev
Date: Fri, 25 Sep 2026 16:28:55 +0200 [thread overview]
Message-ID: <179034653501.1166139.9018677426507757712.b4-ty@bootlin.com> (raw)
In-Reply-To: <20260917204724.1289912-1-Frank.Li@oss.nxp.com>
On Thu, 17 Sep 2026 16:47:06 -0400, Frank.Li@oss.nxp.com wrote:
> 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.
>
> [...]
Applied to mtd/next, thanks!
[1/1] mtd: use dmaengine_get_dma_device() instead of chan->device->dev
commit: a018524a2ec96da5bb1965053967a20e0069ed9e
Patche(s) should be available on mtd/linux.git and will be
part of the next PR (provided that no robot complains by then).
Kind regards,
Miquèl
prev parent reply other threads:[~2026-09-25 14:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 20:47 Frank.Li
2026-09-25 14:28 ` Miquel Raynal [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=179034653501.1166139.9018677426507757712.b4-ty@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=Frank.Li@nxp.com \
--cc=Frank.Li@oss.nxp.com \
--cc=alok.a.tiwari@oracle.com \
--cc=imx@lists.linux.dev \
--cc=johan@kernel.org \
--cc=keguang.zhang@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=nichen@iscas.ac.cn \
--cc=niravkumarlaxmidas.rabara@altera.com \
--cc=pengpeng@iscas.ac.cn \
--cc=piotr.wojtaszczyk@timesys.com \
--cc=richard@nod.at \
--cc=rosenp@gmail.com \
--cc=runyu.xiao@seu.edu.cn \
--cc=tudor.ambarus@linaro.org \
--cc=u.kleine-koenig@baylibre.com \
--cc=vigneshr@ti.com \
--cc=vkoul@kernel.org \
--cc=vulab@iscas.ac.cn \
--cc=vz@mleia.com \
/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®