From: Vignesh R <vigneshr@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 5/6] arm64: dts: ti: k3-am65: add mcu navss nodes
Date: Tue, 22 Jan 2019 20:33:58 +0530 [thread overview]
Message-ID: <20190122150359.15919-6-vigneshr@ti.com> (raw)
In-Reply-To: <20190122150359.15919-1-vigneshr@ti.com>
From: Grygorii Strashko <grygorii.strashko@ti.com>
Add DT node for MCU NAVSS its components to get DMA working on AM654
SoC.
Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
---
arch/arm/dts/k3-am654-base-board-u-boot.dtsi | 49 ++++++++++++++++++++
1 file changed, 49 insertions(+)
diff --git a/arch/arm/dts/k3-am654-base-board-u-boot.dtsi b/arch/arm/dts/k3-am654-base-board-u-boot.dtsi
index 143eb6d63092..41a0390f070f 100644
--- a/arch/arm/dts/k3-am654-base-board-u-boot.dtsi
+++ b/arch/arm/dts/k3-am654-base-board-u-boot.dtsi
@@ -4,6 +4,7 @@
*/
#include <dt-bindings/pinctrl/k3-am65.h>
+#include <dt-bindings/dma/k3-udma.h>
/ {
chosen {
@@ -63,6 +64,54 @@
pinctrl-single,register-width = <32>;
pinctrl-single,function-mask = <0xffffffff>;
};
+
+ navss_mcu: navss-mcu {
+ compatible = "simple-bus";
+ #address-cells = <2>;
+ #size-cells = <2>;
+ ranges;
+
+ ti,sci-dev-id = <119>;
+
+ mcu_ringacc: ringacc at 2b800000 {
+ compatible = "ti,am654-navss-ringacc";
+ reg = <0x0 0x2b800000 0x0 0x400000>,
+ <0x0 0x2b000000 0x0 0x400000>,
+ <0x0 0x28590000 0x0 0x100>,
+ <0x0 0x2a500000 0x0 0x40000>;
+ reg-names = "rt", "fifos",
+ "proxy_gcfg", "proxy_target";
+ ti,num-rings = <286>;
+ ti,gp-rings = <96 255>; /* start, cnt */
+ ti,dma-ring-reset-quirk;
+ ti,sci = <&dmsc>;
+ ti,sci-dev-id = <195>;
+ };
+
+ mcu_psilcfg: psilcfg at 0x2a268000 {
+ compatible = "ti,k3-navss-psilcfg";
+
+ ti,sci = <&dmsc>;
+ ti,sci-dev-id = <119>;
+ };
+
+ mcu_udmap: udmap at 285c0000 {
+ compatible = "ti,k3-navss-udmap";
+ reg = <0x0 0x285c0000 0x0 0x100>,
+ <0x0 0x2a800000 0x0 0x40000>,
+ <0x0 0x2aa00000 0x0 0x40000>;
+ reg-names = "gcfg", "rchanrt", "tchanrt";
+ #dma-cells = <3>;
+ dma-channels = <96>;
+
+ ti,psi-proxy = <&mcu_psilcfg>;
+ ti,ringacc = <&mcu_ringacc>;
+ ti,psil-base = <0x6000>;
+
+ ti,sci = <&dmsc>;
+ ti,sci-dev-id = <194>;
+ };
+ };
};
&cbass_wakeup {
--
2.20.1
next prev parent reply other threads:[~2019-01-22 15:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 15:03 [U-Boot] [PATCH 0/6] AM65x: Add DMA support Vignesh R
2019-01-22 15:03 ` [U-Boot] [PATCH 1/6] firmware: ti_sci: Add support for NAVSS resource management Vignesh R
2019-01-22 18:56 ` Tom Rini
2019-01-23 13:49 ` Vignesh R
2019-01-23 13:56 ` Tom Rini
2019-01-22 15:03 ` [U-Boot] [PATCH 2/6] soc: ti: k3: add navss ringacc driver Vignesh R
2019-01-22 18:56 ` Tom Rini
2019-01-23 13:50 ` Vignesh R
2019-01-22 15:03 ` [U-Boot] [PATCH 3/6] soc: ti: k3: add CPPI5 description and helpers Vignesh R
2019-01-22 18:56 ` Tom Rini
2019-01-22 15:03 ` [U-Boot] [PATCH 4/6] dma: ti: add driver to K3 UDMA Vignesh R
2019-01-22 18:56 ` Tom Rini
2019-01-23 10:35 ` Peter Ujfalusi
2019-01-23 13:43 ` Vignesh R
2019-01-23 13:56 ` Tom Rini
2019-01-25 14:23 ` Vignesh R
2019-01-23 13:52 ` Tom Rini
2019-01-22 15:03 ` Vignesh R [this message]
2019-01-22 18:56 ` [U-Boot] [PATCH 5/6] arm64: dts: ti: k3-am65: add mcu navss nodes Tom Rini
2019-01-22 15:03 ` [U-Boot] [PATCH 6/6] configs: am65x_evm_a53: Enable DMA related configs Vignesh R
2019-01-22 18:56 ` Tom Rini
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=20190122150359.15919-6-vigneshr@ti.com \
--to=vigneshr@ti.com \
--cc=u-boot@lists.denx.de \
/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