On 4/4/24 4:00 AM, Jayesh Choudhary wrote:
Include the uboot device tree files needed to boot the board.

Co-developed-by: Vaishnav Achath <vaishna...@ti.com>
Signed-off-by: Vaishnav Achath <vaishna...@ti.com>
Signed-off-by: Jayesh Choudhary <j-choudh...@ti.com>
---
  arch/arm/dts/Makefile                      |    2 +
  arch/arm/dts/k3-j722s-binman.dtsi          |  171 ++
  arch/arm/dts/k3-j722s-ddr-lp4-50-3733.dtsi | 2795 ++++++++++++++++++++
  arch/arm/dts/k3-j722s-evm-u-boot.dtsi      |   36 +
  arch/arm/dts/k3-j722s-r5-evm.dts           |   82 +
  5 files changed, 3086 insertions(+)
  create mode 100644 arch/arm/dts/k3-j722s-binman.dtsi
  create mode 100644 arch/arm/dts/k3-j722s-ddr-lp4-50-3733.dtsi
  create mode 100644 arch/arm/dts/k3-j722s-evm-u-boot.dtsi
  create mode 100644 arch/arm/dts/k3-j722s-r5-evm.dts


[...]

diff --git a/arch/arm/dts/k3-j722s-evm-u-boot.dtsi 
b/arch/arm/dts/k3-j722s-evm-u-boot.dtsi
new file mode 100644
index 0000000000..056ef08455
--- /dev/null
+++ b/arch/arm/dts/k3-j722s-evm-u-boot.dtsi
@@ -0,0 +1,36 @@
+// SPDX-License-Identifier: GPL-2.0
+/*
+ * Common J722S EVM dts file for SPLs
+ * Copyright (C) 2024 Texas Instruments Incorporated - https://www.ti.com/
+ */
+
+#include "k3-j722s-binman.dtsi"
+
+/ {
+       chosen {
+               stdout-path = "serial2:115200n8";
+               tick-timer = &main_timer0;
+       };
+};
+
+&main_pktdma {
+       reg = <0x00 0x485c0000 0x00 0x000100>,
+             <0x00 0x4a800000 0x00 0x020000>,
+             <0x00 0x4aa00000 0x00 0x040000>,
+             <0x00 0x4b800000 0x00 0x400000>,
+             <0x00 0x485e0000 0x00 0x020000>,
+             <0x00 0x484a0000 0x00 0x004000>,
+             <0x00 0x484c0000 0x00 0x002000>,
+             <0x00 0x48430000 0x00 0x004000>;
+       reg-names = "gcfg", "rchanrt", "tchanrt", "ringrt",
+                   "cfg", "tchan", "rchan", "rflow";

Is this needed? Do we still not have the correct regs in
upstream kernel?

+};
+
+&dmsc {
+       bootph-pre-ram;
+
+       k3_sysreset: sysreset-controller {
+               compatible = "ti,sci-sysreset";
+               bootph-pre-ram;

This node won't be needed soon either[0]. Should mean an
almost empty -u-boot.dtsi file, which should be the goal.

Andrew

[0] https://lore.kernel.org/all/20240402160908.508974-1-...@ti.com/

+       };
+};
diff --git a/arch/arm/dts/k3-j722s-r5-evm.dts b/arch/arm/dts/k3-j722s-r5-evm.dts
new file mode 100644
index 0000000000..aff83cd5d9
--- /dev/null
+++ b/arch/arm/dts/k3-j722s-r5-evm.dts
@@ -0,0 +1,82 @@
+// SPDX-License-Identifier: GPL-2.0
+/*
+ * J722S EVM dts file for R5 SPL
+ * Copyright (C) 2024 Texas Instruments Incorporated - https://www.ti.com/
+ */
+
+#include "k3-j722s-evm.dts"
+#include "k3-j722s-evm-u-boot.dtsi"
+
+#include "k3-j722s-ddr-lp4-50-3733.dtsi"
+#include "k3-am62a-ddr.dtsi"
+
+/ {
+       aliases {
+               remoteproc0 = &sysctrler;
+               remoteproc1 = &a53_0;
+               serial0 = &wkup_uart0;
+               serial2 = &main_uart0;
+       };
+
+       a53_0: a53@0 {
+               compatible = "ti,am654-rproc";
+               reg = <0x00 0x00a90000 0x00 0x10>;
+               power-domains = <&k3_pds 61 TI_SCI_PD_EXCLUSIVE>,
+                       <&k3_pds 135 TI_SCI_PD_EXCLUSIVE>,
+                       <&k3_pds 166 TI_SCI_PD_EXCLUSIVE>;
+               resets = <&k3_reset 135 0>;
+               clocks = <&k3_clks 61 0>;
+               assigned-clocks = <&k3_clks 61 0>, <&k3_clks 135 0>;
+               assigned-clock-parents = <&k3_clks 61 2>;
+               assigned-clock-rates = <200000000>, <1200000000>;
+               ti,sci = <&dmsc>;
+               ti,sci-proc-id = <32>;
+               ti,sci-host-id = <10>;
+               bootph-all;
+       };
+
+       dm_tifs: dm-tifs {
+               compatible = "ti,j721e-dm-sci";
+               ti,host-id = <36>;
+               ti,secure-host;
+               mbox-names = "rx", "tx";
+               mboxes= <&secure_proxy_main 22>,
+                       <&secure_proxy_main 23>;
+               bootph-all;
+       };
+};
+
+&dmsc {
+       mboxes= <&secure_proxy_main 0>,
+               <&secure_proxy_main 1>,
+               <&secure_proxy_main 0>;
+       mbox-names = "rx", "tx", "notify";
+       ti,host-id = <35>;
+       ti,secure-host;
+};
+
+&cbass_main {
+       sa3_secproxy: secproxy@44880000 {
+               compatible = "ti,am654-secure-proxy";
+               #mbox-cells = <1>;
+               reg = <0x00 0x44880000 0x00 0x20000>,
+                     <0x00 0x44860000 0x00 0x20000>,
+                     <0x00 0x43600000 0x00 0x10000>;
+               reg-names = "rt", "scfg", "target_data";
+               bootph-all;
+       };
+
+       sysctrler: sysctrler {
+               compatible = "ti,am654-system-controller";
+               mboxes= <&secure_proxy_main 1>,
+                       <&secure_proxy_main 0>,
+                       <&sa3_secproxy 0>;
+               mbox-names = "tx", "rx", "boot_notify";
+               bootph-all;
+       };
+};
+
+/* WKUP UART0 is used for DM firmware logs */
+&wkup_uart0 {
+       status = "okay";
+};

Reply via email to