From: Frank Li <Frank.Li@nxp.com>
To: Rob Herring <robh@kernel.org>,
Saravana Kannan <saravanak@google.com>,
Vinod Koul <vkoul@kernel.org>, Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>
Cc: dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
Shawn Guo <shawn.guo@freescale.com>, Frank Li <Frank.Li@nxp.com>,
Jindong Yue <jindong.yue@nxp.com>
Subject: [PATCH 07/13] dmaengine: mxs-dma: Turn MXS_DMA as tristate
Date: Wed, 14 Jan 2026 17:33:19 -0500 [thread overview]
Message-ID: <20260114-mxsdma-module-v1-7-9b2a9eaa4226@nxp.com> (raw)
In-Reply-To: <20260114-mxsdma-module-v1-0-9b2a9eaa4226@nxp.com>
From: Jindong Yue <jindong.yue@nxp.com>
Use tristate for mxs-dma to support module building.
Signed-off-by: Jindong Yue <jindong.yue@nxp.com>
Signed-off-by: Frank Li <Frank.Li@nxp.com>
---
drivers/dma/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/dma/Kconfig b/drivers/dma/Kconfig
index 8bb0a119ecd48a6695404d43fce225987c9c69ff..b1c2d0fd0836edec9f9b6868e020310f50bba63c 100644
--- a/drivers/dma/Kconfig
+++ b/drivers/dma/Kconfig
@@ -505,7 +505,7 @@ config MV_XOR_V2
platforms.
config MXS_DMA
- bool "MXS DMA support"
+ tristate "MXS DMA support"
depends on ARCH_MXS || ARCH_MXC || COMPILE_TEST
select STMP_DEVICE
select DMA_ENGINE
--
2.34.1
next prev parent reply other threads:[~2026-01-14 22:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 22:33 [PATCH 00/13] dmaegnine: freescale-dmas: small improvement Frank Li
2026-01-14 22:33 ` [PATCH 01/13] dmaengine: of_dma: Add devm_of_dma_controller_register() Frank Li
2026-01-15 8:44 ` Daniel Baluta
2026-01-15 10:45 ` kernel test robot
2026-01-15 11:29 ` kernel test robot
2026-01-14 22:33 ` [PATCH 02/13] dmaengine: mxs-dma: Use local dev variable in probe() Frank Li
2026-01-14 23:27 ` Fabio Estevam
2026-01-15 14:35 ` Frank Li
2026-01-14 22:33 ` [PATCH 03/13] dmaengine: mxs-dma: Fix missing return value from of_dma_controller_register() Frank Li
2026-01-15 8:45 ` Daniel Baluta
2026-01-14 22:33 ` [PATCH 04/13] dmaengine: mxs-dma: Use dev_err_probe() simple code Frank Li
2026-01-14 22:33 ` [PATCH 05/13] dmaengine: mxs-dma: Use managed API devm_of_dma_controller_register() Frank Li
2026-01-14 22:33 ` [PATCH 06/13] dmaengine: mxs-dma: Add module license and description Frank Li
2026-01-14 22:33 ` Frank Li [this message]
2026-01-14 22:33 ` [PATCH 08/13] dmaengine: fsl-edma: Use managed API dmaenginem_async_device_register() Frank Li
2026-01-14 22:33 ` [PATCH 09/13] dmaengine: fsl-edma: Use dev_err_probe() to simplify code Frank Li
2026-01-14 22:33 ` [PATCH 10/13] dmaengine: imx-sdma: Use devm_clk_get_prepared() " Frank Li
2026-01-14 22:33 ` [PATCH 11/13] dmaengine: imx-sdma: Use managed API " Frank Li
2026-01-14 22:33 ` [PATCH 12/13] dmaengine: imx-sdma: Use dev_err_probe() " Frank Li
2026-01-14 22:33 ` [PATCH 13/13] dmaengine: fsl-qdma: " 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=20260114-mxsdma-module-v1-7-9b2a9eaa4226@nxp.com \
--to=frank.li@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=jindong.yue@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=saravanak@google.com \
--cc=shawn.guo@freescale.com \
--cc=shawnguo@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