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>,
Hiago De Franco <hiago.franco@toradex.com>,
Francesco Dolcini <francesco.dolcini@toradex.com>,
Emanuele Ghidoli <emanuele.ghidoli@toradex.com>,
Parth Pancholi <parth.pancholi@toradex.com>,
Jo_o Paulo Gon_alves <joao.goncalves@toradex.com>
Subject: [PATCH v4 15/34] arm64: dts: ti: k3-am62p-verdin: Add missing cfg for TI IPC Firmware
Date: Mon, 8 Sep 2025 19:58:07 +0530 [thread overview]
Message-ID: <20250908142826.1828676-16-b-padhi@ti.com> (raw)
In-Reply-To: <20250908142826.1828676-1-b-padhi@ti.com>
The wkup_r5fss0_core0_memory_region is used to store the text/data
sections of the Device Manager (DM) firmware itself and is necessary for
platform boot. Whereas the wkup_r5fss0_core0_dma_memory_region is used
for allocating the Virtio buffers needed for IPC with the DM core which
could be optional. The labels were incorrectly used in the
k3-am62p-verdin.dtsi file. Correct the firmware memory region label.
Currently, only mailbox node is enabled with FIFO assignment. However,
there are no users of the enabled mailboxes. Add the missing carveouts
for WKUP and MCU R5F remote processors, and enable those by associating
to the above carveout and mailboxes. This config aligns with other AM62P
boards and can be refactored out later.
Signed-off-by: Beleswar Padhi <b-padhi@ti.com>
Tested-by: Hiago De Franco <hiago.franco@toradex.com> # Verdin AM62P
---
Cc: Francesco Dolcini <francesco.dolcini@toradex.com>
Cc: Emanuele Ghidoli <emanuele.ghidoli@toradex.com>
Cc: Parth Pancholi <parth.pancholi@toradex.com>
Cc: Jo_o Paulo Gon_alves <joao.goncalves@toradex.com>
Cc: Hiago De Franco <hiago.franco@toradex.com>
Requesting for a review/test.
v4: Changelog:
1. None
Link to v3:
https://lore.kernel.org/all/20250905051846.1189612-15-b-padhi@ti.com/
v3: Changelog:
1. Changed carveout node names to memory@addr.
Link to v2:
https://lore.kernel.org/all/20250823160901.2177841-15-b-padhi@ti.com/
v2: Changelog:
1. Re-ordered patch from [PATCH 16/33] to [PATCH v2 14/33].
2. Added T/B tag.
Link to v1:
https://lore.kernel.org/all/20250814223839.3256046-17-b-padhi@ti.com/
arch/arm64/boot/dts/ti/k3-am62p-verdin.dtsi | 40 +++++++++++++++++++++
1 file changed, 40 insertions(+)
diff --git a/arch/arm64/boot/dts/ti/k3-am62p-verdin.dtsi b/arch/arm64/boot/dts/ti/k3-am62p-verdin.dtsi
index 522d6f029c36..671d367b40d1 100644
--- a/arch/arm64/boot/dts/ti/k3-am62p-verdin.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am62p-verdin.dtsi
@@ -162,6 +162,24 @@ secure_ddr: optee@9e800000 {
no-map;
};
+ mcu_r5fss0_core0_dma_memory_region: memory@9b800000 {
+ compatible = "shared-dma-pool";
+ reg = <0x00 0x9b800000 0x00 0x100000>;
+ no-map;
+ };
+
+ mcu_r5fss0_core0_memory_region: memory@9b900000 {
+ compatible = "shared-dma-pool";
+ reg = <0x00 0x9b900000 0x00 0xf00000>;
+ no-map;
+ };
+
+ wkup_r5fss0_core0_dma_memory_region: memory@9c800000 {
+ compatible = "shared-dma-pool";
+ reg = <0x00 0x9c800000 0x00 0x100000>;
+ no-map;
+ };
+
wkup_r5fss0_core0_memory_region: memory@9c900000 {
compatible = "shared-dma-pool";
reg = <0x00 0x9c900000 0x00 0x01e00000>;
@@ -848,6 +866,28 @@ mbox_mcu_r5_0: mbox-mcu-r5-0 {
};
};
+&wkup_r5fss0 {
+ status = "okay";
+};
+
+&wkup_r5fss0_core0 {
+ mboxes = <&mailbox0_cluster0 &mbox_r5_0>;
+ memory-region = <&wkup_r5fss0_core0_dma_memory_region>,
+ <&wkup_r5fss0_core0_memory_region>;
+ status = "okay";
+};
+
+&mcu_r5fss0 {
+ status = "okay";
+};
+
+&mcu_r5fss0_core0 {
+ mboxes = <&mailbox0_cluster1 &mbox_mcu_r5_0>;
+ memory-region = <&mcu_r5fss0_core0_dma_memory_region>,
+ <&mcu_r5fss0_core0_memory_region>;
+ status = "okay";
+};
+
&main0_alert {
temperature = <95000>;
};
--
2.34.1
next prev parent reply other threads:[~2025-09-08 14:30 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 ` [PATCH v4 01/34] arm64: dts: ti: k3-j7200: Enable R5F remote processors at board level Beleswar Padhi
2025-09-08 14:27 ` [PATCH v4 02/34] arm64: dts: ti: k3-j721e: Enable " 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 ` Beleswar Padhi [this message]
2025-09-08 19:20 ` [PATCH v4 15/34] arm64: dts: ti: k3-am62p-verdin: Add missing cfg for TI IPC Firmware 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-16-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=emanuele.ghidoli@toradex.com \
--cc=francesco.dolcini@toradex.com \
--cc=hiago.franco@toradex.com \
--cc=hnagalla@ti.com \
--cc=jm@ti.com \
--cc=joao.goncalves@toradex.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=parth.pancholi@toradex.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