From: Anshul Dalal <anshuld@ti.com>
To: Nishanth Menon <nm@ti.com>, Tero Kristo <kristo@kernel.org>,
"Santosh Shilimkar" <ssantosh@kernel.org>,
Rob Herring <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, "Andrew Davis" <afd@ti.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>,
"Dhruva Gole" <d-gole@ti.com>,
Manorit Chawdhry <m-chawdhry@ti.com>,
Anshul Dalal <anshuld@ti.com>
Subject: [PATCH v9 2/2] arm64: dts: ti: update compatible to ti,am654-sci
Date: Fri, 16 Jan 2026 15:45:51 +0530 [thread overview]
Message-ID: <20260116-k3_syscon_add_boot_mailboxes-v9-2-6358cd1f2b1f@ti.com> (raw)
In-Reply-To: <20260116-k3_syscon_add_boot_mailboxes-v9-0-6358cd1f2b1f@ti.com>
K3 SoC's use a different architecture to ti,k2g-sci so update the
compatible to reflect the same while also adding the missing boot_*
mailboxes.
Signed-off-by: Anshul Dalal <anshuld@ti.com>
---
arch/arm64/boot/dts/ti/k3-am62-main.dtsi | 9 ++++++---
arch/arm64/boot/dts/ti/k3-am62a-main.dtsi | 9 ++++++---
arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi | 8 +++++---
arch/arm64/boot/dts/ti/k3-am64-main.dtsi | 8 +++++---
arch/arm64/boot/dts/ti/k3-am65-wakeup.dtsi | 6 ++++--
arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi | 8 +++++---
arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi | 9 +++++----
arch/arm64/boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi | 9 ++++++---
arch/arm64/boot/dts/ti/k3-j784s4-j742s2-mcu-wakeup-common.dtsi | 9 ++++++---
9 files changed, 48 insertions(+), 27 deletions(-)
diff --git a/arch/arm64/boot/dts/ti/k3-am62-main.dtsi b/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
index c5ee263d34a6..c790fc643c4b 100644
--- a/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
@@ -181,11 +181,14 @@ main_pktdma: dma-controller@485c0000 {
dmsc: system-controller@44043000 {
bootph-all;
- compatible = "ti,k2g-sci";
+ compatible = "ti,am654-sci";
ti,host-id = <12>;
- mbox-names = "rx", "tx";
+ mbox-names = "rx", "tx", "boot_rx", "boot_tx", "boot_notify";
mboxes = <&secure_proxy_main 12>,
- <&secure_proxy_main 13>;
+ <&secure_proxy_main 13>,
+ <&secure_proxy_main 0>,
+ <&secure_proxy_main 1>,
+ <&secure_proxy_sa3 0>;
reg-names = "debug_messages";
reg = <0x00 0x44043000 0x00 0xfe0>;
diff --git a/arch/arm64/boot/dts/ti/k3-am62a-main.dtsi b/arch/arm64/boot/dts/ti/k3-am62a-main.dtsi
index 9e5b75a4e88e..af459ed3d4ff 100644
--- a/arch/arm64/boot/dts/ti/k3-am62a-main.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am62a-main.dtsi
@@ -214,13 +214,16 @@ main_bcdma_csi: dma-controller@4e230000 {
};
dmsc: system-controller@44043000 {
- compatible = "ti,k2g-sci";
+ compatible = "ti,am654-sci";
reg = <0x00 0x44043000 0x00 0xfe0>;
reg-names = "debug_messages";
ti,host-id = <12>;
- mbox-names = "rx", "tx";
+ mbox-names = "rx", "tx", "boot_rx", "boot_tx", "boot_notify";
mboxes = <&secure_proxy_main 12>,
- <&secure_proxy_main 13>;
+ <&secure_proxy_main 13>,
+ <&secure_proxy_main 0>,
+ <&secure_proxy_main 1>,
+ <&secure_proxy_sa3 0>;
k3_pds: power-controller {
compatible = "ti,sci-pm-domain";
diff --git a/arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi b/arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi
index 3cf7c2b3ce2d..5037efd73d8b 100644
--- a/arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi
@@ -212,11 +212,13 @@ main_bcdma_csi: dma-controller@4e230000 {
};
dmsc: system-controller@44043000 {
- compatible = "ti,k2g-sci";
+ compatible = "ti,am654-sci";
ti,host-id = <12>;
- mbox-names = "rx", "tx";
+ mbox-names = "rx", "tx", "boot_rx", "boot_tx";
mboxes = <&secure_proxy_main 12>,
- <&secure_proxy_main 13>;
+ <&secure_proxy_main 13>,
+ <&secure_proxy_main 0>,
+ <&secure_proxy_main 1>;
reg-names = "debug_messages";
reg = <0x00 0x44043000 0x00 0xfe0>;
bootph-all;
diff --git a/arch/arm64/boot/dts/ti/k3-am64-main.dtsi b/arch/arm64/boot/dts/ti/k3-am64-main.dtsi
index 1b1d3970888b..ab105fc1f718 100644
--- a/arch/arm64/boot/dts/ti/k3-am64-main.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am64-main.dtsi
@@ -209,11 +209,13 @@ main_pktdma: dma-controller@485c0000 {
dmsc: system-controller@44043000 {
bootph-all;
- compatible = "ti,k2g-sci";
+ compatible = "ti,am654-sci";
ti,host-id = <12>;
- mbox-names = "rx", "tx";
+ mbox-names = "rx", "tx", "boot_rx", "boot_tx";
mboxes = <&secure_proxy_main 12>,
- <&secure_proxy_main 13>;
+ <&secure_proxy_main 13>,
+ <&secure_proxy_main 0>,
+ <&secure_proxy_main 1>;
reg-names = "debug_messages";
reg = <0x00 0x44043000 0x00 0xfe0>;
diff --git a/arch/arm64/boot/dts/ti/k3-am65-wakeup.dtsi b/arch/arm64/boot/dts/ti/k3-am65-wakeup.dtsi
index d62a0be767c8..98608793fa22 100644
--- a/arch/arm64/boot/dts/ti/k3-am65-wakeup.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am65-wakeup.dtsi
@@ -10,10 +10,12 @@ dmsc: system-controller@44083000 {
compatible = "ti,am654-sci";
ti,host-id = <12>;
- mbox-names = "rx", "tx";
+ mbox-names = "rx", "tx", "boot_rx", "boot_tx";
mboxes = <&secure_proxy_main 11>,
- <&secure_proxy_main 13>;
+ <&secure_proxy_main 13>,
+ <&secure_proxy_mcu 5>,
+ <&secure_proxy_mcu 4>;
reg-names = "debug_messages";
reg = <0x44083000 0x1000>;
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 dc5c02a025f8..a185aeb0ae2e 100644
--- a/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi
@@ -7,13 +7,15 @@
&cbass_mcu_wakeup {
dmsc: system-controller@44083000 {
- compatible = "ti,k2g-sci";
+ compatible = "ti,am654-sci";
ti,host-id = <12>;
- mbox-names = "rx", "tx";
+ mbox-names = "rx", "tx", "boot_rx", "boot_tx";
mboxes = <&secure_proxy_main 11>,
- <&secure_proxy_main 13>;
+ <&secure_proxy_main 13>,
+ <&secure_proxy_mcu 5>,
+ <&secure_proxy_mcu 4>;
reg-names = "debug_messages";
reg = <0x00 0x44083000 0x00 0x1000>;
diff --git a/arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi b/arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi
index d5e5e89be5e9..21cc01ab9dba 100644
--- a/arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi
@@ -7,14 +7,15 @@
&cbass_mcu_wakeup {
dmsc: system-controller@44083000 {
- compatible = "ti,k2g-sci";
+ compatible = "ti,am654-sci";
ti,host-id = <12>;
- mbox-names = "rx", "tx";
+ mbox-names = "rx", "tx", "boot_rx", "boot_tx";
mboxes = <&secure_proxy_main 11>,
- <&secure_proxy_main 13>;
-
+ <&secure_proxy_main 13>,
+ <&secure_proxy_mcu 5>,
+ <&secure_proxy_mcu 4>;
reg-names = "debug_messages";
reg = <0x00 0x44083000 0x0 0x1000>;
diff --git a/arch/arm64/boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi b/arch/arm64/boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi
index fd01437726ab..81d352d7912d 100644
--- a/arch/arm64/boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi
@@ -7,13 +7,16 @@
&cbass_mcu_wakeup {
sms: system-controller@44083000 {
- compatible = "ti,k2g-sci";
+ compatible = "ti,am654-sci";
ti,host-id = <12>;
- mbox-names = "rx", "tx";
+ mbox-names = "rx", "tx", "boot_rx", "boot_tx", "boot_notify";
mboxes = <&secure_proxy_main 11>,
- <&secure_proxy_main 13>;
+ <&secure_proxy_main 13>,
+ <&secure_proxy_mcu 5>,
+ <&secure_proxy_mcu 4>,
+ <&secure_proxy_sa3 5>;
reg-names = "debug_messages";
reg = <0x00 0x44083000 0x00 0x1000>;
diff --git a/arch/arm64/boot/dts/ti/k3-j784s4-j742s2-mcu-wakeup-common.dtsi b/arch/arm64/boot/dts/ti/k3-j784s4-j742s2-mcu-wakeup-common.dtsi
index cc22bfb5f599..3f0cef544ca8 100644
--- a/arch/arm64/boot/dts/ti/k3-j784s4-j742s2-mcu-wakeup-common.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-j784s4-j742s2-mcu-wakeup-common.dtsi
@@ -7,13 +7,16 @@
&cbass_mcu_wakeup {
sms: system-controller@44083000 {
- compatible = "ti,k2g-sci";
+ compatible = "ti,am654-sci";
ti,host-id = <12>;
- mbox-names = "rx", "tx";
+ mbox-names = "rx", "tx", "boot_rx", "boot_tx", "boot_notify";
mboxes = <&secure_proxy_main 11>,
- <&secure_proxy_main 13>;
+ <&secure_proxy_main 13>,
+ <&secure_proxy_mcu 5>,
+ <&secure_proxy_mcu 4>,
+ <&secure_proxy_sa3 5>;
reg-names = "debug_messages";
reg = <0x00 0x44083000 0x00 0x1000>;
--
2.52.0
next prev parent reply other threads:[~2026-01-16 10:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 10:15 [PATCH v9 0/2] dt-bindings: arm: keystone: ti,sci: add entries for boot mboxes Anshul Dalal
2026-01-16 10:15 ` [PATCH v9 1/2] dt-bindings: arm: keystone: add boot_* mboxes to ti,sci Anshul Dalal
2026-01-16 10:15 ` Anshul Dalal [this message]
2026-01-16 10:48 ` [PATCH v9 2/2] arm64: dts: ti: update compatible to ti,am654-sci 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=20260116-k3_syscon_add_boot_mailboxes-v9-2-6358cd1f2b1f@ti.com \
--to=anshuld@ti.com \
--cc=afd@ti.com \
--cc=conor+dt@kernel.org \
--cc=d-gole@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-chawdhry@ti.com \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=ssantosh@kernel.org \
--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