From: Lubomir Rintel <lkundrak@v3.sk>
To: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>
Cc: SoC Team <soc@kernel.org>, Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Lubomir Rintel <lkundrak@v3.sk>
Subject: [PATCH v2 06/13] ARM: dts: mmp2: Add DMA nodes
Date: Sat, 18 Jul 2020 22:50:12 +0200 [thread overview]
Message-ID: <20200718205019.184927-7-lkundrak@v3.sk> (raw)
In-Reply-To: <20200718205019.184927-1-lkundrak@v3.sk>
There is a 16-channel peripheral DMA controller along with two-channel
audio DMA engines.
Signed-off-by: Lubomir Rintel <lkundrak@v3.sk>
---
arch/arm/boot/dts/mmp2.dtsi | 26 ++++++++++++++++++++++++++
1 file changed, 26 insertions(+)
diff --git a/arch/arm/boot/dts/mmp2.dtsi b/arch/arm/boot/dts/mmp2.dtsi
index da2c92328464e..b349f4f35706b 100644
--- a/arch/arm/boot/dts/mmp2.dtsi
+++ b/arch/arm/boot/dts/mmp2.dtsi
@@ -192,6 +192,24 @@ camera1: camera@d420a800 {
clock-output-names = "mclk";
status = "disabled";
};
+
+ adma0: dma-controller@d42a0800 {
+ compatible = "marvell,adma-1.0";
+ reg = <0xd42a0800 0x100>;
+ interrupts = <48>;
+ #dma-cells = <1>;
+ asram = <&asram>;
+ iram = <&asram>;
+ status = "disabled";
+ };
+
+ adma1: dma-controller@d42a0900 {
+ compatible = "marvell,adma-1.0";
+ reg = <0xd42a0900 0x100>;
+ interrupts = <48>;
+ #dma-cells = <1>;
+ status = "disabled";
+ };
};
apb@d4000000 { /* APB */
@@ -201,6 +219,14 @@ apb@d4000000 { /* APB */
reg = <0xd4000000 0x00200000>;
ranges;
+ dma-controller@d4000000 {
+ compatible = "marvell,pdma-1.0";
+ reg = <0xd4000000 0x10000>;
+ interrupts = <48>;
+ #dma-channels = <16>;
+ status = "disabled";
+ };
+
timer0: timer@d4014000 {
compatible = "mrvl,mmp-timer";
reg = <0xd4014000 0x100>;
--
2.26.2
next prev parent reply other threads:[~2020-07-18 20:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-18 20:50 [PATCH v2 00/13] MMP DTS updates for 5.9 Lubomir Rintel
2020-07-18 20:50 ` [PATCH v2 01/13] ARM: dts: mmp2-olpc-xo-1-75: Fix camera I2C node validation Lubomir Rintel
2020-07-18 20:50 ` [PATCH v2 02/13] ARM: dts: mmp2-olpc-xo-1-75: Delete #address-cells from ssp3 Lubomir Rintel
2020-11-10 3:19 ` Florian Fainelli
2020-07-18 20:50 ` [PATCH v2 03/13] ARM: dts: mmp2: Add #power-domain-cells to /clocks Lubomir Rintel
2020-07-18 20:50 ` [PATCH v2 04/13] ARM: dts: mmp2: Extend the MPMU reg range Lubomir Rintel
2020-07-18 20:50 ` [PATCH v2 05/13] ARM: dts: mmp2: Add Audio SRAM Lubomir Rintel
2020-07-18 20:50 ` Lubomir Rintel [this message]
2020-07-18 20:50 ` [PATCH v2 07/13] ARM: dts: mmp2: Add Audio Clock controller Lubomir Rintel
2020-07-18 20:50 ` [PATCH v2 08/13] ARM: dts: mmp2: Add SSPA nodes Lubomir Rintel
2020-07-18 20:50 ` [PATCH v2 09/13] ARM: dts: mmp2-olpc-xo-1-75: Enable audio support Lubomir Rintel
2020-07-18 20:50 ` [PATCH v2 10/13] ARM: dts: mmp2: Add the GPU Lubomir Rintel
2020-07-18 20:50 ` [PATCH v2 11/13] ARM: dts: mmp2-olpc-xo-1-75: Enable " Lubomir Rintel
2020-07-18 20:50 ` [PATCH v2 12/13] ARM: dts: mmp3: Add " Lubomir Rintel
2020-07-18 20:50 ` [PATCH v2 13/13] ARM: dts: mmp3-dell-ariel: Enable " Lubomir Rintel
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=20200718205019.184927-7-lkundrak@v3.sk \
--to=lkundrak@v3.sk \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=soc@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;
as well as URLs for NNTP newsgroup(s).