From: Jelly Jia <Jelly.Jia@cixtech.com>
To: vkoul@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, robin.murphy@arm.com
Cc: devicetree@vger.kernel.org, Frank.Li@kernel.org,
cix-kernel-upstream@cixtech.com, dmaengine@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Jelly.Jia@cixtech.com
Subject: [PATCH v3 5/6] dmaengine: arm-dma350: Support integration clocks, resets and reserved memory
Date: Mon, 12 Oct 2026 16:41:54 +0800 [thread overview]
Message-ID: <20261012084155.2547480-6-Jelly.Jia@cixtech.com> (raw)
In-Reply-To: <20261012084155.2547480-1-Jelly.Jia@cixtech.com>
SoC integrations of the DMA-350 gate the controller with a clock and may
hold it in reset until the driver brings it up, and a DMA master which
cannot reach all of system memory may have a reserved memory region
attached to it. Bring the controller up with these resources: enable
the clock, release the reset, and attach the reserved memory region when
the device tree provides one.
The integration is described entirely by the device tree; the driver
contains no SoC-specific code.
v2 -> v3:
- The patch no longer carries CIX Sky1 match data, the interrupt router
handling or the system resume hook: the Sky1 interrupt gate is set up
by the boot firmware and is not configured by Linux.
- of_reserved_mem_device_release() is now also called when the DMA
device or the OF DMA controller registration fails.
Assisted-by: LLM checkpatch sparse dt_binding_check dtbs_check
Signed-off-by: Jelly Jia <Jelly.Jia@cixtech.com>
---
drivers/dma/arm-dma350.c | 35 +++++++++++++++++++++++++++++++++--
1 file changed, 33 insertions(+), 2 deletions(-)
diff --git a/drivers/dma/arm-dma350.c b/drivers/dma/arm-dma350.c
index 79bd6a04ea0c..d811a0dc9fe9 100644
--- a/drivers/dma/arm-dma350.c
+++ b/drivers/dma/arm-dma350.c
@@ -4,14 +4,17 @@
#include <linux/bitfield.h>
#include <linux/bitops.h>
+#include <linux/clk.h>
#include <linux/dmaengine.h>
#include <linux/dma-mapping.h>
#include <linux/io.h>
#include <linux/of.h>
#include <linux/of_dma.h>
+#include <linux/of_reserved_mem.h>
#include <linux/module.h>
#include <linux/overflow.h>
#include <linux/platform_device.h>
+#include <linux/reset.h>
#include <linux/scatterlist.h>
#include <linux/slab.h>
@@ -1139,12 +1142,28 @@ static void d350_free_chan_resources(struct dma_chan *chan)
static int d350_probe(struct platform_device *pdev)
{
struct device *dev = &pdev->dev;
+ struct reset_control *reset;
+ struct clk *clk;
struct d350 *dmac;
void __iomem *base;
u32 reg;
int ret, nchan, dw, aw, r, p;
bool coherent, memset;
+ clk = devm_clk_get_optional_enabled(dev, NULL);
+ if (IS_ERR(clk))
+ return dev_err_probe(dev, PTR_ERR(clk),
+ "failed to enable clock\n");
+
+ reset = devm_reset_control_get_optional_exclusive(dev, NULL);
+ if (IS_ERR(reset))
+ return dev_err_probe(dev, PTR_ERR(reset),
+ "failed to get reset\n");
+
+ ret = reset_control_reset(reset);
+ if (ret)
+ return ret;
+
base = devm_platform_ioremap_resource(pdev, 0);
if (IS_ERR(base))
return PTR_ERR(base);
@@ -1251,15 +1270,26 @@ static int d350_probe(struct platform_device *pdev)
dmac->dma.device_prep_dma_memset = d350_prep_memset;
}
+ if (of_property_present(dev->of_node, "memory-region")) {
+ ret = of_reserved_mem_device_init(dev);
+ if (ret)
+ return dev_err_probe(dev, ret,
+ "failed to attach reserved memory\n");
+ }
+
platform_set_drvdata(pdev, dmac);
ret = dma_async_device_register(&dmac->dma);
- if (ret)
- return dev_err_probe(dev, ret, "Failed to register DMA device\n");
+ if (ret) {
+ of_reserved_mem_device_release(dev);
+ return dev_err_probe(dev, ret,
+ "Failed to register DMA device\n");
+ }
ret = of_dma_controller_register(dev->of_node, d350_of_xlate, dmac);
if (ret) {
dma_async_device_unregister(&dmac->dma);
+ of_reserved_mem_device_release(dev);
return dev_err_probe(dev, ret,
"Failed to register OF DMA controller\n");
}
@@ -1273,6 +1303,7 @@ static void d350_remove(struct platform_device *pdev)
of_dma_controller_free(pdev->dev.of_node);
dma_async_device_unregister(&dmac->dma);
+ of_reserved_mem_device_release(&pdev->dev);
}
static const struct of_device_id d350_of_match[] __maybe_unused = {
--
2.54.0
next prev parent reply other threads:[~2026-10-12 8:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 8:41 [PATCH v3 0/6] dmaengine: arm-dma350: Add slave support and CIX Sky1 integration Jelly Jia
2026-10-12 8:41 ` [PATCH v3 1/6] dmaengine: arm-dma350: Fix source trigger bit Jelly Jia
2026-10-12 15:09 ` Frank Li
2026-10-12 8:41 ` [PATCH v3 2/6] dmaengine: arm-dma350: Add slave and cyclic transfer support Jelly Jia
2026-10-12 8:41 ` [PATCH v3 3/6] dmaengine: arm-dma350: Sync the slave command list before starting Jelly Jia
2026-10-12 8:41 ` [PATCH v3 4/6] dt-bindings: dma: arm,dma-350: Document the CIX Sky1 integration Jelly Jia
2026-10-12 19:06 ` Conor Dooley
2026-10-12 8:41 ` Jelly Jia [this message]
2026-10-12 8:41 ` [PATCH v3 6/6] arm64: dts: cix: Describe the Sky1 DMA-350 bus integration Jelly Jia
2026-10-12 19:07 ` Conor Dooley
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=20261012084155.2547480-6-Jelly.Jia@cixtech.com \
--to=jelly.jia@cixtech.com \
--cc=Frank.Li@kernel.org \
--cc=cix-kernel-upstream@cixtech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--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®