Devicetree
 help / color / mirror / Atom feed
From: Beleswar Padhi <b-padhi@ti.com>
To: <nm@ti.com>, <vigneshr@ti.com>, <kristo@kernel.org>,
	<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>
Cc: <afd@ti.com>, <u-kumar1@ti.com>, <hnagalla@ti.com>, <jm@ti.com>,
	<d-gole@ti.com>, <b-padhi@ti.com>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH v4 01/34] arm64: dts: ti: k3-j7200: Enable R5F remote processors at board level
Date: Mon, 8 Sep 2025 19:57:53 +0530	[thread overview]
Message-ID: <20250908142826.1828676-2-b-padhi@ti.com> (raw)
In-Reply-To: <20250908142826.1828676-1-b-padhi@ti.com>

Remote Processors defined in top-level J7200 SoC dtsi files are
incomplete without the memory carveouts and mailbox assignments which
are only known at board integration level.

Therefore, disable the remote processors at SoC level and enable them at
board level where above information is available.

Signed-off-by: Beleswar Padhi <b-padhi@ti.com>
Acked-by: Andrew Davis <afd@ti.com>
---
v4: Changelog:
1. None

Link to v3:
https://lore.kernel.org/all/20250905051846.1189612-2-b-padhi@ti.com/

v3: Changelog:
1. Carried A/B tag.
2. Updated $subject to include R5F remote processors.

Link to v2:
https://lore.kernel.org/all/20250823160901.2177841-2-b-padhi@ti.com/

v2: Changelog:
1. None

Link to v1:
https://lore.kernel.org/all/20250814223839.3256046-2-b-padhi@ti.com/

 arch/arm64/boot/dts/ti/k3-j7200-main.dtsi       | 3 +++
 arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi | 3 +++
 arch/arm64/boot/dts/ti/k3-j7200-som-p0.dtsi     | 9 +++++++++
 3 files changed, 15 insertions(+)

diff --git a/arch/arm64/boot/dts/ti/k3-j7200-main.dtsi b/arch/arm64/boot/dts/ti/k3-j7200-main.dtsi
index 5ce5f0a3d6f5..628ff89dd72f 100644
--- a/arch/arm64/boot/dts/ti/k3-j7200-main.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-j7200-main.dtsi
@@ -1516,6 +1516,7 @@ main_r5fss0: r5fss@5c00000 {
 		ranges = <0x5c00000 0x00 0x5c00000 0x20000>,
 			 <0x5d00000 0x00 0x5d00000 0x20000>;
 		power-domains = <&k3_pds 243 TI_SCI_PD_EXCLUSIVE>;
+		status = "disabled";
 
 		main_r5fss0_core0: r5f@5c00000 {
 			compatible = "ti,j7200-r5f";
@@ -1530,6 +1531,7 @@ main_r5fss0_core0: r5f@5c00000 {
 			ti,atcm-enable = <1>;
 			ti,btcm-enable = <1>;
 			ti,loczrama = <1>;
+			status = "disabled";
 		};
 
 		main_r5fss0_core1: r5f@5d00000 {
@@ -1545,6 +1547,7 @@ main_r5fss0_core1: r5f@5d00000 {
 			ti,atcm-enable = <1>;
 			ti,btcm-enable = <1>;
 			ti,loczrama = <1>;
+			status = "disabled";
 		};
 	};
 
diff --git a/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi b/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi
index 56ab144fea07..692c4745040e 100644
--- a/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi
@@ -612,6 +612,7 @@ mcu_r5fss0: r5fss@41000000 {
 		ranges = <0x41000000 0x00 0x41000000 0x20000>,
 			 <0x41400000 0x00 0x41400000 0x20000>;
 		power-domains = <&k3_pds 249 TI_SCI_PD_EXCLUSIVE>;
+		status = "disabled";
 
 		mcu_r5fss0_core0: r5f@41000000 {
 			compatible = "ti,j7200-r5f";
@@ -626,6 +627,7 @@ mcu_r5fss0_core0: r5f@41000000 {
 			ti,atcm-enable = <1>;
 			ti,btcm-enable = <1>;
 			ti,loczrama = <1>;
+			status = "disabled";
 		};
 
 		mcu_r5fss0_core1: r5f@41400000 {
@@ -641,6 +643,7 @@ mcu_r5fss0_core1: r5f@41400000 {
 			ti,atcm-enable = <1>;
 			ti,btcm-enable = <1>;
 			ti,loczrama = <1>;
+			status = "disabled";
 		};
 	};
 
diff --git a/arch/arm64/boot/dts/ti/k3-j7200-som-p0.dtsi b/arch/arm64/boot/dts/ti/k3-j7200-som-p0.dtsi
index 291ab9bb414d..90befcdc8d08 100644
--- a/arch/arm64/boot/dts/ti/k3-j7200-som-p0.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-j7200-som-p0.dtsi
@@ -254,20 +254,27 @@ mbox_main_r5fss0_core1: mbox-main-r5fss0-core1 {
 	};
 };
 
+&mcu_r5fss0 {
+	status = "okay";
+};
+
 &mcu_r5fss0_core0 {
 	mboxes = <&mailbox0_cluster0 &mbox_mcu_r5fss0_core0>;
 	memory-region = <&mcu_r5fss0_core0_dma_memory_region>,
 			<&mcu_r5fss0_core0_memory_region>;
+	status = "okay";
 };
 
 &mcu_r5fss0_core1 {
 	mboxes = <&mailbox0_cluster0 &mbox_mcu_r5fss0_core1>;
 	memory-region = <&mcu_r5fss0_core1_dma_memory_region>,
 			<&mcu_r5fss0_core1_memory_region>;
+	status = "okay";
 };
 
 &main_r5fss0 {
 	ti,cluster-mode = <0>;
+	status = "okay";
 };
 
 /* Timers are used by Remoteproc firmware */
@@ -287,12 +294,14 @@ &main_r5fss0_core0 {
 	mboxes = <&mailbox0_cluster1 &mbox_main_r5fss0_core0>;
 	memory-region = <&main_r5fss0_core0_dma_memory_region>,
 			<&main_r5fss0_core0_memory_region>;
+	status = "okay";
 };
 
 &main_r5fss0_core1 {
 	mboxes = <&mailbox0_cluster1 &mbox_main_r5fss0_core1>;
 	memory-region = <&main_r5fss0_core1_dma_memory_region>,
 			<&main_r5fss0_core1_memory_region>;
+	status = "okay";
 };
 
 &main_i2c0 {
-- 
2.34.1


  reply	other threads:[~2025-09-08 14:29 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-08 14:27 [PATCH v4 00/34] Refactor TI IPC DT configs into dtsi Beleswar Padhi
2025-09-08 14:27 ` Beleswar Padhi [this message]
2025-09-08 14:27 ` [PATCH v4 02/34] arm64: dts: ti: k3-j721e: Enable remote processors at board level Beleswar Padhi
2025-09-08 14:27 ` [PATCH v4 03/34] arm64: dts: ti: k3-j721s2: " Beleswar Padhi
2025-09-08 14:27 ` [PATCH v4 04/34] arm64: dts: ti: k3-j784s4-j742s2: " Beleswar Padhi
2025-09-08 14:27 ` [PATCH v4 05/34] arm64: dts: ti: k3-am62p-j722s: " Beleswar Padhi
2025-09-08 14:27 ` [PATCH v4 06/34] arm64: dts: ti: k3-am62: " Beleswar Padhi
2025-09-08 14:27 ` [PATCH v4 07/34] arm64: dts: ti: k3-am62a: " Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 08/34] arm64: dts: ti: k3-am64: " Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 09/34] arm64: dts: ti: k3-am65: " Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 10/34] arm64: dts: ti: k3-am62: Enable Mailbox nodes at the " Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 11/34] arm64: dts: ti: k3-am62a: " Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 12/34] arm64: dts: ti: k3-am6*-boards: Add label to reserved-memory node Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 13/34] arm64: dts: ti: k3: Rename rproc reserved-mem nodes to 'memory@addr' Beleswar Padhi
2025-09-08 19:23   ` Francesco Dolcini
2025-09-08 14:28 ` [PATCH v4 14/34] arm64: dts: ti: k3-j721e-beagleboneai64: Add missing cfg for TI IPC FW Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 15/34] arm64: dts: ti: k3-am62p-verdin: Add missing cfg for TI IPC Firmware Beleswar Padhi
2025-09-08 19:20   ` Francesco Dolcini
2025-09-08 14:28 ` [PATCH v4 16/34] arm64: dts: ti: k3-am62-verdin: " Beleswar Padhi
2025-09-08 19:21   ` Francesco Dolcini
2025-09-08 14:28 ` [PATCH v4 17/34] arm64: dts: ti: k3-am62-pocketbeagle2: " Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 18/34] arm64: dts: ti: k3-am642-sr-som: " Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 19/34] arm64: dts: ti: k3-am64-phycore-som: " Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 20/34] arm64: dts: ti: k3-am642-tqma64xxl: " Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 21/34] Revert "arm64: dts: ti: k3-j721e-sk: Fix reversed C6x carveout locations" Beleswar Padhi
2025-09-10 14:07   ` Andrew Davis
2025-09-08 14:28 ` [PATCH v4 22/34] Revert "arm64: dts: ti: k3-j721e-beagleboneai64: " Beleswar Padhi
2025-09-10 14:07   ` Andrew Davis
2025-09-08 14:28 ` [PATCH v4 23/34] arm64: dts: ti: k3-j721e-beagleboneai64: Switch MAIN R5F clusters to Split-mode Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 24/34] arm64: dts: ti: k3-j7200-ti-ipc-firmware: Refactor IPC cfg into new dtsi Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 25/34] arm64: dts: ti: k3-j721e-ti-ipc-firmware: " Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 26/34] arm64: dts: ti: k3-j721s2-ti-ipc-firmware: " Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 27/34] arm64: dts: ti: k3-j784s4-j742s2-ti-ipc-firmware-common: " Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 28/34] arm64: dts: ti: k3-j784s4-ti-ipc-firmware: " Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 29/34] arm64: dts: ti: k3-j722s-ti-ipc-firmware: " Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 30/34] arm64: dts: ti: k3-am62p-ti-ipc-firmware: " Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 31/34] arm64: dts: ti: k3-am62-ti-ipc-firmware: " Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 32/34] arm64: dts: ti: k3-am62a-ti-ipc-firmware: " Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 33/34] arm64: dts: ti: k3-am64-ti-ipc-firmware: " Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 34/34] arm64: dts: ti: k3-am65-ti-ipc-firmware: " Beleswar Padhi
2025-09-12  9:49 ` [PATCH v4 00/34] Refactor TI IPC DT configs into dtsi Nishanth Menon

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=20250908142826.1828676-2-b-padhi@ti.com \
    --to=b-padhi@ti.com \
    --cc=afd@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=d-gole@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hnagalla@ti.com \
    --cc=jm@ti.com \
    --cc=kristo@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=robh@kernel.org \
    --cc=u-kumar1@ti.com \
    --cc=vigneshr@ti.com \
    /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