* [PATCH v3 0/7] RZN1 DMA support
@ 2022-02-25 11:23 Miquel Raynal
2022-02-25 11:23 ` [PATCH v3 1/7] dt-bindings: dma: Introduce RZN1 dmamux bindings Miquel Raynal
` (6 more replies)
0 siblings, 7 replies; 11+ messages in thread
From: Miquel Raynal @ 2022-02-25 11:23 UTC (permalink / raw)
To: Vinod Koul, dmaengine
Cc: Rob Herring, devicetree, Stephen Boyd, Michael Turquette,
linux-clk, Milan Stevanovic, Jimmy Lalande, Pascal Eberhard,
linux-renesas-soc, Magnus Damm, Gareth Williams, Phil Edworthy,
Geert Uytterhoeven, Thomas Petazzoni, Miquel Raynal
Hello,
Here is a first series bringing DMA support to RZN1 platforms. I'm not a
DMA expert at all so criticism is welcome.
Soon a second series will come with changes made to the UART controller
driver, in order to interact with the RZN1 DMA controller.
Cheers,
Miquèl
Changes in v3:
* Added Reviewed-by tags.
* Exported the set_dmamux* symbol properly.
* Dropped a useless check in the probe and moved the sysctrl_priv
assignation to the end of the probe.
* Renamed the dmamux driver
* Added a couple of missing MODULE_ macros in the dmamux driver.
* Decided to use a regular platform init call instead of the
arch_initcall() initially proposed.
* s/%d/%u/ in printk's when appropriate.
* Used a hardcoded value instead of dmamux->dmac_requests when
appropriate.
* Changed the variable name "master" to "dmac_idx" to be more
descriptive.
* Dropped most of the of_* calls in favor of #define's.
* Fixed a typo.
* Exported two symbols from 8250_dma.c.
Changes in v2:
* Clarified that the 'fix' regarding non aligned reads would only apply
to the DEV_TO_MEM case.
* Fix the DMA controller compatible string (copy-paste error).
* s/syscon/sysctrl/ as advised by Geert.
* Disabled irqs when taking the spinlock from the clocks driver.
* Moved the DMAMUX offset inside the driver.
* Removed extra commas.
* Improved the style as suggested by Andy.
* Removed a dupplicated check against the device node presence.
* Reduced the number of lines of code by using dev_err_probe().
* Created a Kconfig symbol for DMAMUX to fix the two robot reports
received and be sure there was no useless overhead with other
platforms.
* Exported the serial8250_{tx,rx}_dma() symbols.
Miquel Raynal (7):
dt-bindings: dma: Introduce RZN1 dmamux bindings
dt-bindings: dma: Introduce RZN1 DMA compatible
soc: renesas: rzn1-sysc: Export function to set dmamux
dma: dmamux: Introduce RZN1 DMA router support
dma: dw: Add RZN1 compatible
ARM: dts: r9a06g032: Add the two DMA nodes
ARM: dts: r9a06g032: Describe the DMA router
.../bindings/dma/renesas,rzn1-dmamux.yaml | 42 +++++
.../bindings/dma/snps,dma-spear1340.yaml | 8 +-
MAINTAINERS | 1 +
arch/arm/boot/dts/r9a06g032.dtsi | 37 +++++
drivers/clk/renesas/r9a06g032-clocks.c | 35 +++-
drivers/dma/dw/Kconfig | 8 +
drivers/dma/dw/Makefile | 2 +
drivers/dma/dw/platform.c | 1 +
drivers/dma/dw/rzn1-dmamux.c | 152 ++++++++++++++++++
include/linux/soc/renesas/r9a06g032-sysctrl.h | 11 ++
10 files changed, 295 insertions(+), 2 deletions(-)
create mode 100644 Documentation/devicetree/bindings/dma/renesas,rzn1-dmamux.yaml
create mode 100644 drivers/dma/dw/rzn1-dmamux.c
create mode 100644 include/linux/soc/renesas/r9a06g032-sysctrl.h
--
2.27.0
^ permalink raw reply [flat|nested] 11+ messages in thread
* [PATCH v3 1/7] dt-bindings: dma: Introduce RZN1 dmamux bindings
2022-02-25 11:23 [PATCH v3 0/7] RZN1 DMA support Miquel Raynal
@ 2022-02-25 11:23 ` Miquel Raynal
2022-03-03 13:42 ` Rob Herring
2022-02-25 11:23 ` [PATCH v3 2/7] dt-bindings: dma: Introduce RZN1 DMA compatible Miquel Raynal
` (5 subsequent siblings)
6 siblings, 1 reply; 11+ messages in thread
From: Miquel Raynal @ 2022-02-25 11:23 UTC (permalink / raw)
To: Vinod Koul, dmaengine
Cc: Rob Herring, devicetree, Stephen Boyd, Michael Turquette,
linux-clk, Milan Stevanovic, Jimmy Lalande, Pascal Eberhard,
linux-renesas-soc, Magnus Damm, Gareth Williams, Phil Edworthy,
Geert Uytterhoeven, Thomas Petazzoni, Miquel Raynal,
Geert Uytterhoeven
The Renesas RZN1 DMA IP is a based on a DW core, with eg. an additional
dmamux register located in the system control area which can take up to
32 requests (16 per DMA controller). Each DMA channel can be wired to
two different peripherals.
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
---
.../bindings/dma/renesas,rzn1-dmamux.yaml | 42 +++++++++++++++++++
MAINTAINERS | 1 +
2 files changed, 43 insertions(+)
create mode 100644 Documentation/devicetree/bindings/dma/renesas,rzn1-dmamux.yaml
diff --git a/Documentation/devicetree/bindings/dma/renesas,rzn1-dmamux.yaml b/Documentation/devicetree/bindings/dma/renesas,rzn1-dmamux.yaml
new file mode 100644
index 000000000000..e2c82e43b8b1
--- /dev/null
+++ b/Documentation/devicetree/bindings/dma/renesas,rzn1-dmamux.yaml
@@ -0,0 +1,42 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/dma/renesas,rzn1-dmamux.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Renesas RZ/N1 DMA mux
+
+maintainers:
+ - Miquel Raynal <miquel.raynal@bootlin.com>
+
+allOf:
+ - $ref: "dma-router.yaml#"
+
+properties:
+ compatible:
+ const: renesas,rzn1-dmamux
+
+ '#dma-cells':
+ const: 6
+ description:
+ The first four cells are dedicated to the master DMA controller. The fifth
+ cell gives the DMA mux bit index that must be set starting from 0. The
+ sixth cell gives the binary value that must be written there, ie. 0 or 1.
+
+ dma-masters:
+ minItems: 1
+ maxItems: 2
+
+ dma-requests:
+ const: 32
+
+additionalProperties: false
+
+examples:
+ - |
+ dma-router {
+ compatible = "renesas,rzn1-dmamux";
+ #dma-cells = <6>;
+ dma-masters = <&dma0 &dma1>;
+ dma-requests = <32>;
+ };
diff --git a/MAINTAINERS b/MAINTAINERS
index ea3e6c914384..c70c9c39a2f3 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -18636,6 +18636,7 @@ SYNOPSYS DESIGNWARE DMAC DRIVER
M: Viresh Kumar <vireshk@kernel.org>
R: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
S: Maintained
+F: Documentation/devicetree/bindings/dma/renesas,rzn1-dmamux.yaml
F: Documentation/devicetree/bindings/dma/snps,dma-spear1340.yaml
F: drivers/dma/dw/
F: include/dt-bindings/dma/dw-dmac.h
--
2.27.0
^ permalink raw reply related [flat|nested] 11+ messages in thread
* [PATCH v3 2/7] dt-bindings: dma: Introduce RZN1 DMA compatible
2022-02-25 11:23 [PATCH v3 0/7] RZN1 DMA support Miquel Raynal
2022-02-25 11:23 ` [PATCH v3 1/7] dt-bindings: dma: Introduce RZN1 dmamux bindings Miquel Raynal
@ 2022-02-25 11:23 ` Miquel Raynal
2022-03-03 13:42 ` Rob Herring
2022-02-25 11:23 ` [PATCH v3 3/7] soc: renesas: rzn1-sysc: Export function to set dmamux Miquel Raynal
` (4 subsequent siblings)
6 siblings, 1 reply; 11+ messages in thread
From: Miquel Raynal @ 2022-02-25 11:23 UTC (permalink / raw)
To: Vinod Koul, dmaengine
Cc: Rob Herring, devicetree, Stephen Boyd, Michael Turquette,
linux-clk, Milan Stevanovic, Jimmy Lalande, Pascal Eberhard,
linux-renesas-soc, Magnus Damm, Gareth Williams, Phil Edworthy,
Geert Uytterhoeven, Thomas Petazzoni, Miquel Raynal,
Geert Uytterhoeven
Just like for the NAND controller that is also on this SoC, let's
provide a SoC generic and a more specific couple of compatibles for the
DMA controller.
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
---
.../devicetree/bindings/dma/snps,dma-spear1340.yaml | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/dma/snps,dma-spear1340.yaml b/Documentation/devicetree/bindings/dma/snps,dma-spear1340.yaml
index 6b35089ac017..c13649bf7f19 100644
--- a/Documentation/devicetree/bindings/dma/snps,dma-spear1340.yaml
+++ b/Documentation/devicetree/bindings/dma/snps,dma-spear1340.yaml
@@ -15,7 +15,13 @@ allOf:
properties:
compatible:
- const: snps,dma-spear1340
+ oneOf:
+ - const: snps,dma-spear1340
+ - items:
+ - enum:
+ - renesas,r9a06g032-dma
+ - const: renesas,rzn1-dma
+
"#dma-cells":
minimum: 3
--
2.27.0
^ permalink raw reply related [flat|nested] 11+ messages in thread
* [PATCH v3 3/7] soc: renesas: rzn1-sysc: Export function to set dmamux
2022-02-25 11:23 [PATCH v3 0/7] RZN1 DMA support Miquel Raynal
2022-02-25 11:23 ` [PATCH v3 1/7] dt-bindings: dma: Introduce RZN1 dmamux bindings Miquel Raynal
2022-02-25 11:23 ` [PATCH v3 2/7] dt-bindings: dma: Introduce RZN1 DMA compatible Miquel Raynal
@ 2022-02-25 11:23 ` Miquel Raynal
2022-02-25 11:23 ` [PATCH v3 4/7] dma: dmamux: Introduce RZN1 DMA router support Miquel Raynal
` (3 subsequent siblings)
6 siblings, 0 replies; 11+ messages in thread
From: Miquel Raynal @ 2022-02-25 11:23 UTC (permalink / raw)
To: Vinod Koul, dmaengine
Cc: Rob Herring, devicetree, Stephen Boyd, Michael Turquette,
linux-clk, Milan Stevanovic, Jimmy Lalande, Pascal Eberhard,
linux-renesas-soc, Magnus Damm, Gareth Williams, Phil Edworthy,
Geert Uytterhoeven, Thomas Petazzoni, Miquel Raynal
The dmamux register is located within the system controller.
Without syscon, we need an extra helper in order to give write access to
this register to a dmamux driver.
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
---
drivers/clk/renesas/r9a06g032-clocks.c | 35 ++++++++++++++++++-
include/linux/soc/renesas/r9a06g032-sysctrl.h | 11 ++++++
2 files changed, 45 insertions(+), 1 deletion(-)
create mode 100644 include/linux/soc/renesas/r9a06g032-sysctrl.h
diff --git a/drivers/clk/renesas/r9a06g032-clocks.c b/drivers/clk/renesas/r9a06g032-clocks.c
index c99942f0e4d4..edcdbe3152f0 100644
--- a/drivers/clk/renesas/r9a06g032-clocks.c
+++ b/drivers/clk/renesas/r9a06g032-clocks.c
@@ -20,9 +20,12 @@
#include <linux/pm_clock.h>
#include <linux/pm_domain.h>
#include <linux/slab.h>
+#include <linux/soc/renesas/r9a06g032-sysctrl.h>
#include <linux/spinlock.h>
#include <dt-bindings/clock/r9a06g032-sysctrl.h>
+#define R9A06G032_SYSCTRL_DMAMUX 0xA0
+
struct r9a06g032_gate {
u16 gate, reset, ready, midle,
scon, mirack, mistat;
@@ -315,6 +318,29 @@ struct r9a06g032_priv {
void __iomem *reg;
};
+/* Exported helper to access the DMAMUX register */
+static struct r9a06g032_priv *sysctrl_priv;
+int r9a06g032_sysctrl_set_dmamux(u32 mask, u32 val)
+{
+ unsigned long flags;
+ u32 dmamux;
+
+ if (!sysctrl_priv)
+ return -EPROBE_DEFER;
+
+ spin_lock_irqsave(&sysctrl_priv->lock, flags);
+
+ dmamux = readl(sysctrl_priv->reg + R9A06G032_SYSCTRL_DMAMUX);
+ dmamux &= ~mask;
+ dmamux |= val & mask;
+ writel(dmamux, sysctrl_priv->reg + R9A06G032_SYSCTRL_DMAMUX);
+
+ spin_unlock_irqrestore(&sysctrl_priv->lock, flags);
+
+ return 0;
+}
+EXPORT_SYMBOL_GPL(r9a06g032_sysctrl_set_dmamux);
+
/* register/bit pairs are encoded as an uint16_t */
static void
clk_rdesc_set(struct r9a06g032_priv *clocks,
@@ -922,6 +948,7 @@ static int __init r9a06g032_clocks_probe(struct platform_device *pdev)
clocks->reg = of_iomap(np, 0);
if (WARN_ON(!clocks->reg))
return -ENOMEM;
+
for (i = 0; i < ARRAY_SIZE(r9a06g032_clocks); ++i) {
const struct r9a06g032_clkdesc *d = &r9a06g032_clocks[i];
const char *parent_name = d->source ?
@@ -963,7 +990,13 @@ static int __init r9a06g032_clocks_probe(struct platform_device *pdev)
if (error)
return error;
- return r9a06g032_add_clk_domain(dev);
+ error = r9a06g032_add_clk_domain(dev);
+ if (error)
+ return error;
+
+ sysctrl_priv = clocks;
+
+ return 0;
}
static const struct of_device_id r9a06g032_match[] = {
diff --git a/include/linux/soc/renesas/r9a06g032-sysctrl.h b/include/linux/soc/renesas/r9a06g032-sysctrl.h
new file mode 100644
index 000000000000..066dfb15cbdd
--- /dev/null
+++ b/include/linux/soc/renesas/r9a06g032-sysctrl.h
@@ -0,0 +1,11 @@
+/* SPDX-License-Identifier: GPL-2.0 */
+#ifndef __LINUX_SOC_RENESAS_R9A06G032_SYSCTRL_H__
+#define __LINUX_SOC_RENESAS_R9A06G032_SYSCTRL_H__
+
+#ifdef CONFIG_CLK_R9A06G032
+int r9a06g032_sysctrl_set_dmamux(u32 mask, u32 val);
+#else
+static inline int r9a06g032_sysctrl_set_dmamux(u32 mask, u32 val) { return -ENODEV; }
+#endif
+
+#endif /* __LINUX_SOC_RENESAS_R9A06G032_SYSCTRL_H__ */
--
2.27.0
^ permalink raw reply related [flat|nested] 11+ messages in thread
* [PATCH v3 4/7] dma: dmamux: Introduce RZN1 DMA router support
2022-02-25 11:23 [PATCH v3 0/7] RZN1 DMA support Miquel Raynal
` (2 preceding siblings ...)
2022-02-25 11:23 ` [PATCH v3 3/7] soc: renesas: rzn1-sysc: Export function to set dmamux Miquel Raynal
@ 2022-02-25 11:23 ` Miquel Raynal
2022-02-25 22:01 ` Lad, Prabhakar
2022-02-25 11:24 ` [PATCH v3 5/7] dma: dw: Add RZN1 compatible Miquel Raynal
` (2 subsequent siblings)
6 siblings, 1 reply; 11+ messages in thread
From: Miquel Raynal @ 2022-02-25 11:23 UTC (permalink / raw)
To: Vinod Koul, dmaengine
Cc: Rob Herring, devicetree, Stephen Boyd, Michael Turquette,
linux-clk, Milan Stevanovic, Jimmy Lalande, Pascal Eberhard,
linux-renesas-soc, Magnus Damm, Gareth Williams, Phil Edworthy,
Geert Uytterhoeven, Thomas Petazzoni, Miquel Raynal
The Renesas RZN1 DMA IP is a based on a DW core, with eg. an additional
dmamux register located in the system control area which can take up to
32 requests (16 per DMA controller). Each DMA channel can be wired to
two different peripherals.
We need two additional information from the 'dmas' property: the channel
(bit in the dmamux register) that must be accessed and the value of the
mux for this channel.
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
---
drivers/dma/dw/Kconfig | 8 ++
drivers/dma/dw/Makefile | 2 +
drivers/dma/dw/rzn1-dmamux.c | 152 +++++++++++++++++++++++++++++++++++
3 files changed, 162 insertions(+)
create mode 100644 drivers/dma/dw/rzn1-dmamux.c
diff --git a/drivers/dma/dw/Kconfig b/drivers/dma/dw/Kconfig
index db25f9b7778c..dd53d4a9fa92 100644
--- a/drivers/dma/dw/Kconfig
+++ b/drivers/dma/dw/Kconfig
@@ -16,6 +16,14 @@ config DW_DMAC
Support the Synopsys DesignWare AHB DMA controller. This
can be integrated in chips such as the Intel Cherrytrail.
+config RZN1_DMAMUX
+ tristate "Renesas RZ/N1 DMAMUX driver"
+ depends on DW_DMAC
+ help
+ Support the Renesas RZ/N1 DMAMUX which is located in front of
+ the Synopsys DesignWare AHB DMA controller located on Renesas
+ SoCs.
+
config DW_DMAC_PCI
tristate "Synopsys DesignWare AHB DMA PCI driver"
depends on PCI
diff --git a/drivers/dma/dw/Makefile b/drivers/dma/dw/Makefile
index a6f358ad8591..8025f75e589c 100644
--- a/drivers/dma/dw/Makefile
+++ b/drivers/dma/dw/Makefile
@@ -7,5 +7,7 @@ obj-$(CONFIG_DW_DMAC) += dw_dmac.o
dw_dmac-y := platform.o
dw_dmac-$(CONFIG_OF) += of.o
+obj-$(CONFIG_RZN1_DMAMUX) += rzn1-dmamux.o
+
obj-$(CONFIG_DW_DMAC_PCI) += dw_dmac_pci.o
dw_dmac_pci-y := pci.o
diff --git a/drivers/dma/dw/rzn1-dmamux.c b/drivers/dma/dw/rzn1-dmamux.c
new file mode 100644
index 000000000000..bc4e2e7c3d18
--- /dev/null
+++ b/drivers/dma/dw/rzn1-dmamux.c
@@ -0,0 +1,152 @@
+// SPDX-License-Identifier: GPL-2.0-only
+/*
+ * Copyright (C) 2022 Schneider-Electric
+ * Author: Miquel Raynal <miquel.raynal@bootlin.com
+ * Based on TI crossbar driver written by Peter Ujfalusi <peter.ujfalusi@ti.com>
+ */
+#include <linux/slab.h>
+#include <linux/err.h>
+#include <linux/init.h>
+#include <linux/list.h>
+#include <linux/io.h>
+#include <linux/of_address.h>
+#include <linux/of_device.h>
+#include <linux/of_dma.h>
+#include <linux/soc/renesas/r9a06g032-sysctrl.h>
+
+#define RZN1_DMAMUX_LINES 64
+#define RZN1_DMAMUX_SPLIT 16
+
+struct rzn1_dmamux_data {
+ struct dma_router dmarouter;
+ u32 used_chans;
+ struct mutex lock;
+};
+
+struct rzn1_dmamux_map {
+ unsigned int req_idx;
+};
+
+static void rzn1_dmamux_free(struct device *dev, void *route_data)
+{
+ struct rzn1_dmamux_data *dmamux = dev_get_drvdata(dev);
+ struct rzn1_dmamux_map *map = route_data;
+
+ dev_dbg(dev, "Unmapping DMAMUX request %u\n", map->req_idx);
+
+ mutex_lock(&dmamux->lock);
+ dmamux->used_chans &= ~BIT(map->req_idx);
+ mutex_unlock(&dmamux->lock);
+
+ kfree(map);
+}
+
+static void *rzn1_dmamux_route_allocate(struct of_phandle_args *dma_spec,
+ struct of_dma *ofdma)
+{
+ struct platform_device *pdev = of_find_device_by_node(ofdma->of_node);
+ struct rzn1_dmamux_data *dmamux = platform_get_drvdata(pdev);
+ struct rzn1_dmamux_map *map;
+ unsigned int dmac_idx, chan, val;
+ u32 mask;
+ int ret;
+
+ map = kzalloc(sizeof(*map), GFP_KERNEL);
+ if (!map)
+ return ERR_PTR(-ENOMEM);
+
+ if (dma_spec->args_count != 6)
+ return ERR_PTR(-EINVAL);
+
+ chan = dma_spec->args[0];
+ map->req_idx = dma_spec->args[4];
+ val = dma_spec->args[5];
+ dma_spec->args_count -= 2;
+
+ if (chan >= RZN1_DMAMUX_SPLIT) {
+ dev_err(&pdev->dev, "Invalid DMA request line: %u\n", chan);
+ return ERR_PTR(-EINVAL);
+ }
+
+ if (map->req_idx >= RZN1_DMAMUX_LINES ||
+ (map->req_idx % RZN1_DMAMUX_SPLIT) != chan) {
+ dev_err(&pdev->dev, "Invalid MUX request line: %u\n", map->req_idx);
+ return ERR_PTR(-EINVAL);
+ }
+
+ dmac_idx = map->req_idx < RZN1_DMAMUX_SPLIT ? 0 : 1;
+ dma_spec->np = of_parse_phandle(ofdma->of_node, "dma-masters", dmac_idx);
+ if (!dma_spec->np) {
+ dev_err(&pdev->dev, "Can't get DMA master\n");
+ return ERR_PTR(-EINVAL);
+ }
+
+ dev_dbg(&pdev->dev, "Mapping DMAMUX request %u to DMAC%u request %u\n",
+ map->req_idx, dmac_idx, chan);
+
+ mask = BIT(map->req_idx);
+ mutex_lock(&dmamux->lock);
+ dmamux->used_chans |= mask;
+ ret = r9a06g032_sysctrl_set_dmamux(mask, val ? mask : 0);
+ mutex_unlock(&dmamux->lock);
+ if (ret) {
+ rzn1_dmamux_free(&pdev->dev, map);
+ return ERR_PTR(ret);
+ }
+
+ return map;
+}
+
+static const struct of_device_id rzn1_dmac_match[] __maybe_unused = {
+ { .compatible = "renesas,rzn1-dma" },
+ {},
+};
+
+static int rzn1_dmamux_probe(struct platform_device *pdev)
+{
+ struct device_node *mux_node = pdev->dev.of_node;
+ const struct of_device_id *match;
+ struct device_node *dmac_node;
+ struct rzn1_dmamux_data *dmamux;
+
+ dmamux = devm_kzalloc(&pdev->dev, sizeof(*dmamux), GFP_KERNEL);
+ if (!dmamux)
+ return -ENOMEM;
+
+ mutex_init(&dmamux->lock);
+
+ dmac_node = of_parse_phandle(mux_node, "dma-masters", 0);
+ if (!dmac_node)
+ return dev_err_probe(&pdev->dev, -ENODEV, "Can't get DMA master node\n");
+
+ match = of_match_node(rzn1_dmac_match, dmac_node);
+ of_node_put(dmac_node);
+ if (!match)
+ return dev_err_probe(&pdev->dev, -EINVAL, "DMA master is not supported\n");
+
+ dmamux->dmarouter.dev = &pdev->dev;
+ dmamux->dmarouter.route_free = rzn1_dmamux_free;
+
+ platform_set_drvdata(pdev, dmamux);
+
+ return of_dma_router_register(mux_node, rzn1_dmamux_route_allocate,
+ &dmamux->dmarouter);
+}
+
+static const struct of_device_id rzn1_dmamux_match[] = {
+ { .compatible = "renesas,rzn1-dmamux" },
+ {},
+};
+
+static struct platform_driver rzn1_dmamux_driver = {
+ .driver = {
+ .name = "renesas,rzn1-dmamux",
+ .of_match_table = rzn1_dmamux_match,
+ },
+ .probe = rzn1_dmamux_probe,
+};
+module_platform_driver(rzn1_dmamux_driver);
+
+MODULE_LICENSE("GPL");
+MODULE_AUTHOR("Miquel Raynal <miquel.raynal@bootlin.com");
+MODULE_DESCRIPTION("Renesas RZ/N1 DMAMUX driver");
--
2.27.0
^ permalink raw reply related [flat|nested] 11+ messages in thread
* [PATCH v3 5/7] dma: dw: Add RZN1 compatible
2022-02-25 11:23 [PATCH v3 0/7] RZN1 DMA support Miquel Raynal
` (3 preceding siblings ...)
2022-02-25 11:23 ` [PATCH v3 4/7] dma: dmamux: Introduce RZN1 DMA router support Miquel Raynal
@ 2022-02-25 11:24 ` Miquel Raynal
2022-02-25 11:24 ` [PATCH v3 6/7] ARM: dts: r9a06g032: Add the two DMA nodes Miquel Raynal
2022-02-25 11:24 ` [PATCH v3 7/7] ARM: dts: r9a06g032: Describe the DMA router Miquel Raynal
6 siblings, 0 replies; 11+ messages in thread
From: Miquel Raynal @ 2022-02-25 11:24 UTC (permalink / raw)
To: Vinod Koul, dmaengine
Cc: Rob Herring, devicetree, Stephen Boyd, Michael Turquette,
linux-clk, Milan Stevanovic, Jimmy Lalande, Pascal Eberhard,
linux-renesas-soc, Magnus Damm, Gareth Williams, Phil Edworthy,
Geert Uytterhoeven, Thomas Petazzoni, Miquel Raynal,
Geert Uytterhoeven
The Renesas RZN1 DMA IP is very close to the original DW DMA IP, a DMA
router has been introduced to handle the wiring options that have been
added.
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
---
drivers/dma/dw/platform.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/dma/dw/platform.c b/drivers/dma/dw/platform.c
index 246118955877..47f2292dba98 100644
--- a/drivers/dma/dw/platform.c
+++ b/drivers/dma/dw/platform.c
@@ -137,6 +137,7 @@ static void dw_shutdown(struct platform_device *pdev)
#ifdef CONFIG_OF
static const struct of_device_id dw_dma_of_id_table[] = {
{ .compatible = "snps,dma-spear1340", .data = &dw_dma_chip_pdata },
+ { .compatible = "renesas,rzn1-dma", .data = &dw_dma_chip_pdata },
{}
};
MODULE_DEVICE_TABLE(of, dw_dma_of_id_table);
--
2.27.0
^ permalink raw reply related [flat|nested] 11+ messages in thread
* [PATCH v3 6/7] ARM: dts: r9a06g032: Add the two DMA nodes
2022-02-25 11:23 [PATCH v3 0/7] RZN1 DMA support Miquel Raynal
` (4 preceding siblings ...)
2022-02-25 11:24 ` [PATCH v3 5/7] dma: dw: Add RZN1 compatible Miquel Raynal
@ 2022-02-25 11:24 ` Miquel Raynal
2022-02-25 11:24 ` [PATCH v3 7/7] ARM: dts: r9a06g032: Describe the DMA router Miquel Raynal
6 siblings, 0 replies; 11+ messages in thread
From: Miquel Raynal @ 2022-02-25 11:24 UTC (permalink / raw)
To: Vinod Koul, dmaengine
Cc: Rob Herring, devicetree, Stephen Boyd, Michael Turquette,
linux-clk, Milan Stevanovic, Jimmy Lalande, Pascal Eberhard,
linux-renesas-soc, Magnus Damm, Gareth Williams, Phil Edworthy,
Geert Uytterhoeven, Thomas Petazzoni, Miquel Raynal,
Geert Uytterhoeven
Describe the two DMA controllers available on this SoC.
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
---
arch/arm/boot/dts/r9a06g032.dtsi | 30 ++++++++++++++++++++++++++++++
1 file changed, 30 insertions(+)
diff --git a/arch/arm/boot/dts/r9a06g032.dtsi b/arch/arm/boot/dts/r9a06g032.dtsi
index db657224688a..640c3eb4bbcd 100644
--- a/arch/arm/boot/dts/r9a06g032.dtsi
+++ b/arch/arm/boot/dts/r9a06g032.dtsi
@@ -184,6 +184,36 @@ nand_controller: nand-controller@40102000 {
status = "disabled";
};
+ dma0: dma-controller@40104000 {
+ compatible = "renesas,r9a06g032-dma", "renesas,rzn1-dma";
+ reg = <0x40104000 0x1000>;
+ interrupts = <GIC_SPI 56 IRQ_TYPE_LEVEL_HIGH>;
+ clock-names = "hclk";
+ clocks = <&sysctrl R9A06G032_HCLK_DMA0>;
+ dma-channels = <8>;
+ dma-requests = <16>;
+ dma-masters = <1>;
+ #dma-cells = <3>;
+ block_size = <0xfff>;
+ data_width = <3>;
+ status = "disabled";
+ };
+
+ dma1: dma-controller@40105000 {
+ compatible = "renesas,r9a06g032-dma", "renesas,rzn1-dma";
+ reg = <0x40105000 0x1000>;
+ interrupts = <GIC_SPI 57 IRQ_TYPE_LEVEL_HIGH>;
+ clock-names = "hclk";
+ clocks = <&sysctrl R9A06G032_HCLK_DMA1>;
+ dma-channels = <8>;
+ dma-requests = <16>;
+ dma-masters = <1>;
+ #dma-cells = <3>;
+ block_size = <0xfff>;
+ data_width = <3>;
+ status = "disabled";
+ };
+
gic: interrupt-controller@44101000 {
compatible = "arm,gic-400", "arm,cortex-a7-gic";
interrupt-controller;
--
2.27.0
^ permalink raw reply related [flat|nested] 11+ messages in thread
* [PATCH v3 7/7] ARM: dts: r9a06g032: Describe the DMA router
2022-02-25 11:23 [PATCH v3 0/7] RZN1 DMA support Miquel Raynal
` (5 preceding siblings ...)
2022-02-25 11:24 ` [PATCH v3 6/7] ARM: dts: r9a06g032: Add the two DMA nodes Miquel Raynal
@ 2022-02-25 11:24 ` Miquel Raynal
6 siblings, 0 replies; 11+ messages in thread
From: Miquel Raynal @ 2022-02-25 11:24 UTC (permalink / raw)
To: Vinod Koul, dmaengine
Cc: Rob Herring, devicetree, Stephen Boyd, Michael Turquette,
linux-clk, Milan Stevanovic, Jimmy Lalande, Pascal Eberhard,
linux-renesas-soc, Magnus Damm, Gareth Williams, Phil Edworthy,
Geert Uytterhoeven, Thomas Petazzoni, Miquel Raynal
There is a dmamux on this SoC which allows picking two different sources
for a single DMA request.
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
---
arch/arm/boot/dts/r9a06g032.dtsi | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boot/dts/r9a06g032.dtsi b/arch/arm/boot/dts/r9a06g032.dtsi
index 640c3eb4bbcd..0eb12c3d9cfd 100644
--- a/arch/arm/boot/dts/r9a06g032.dtsi
+++ b/arch/arm/boot/dts/r9a06g032.dtsi
@@ -59,6 +59,13 @@ ext_rtc_clk: extrtcclk {
clock-frequency = <0>;
};
+ dmamux: dma-router {
+ compatible = "renesas,rzn1-dmamux";
+ #dma-cells = <6>;
+ dma-requests = <32>;
+ dma-masters = <&dma0 &dma1>;
+ };
+
soc {
compatible = "simple-bus";
#address-cells = <1>;
--
2.27.0
^ permalink raw reply related [flat|nested] 11+ messages in thread
* Re: [PATCH v3 4/7] dma: dmamux: Introduce RZN1 DMA router support
2022-02-25 11:23 ` [PATCH v3 4/7] dma: dmamux: Introduce RZN1 DMA router support Miquel Raynal
@ 2022-02-25 22:01 ` Lad, Prabhakar
0 siblings, 0 replies; 11+ messages in thread
From: Lad, Prabhakar @ 2022-02-25 22:01 UTC (permalink / raw)
To: Miquel Raynal
Cc: Vinod Koul, dmaengine, Rob Herring,
open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS,
Stephen Boyd, Michael Turquette, linux-clk, Milan Stevanovic,
Jimmy Lalande, Pascal Eberhard, Linux-Renesas, Magnus Damm,
Gareth Williams, Phil Edworthy, Geert Uytterhoeven,
Thomas Petazzoni
Hi Miquel,
Thank you for the patch.
On Fri, Feb 25, 2022 at 12:09 PM Miquel Raynal
<miquel.raynal@bootlin.com> wrote:
>
> The Renesas RZN1 DMA IP is a based on a DW core, with eg. an additional
> dmamux register located in the system control area which can take up to
> 32 requests (16 per DMA controller). Each DMA channel can be wired to
> two different peripherals.
>
> We need two additional information from the 'dmas' property: the channel
> (bit in the dmamux register) that must be accessed and the value of the
> mux for this channel.
>
> Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
> ---
> drivers/dma/dw/Kconfig | 8 ++
> drivers/dma/dw/Makefile | 2 +
> drivers/dma/dw/rzn1-dmamux.c | 152 +++++++++++++++++++++++++++++++++++
> 3 files changed, 162 insertions(+)
> create mode 100644 drivers/dma/dw/rzn1-dmamux.c
>
> diff --git a/drivers/dma/dw/Kconfig b/drivers/dma/dw/Kconfig
> index db25f9b7778c..dd53d4a9fa92 100644
> --- a/drivers/dma/dw/Kconfig
> +++ b/drivers/dma/dw/Kconfig
> @@ -16,6 +16,14 @@ config DW_DMAC
> Support the Synopsys DesignWare AHB DMA controller. This
> can be integrated in chips such as the Intel Cherrytrail.
>
> +config RZN1_DMAMUX
> + tristate "Renesas RZ/N1 DMAMUX driver"
> + depends on DW_DMAC
Maybe dependencies for ARCH_RZN1and COMPILE_TEST too?
> + help
> + Support the Renesas RZ/N1 DMAMUX which is located in front of
> + the Synopsys DesignWare AHB DMA controller located on Renesas
> + SoCs.
> +
> config DW_DMAC_PCI
> tristate "Synopsys DesignWare AHB DMA PCI driver"
> depends on PCI
> diff --git a/drivers/dma/dw/Makefile b/drivers/dma/dw/Makefile
> index a6f358ad8591..8025f75e589c 100644
> --- a/drivers/dma/dw/Makefile
> +++ b/drivers/dma/dw/Makefile
> @@ -7,5 +7,7 @@ obj-$(CONFIG_DW_DMAC) += dw_dmac.o
> dw_dmac-y := platform.o
> dw_dmac-$(CONFIG_OF) += of.o
>
> +obj-$(CONFIG_RZN1_DMAMUX) += rzn1-dmamux.o
> +
> obj-$(CONFIG_DW_DMAC_PCI) += dw_dmac_pci.o
> dw_dmac_pci-y := pci.o
> diff --git a/drivers/dma/dw/rzn1-dmamux.c b/drivers/dma/dw/rzn1-dmamux.c
> new file mode 100644
> index 000000000000..bc4e2e7c3d18
> --- /dev/null
> +++ b/drivers/dma/dw/rzn1-dmamux.c
> @@ -0,0 +1,152 @@
> +// SPDX-License-Identifier: GPL-2.0-only
> +/*
> + * Copyright (C) 2022 Schneider-Electric
> + * Author: Miquel Raynal <miquel.raynal@bootlin.com
> + * Based on TI crossbar driver written by Peter Ujfalusi <peter.ujfalusi@ti.com>
> + */
> +#include <linux/slab.h>
> +#include <linux/err.h>
> +#include <linux/init.h>
> +#include <linux/list.h>
> +#include <linux/io.h>
> +#include <linux/of_address.h>
can you please check if the above four includes are really required.
> +#include <linux/of_device.h>
> +#include <linux/of_dma.h>
> +#include <linux/soc/renesas/r9a06g032-sysctrl.h>
> +
headers need to be sorted.
> +#define RZN1_DMAMUX_LINES 64
> +#define RZN1_DMAMUX_SPLIT 16
> +
> +struct rzn1_dmamux_data {
> + struct dma_router dmarouter;
> + u32 used_chans;
> + struct mutex lock;
> +};
> +
> +struct rzn1_dmamux_map {
> + unsigned int req_idx;
> +};
> +
> +static void rzn1_dmamux_free(struct device *dev, void *route_data)
> +{
> + struct rzn1_dmamux_data *dmamux = dev_get_drvdata(dev);
> + struct rzn1_dmamux_map *map = route_data;
> +
> + dev_dbg(dev, "Unmapping DMAMUX request %u\n", map->req_idx);
> +
> + mutex_lock(&dmamux->lock);
> + dmamux->used_chans &= ~BIT(map->req_idx);
> + mutex_unlock(&dmamux->lock);
> +
> + kfree(map);
> +}
> +
> +static void *rzn1_dmamux_route_allocate(struct of_phandle_args *dma_spec,
> + struct of_dma *ofdma)
> +{
> + struct platform_device *pdev = of_find_device_by_node(ofdma->of_node);
> + struct rzn1_dmamux_data *dmamux = platform_get_drvdata(pdev);
> + struct rzn1_dmamux_map *map;
> + unsigned int dmac_idx, chan, val;
> + u32 mask;
> + int ret;
> +
> + map = kzalloc(sizeof(*map), GFP_KERNEL);
> + if (!map)
> + return ERR_PTR(-ENOMEM);
> +
map needs to be freed in the error path.
> + if (dma_spec->args_count != 6)
> + return ERR_PTR(-EINVAL);
> +
> + chan = dma_spec->args[0];
> + map->req_idx = dma_spec->args[4];
> + val = dma_spec->args[5];
> + dma_spec->args_count -= 2;
> +
> + if (chan >= RZN1_DMAMUX_SPLIT) {
> + dev_err(&pdev->dev, "Invalid DMA request line: %u\n", chan);
> + return ERR_PTR(-EINVAL);
> + }
> +
> + if (map->req_idx >= RZN1_DMAMUX_LINES ||
> + (map->req_idx % RZN1_DMAMUX_SPLIT) != chan) {
> + dev_err(&pdev->dev, "Invalid MUX request line: %u\n", map->req_idx);
> + return ERR_PTR(-EINVAL);
> + }
> +
> + dmac_idx = map->req_idx < RZN1_DMAMUX_SPLIT ? 0 : 1;
> + dma_spec->np = of_parse_phandle(ofdma->of_node, "dma-masters", dmac_idx);
> + if (!dma_spec->np) {
> + dev_err(&pdev->dev, "Can't get DMA master\n");
> + return ERR_PTR(-EINVAL);
> + }
> +
> + dev_dbg(&pdev->dev, "Mapping DMAMUX request %u to DMAC%u request %u\n",
> + map->req_idx, dmac_idx, chan);
> +
> + mask = BIT(map->req_idx);
> + mutex_lock(&dmamux->lock);
> + dmamux->used_chans |= mask;
> + ret = r9a06g032_sysctrl_set_dmamux(mask, val ? mask : 0);
> + mutex_unlock(&dmamux->lock);
> + if (ret) {
> + rzn1_dmamux_free(&pdev->dev, map);
> + return ERR_PTR(ret);
> + }
> +
> + return map;
> +}
> +
> +static const struct of_device_id rzn1_dmac_match[] __maybe_unused = {
any reason for using __maybe_unused?
> + { .compatible = "renesas,rzn1-dma" },
> + {},
"," not required.
> +};
> +
> +static int rzn1_dmamux_probe(struct platform_device *pdev)
> +{
> + struct device_node *mux_node = pdev->dev.of_node;
> + const struct of_device_id *match;
> + struct device_node *dmac_node;
> + struct rzn1_dmamux_data *dmamux;
> +
> + dmamux = devm_kzalloc(&pdev->dev, sizeof(*dmamux), GFP_KERNEL);
> + if (!dmamux)
> + return -ENOMEM;
> +
> + mutex_init(&dmamux->lock);
> +
> + dmac_node = of_parse_phandle(mux_node, "dma-masters", 0);
> + if (!dmac_node)
> + return dev_err_probe(&pdev->dev, -ENODEV, "Can't get DMA master node\n");
> +
> + match = of_match_node(rzn1_dmac_match, dmac_node);
> + of_node_put(dmac_node);
> + if (!match)
> + return dev_err_probe(&pdev->dev, -EINVAL, "DMA master is not supported\n");
> +
> + dmamux->dmarouter.dev = &pdev->dev;
> + dmamux->dmarouter.route_free = rzn1_dmamux_free;
> +
> + platform_set_drvdata(pdev, dmamux);
> +
> + return of_dma_router_register(mux_node, rzn1_dmamux_route_allocate,
> + &dmamux->dmarouter);
> +}
> +
> +static const struct of_device_id rzn1_dmamux_match[] = {
> + { .compatible = "renesas,rzn1-dmamux" },
> + {},
"," not required.
> +};
> +
> +static struct platform_driver rzn1_dmamux_driver = {
> + .driver = {
> + .name = "renesas,rzn1-dmamux",
> + .of_match_table = rzn1_dmamux_match,
> + },
> + .probe = rzn1_dmamux_probe,
> +};
> +module_platform_driver(rzn1_dmamux_driver);
> +
> +MODULE_LICENSE("GPL");
> +MODULE_AUTHOR("Miquel Raynal <miquel.raynal@bootlin.com");
> +MODULE_DESCRIPTION("Renesas RZ/N1 DMAMUX driver");
> --
> 2.27.0
>
Cheers,
Prabhakar
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PATCH v3 1/7] dt-bindings: dma: Introduce RZN1 dmamux bindings
2022-02-25 11:23 ` [PATCH v3 1/7] dt-bindings: dma: Introduce RZN1 dmamux bindings Miquel Raynal
@ 2022-03-03 13:42 ` Rob Herring
0 siblings, 0 replies; 11+ messages in thread
From: Rob Herring @ 2022-03-03 13:42 UTC (permalink / raw)
To: Miquel Raynal
Cc: Vinod Koul, dmaengine, devicetree, Stephen Boyd,
Michael Turquette, linux-clk, Milan Stevanovic, Jimmy Lalande,
Pascal Eberhard, linux-renesas-soc, Magnus Damm, Gareth Williams,
Phil Edworthy, Geert Uytterhoeven, Thomas Petazzoni,
Geert Uytterhoeven
On Fri, Feb 25, 2022 at 12:23:56PM +0100, Miquel Raynal wrote:
> The Renesas RZN1 DMA IP is a based on a DW core, with eg. an additional
> dmamux register located in the system control area which can take up to
> 32 requests (16 per DMA controller). Each DMA channel can be wired to
> two different peripherals.
This should be a child of and referenced by the 'system control area'
schema. Also, add a reg property for the register.
> Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> .../bindings/dma/renesas,rzn1-dmamux.yaml | 42 +++++++++++++++++++
> MAINTAINERS | 1 +
> 2 files changed, 43 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/dma/renesas,rzn1-dmamux.yaml
>
> diff --git a/Documentation/devicetree/bindings/dma/renesas,rzn1-dmamux.yaml b/Documentation/devicetree/bindings/dma/renesas,rzn1-dmamux.yaml
> new file mode 100644
> index 000000000000..e2c82e43b8b1
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/dma/renesas,rzn1-dmamux.yaml
> @@ -0,0 +1,42 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/dma/renesas,rzn1-dmamux.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Renesas RZ/N1 DMA mux
> +
> +maintainers:
> + - Miquel Raynal <miquel.raynal@bootlin.com>
> +
> +allOf:
> + - $ref: "dma-router.yaml#"
> +
> +properties:
> + compatible:
> + const: renesas,rzn1-dmamux
> +
> + '#dma-cells':
> + const: 6
> + description:
> + The first four cells are dedicated to the master DMA controller. The fifth
> + cell gives the DMA mux bit index that must be set starting from 0. The
> + sixth cell gives the binary value that must be written there, ie. 0 or 1.
> +
> + dma-masters:
> + minItems: 1
> + maxItems: 2
> +
> + dma-requests:
> + const: 32
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + dma-router {
> + compatible = "renesas,rzn1-dmamux";
> + #dma-cells = <6>;
> + dma-masters = <&dma0 &dma1>;
> + dma-requests = <32>;
> + };
> diff --git a/MAINTAINERS b/MAINTAINERS
> index ea3e6c914384..c70c9c39a2f3 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -18636,6 +18636,7 @@ SYNOPSYS DESIGNWARE DMAC DRIVER
> M: Viresh Kumar <vireshk@kernel.org>
> R: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> S: Maintained
> +F: Documentation/devicetree/bindings/dma/renesas,rzn1-dmamux.yaml
> F: Documentation/devicetree/bindings/dma/snps,dma-spear1340.yaml
> F: drivers/dma/dw/
> F: include/dt-bindings/dma/dw-dmac.h
> --
> 2.27.0
>
>
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PATCH v3 2/7] dt-bindings: dma: Introduce RZN1 DMA compatible
2022-02-25 11:23 ` [PATCH v3 2/7] dt-bindings: dma: Introduce RZN1 DMA compatible Miquel Raynal
@ 2022-03-03 13:42 ` Rob Herring
0 siblings, 0 replies; 11+ messages in thread
From: Rob Herring @ 2022-03-03 13:42 UTC (permalink / raw)
To: Miquel Raynal
Cc: Vinod Koul, dmaengine, Thomas Petazzoni, Jimmy Lalande,
Pascal Eberhard, Phil Edworthy, devicetree, Geert Uytterhoeven,
Gareth Williams, Stephen Boyd, Rob Herring, linux-clk,
Milan Stevanovic, linux-renesas-soc, Magnus Damm,
Geert Uytterhoeven, Michael Turquette
On Fri, 25 Feb 2022 12:23:57 +0100, Miquel Raynal wrote:
> Just like for the NAND controller that is also on this SoC, let's
> provide a SoC generic and a more specific couple of compatibles for the
> DMA controller.
>
> Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> .../devicetree/bindings/dma/snps,dma-spear1340.yaml | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
Acked-by: Rob Herring <robh@kernel.org>
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2022-03-03 13:42 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-02-25 11:23 [PATCH v3 0/7] RZN1 DMA support Miquel Raynal
2022-02-25 11:23 ` [PATCH v3 1/7] dt-bindings: dma: Introduce RZN1 dmamux bindings Miquel Raynal
2022-03-03 13:42 ` Rob Herring
2022-02-25 11:23 ` [PATCH v3 2/7] dt-bindings: dma: Introduce RZN1 DMA compatible Miquel Raynal
2022-03-03 13:42 ` Rob Herring
2022-02-25 11:23 ` [PATCH v3 3/7] soc: renesas: rzn1-sysc: Export function to set dmamux Miquel Raynal
2022-02-25 11:23 ` [PATCH v3 4/7] dma: dmamux: Introduce RZN1 DMA router support Miquel Raynal
2022-02-25 22:01 ` Lad, Prabhakar
2022-02-25 11:24 ` [PATCH v3 5/7] dma: dw: Add RZN1 compatible Miquel Raynal
2022-02-25 11:24 ` [PATCH v3 6/7] ARM: dts: r9a06g032: Add the two DMA nodes Miquel Raynal
2022-02-25 11:24 ` [PATCH v3 7/7] ARM: dts: r9a06g032: Describe the DMA router Miquel Raynal
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).