* [PATCH v9 0/2] dt-bindings: arm: keystone: ti,sci: add entries for boot mboxes
@ 2026-01-16 10:15 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 ` [PATCH v9 2/2] arm64: dts: ti: update compatible to ti,am654-sci Anshul Dalal
0 siblings, 2 replies; 4+ messages in thread
From: Anshul Dalal @ 2026-01-16 10:15 UTC (permalink / raw)
To: Nishanth Menon, Tero Kristo, Santosh Shilimkar, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Andrew Davis
Cc: linux-arm-kernel, devicetree, linux-kernel, Vignesh Raghavendra,
Dhruva Gole, Manorit Chawdhry, Anshul Dalal
Signed-off-by: Anshul Dalal <anshuld@ti.com>
---
Changes in v9:
- Pick up R-by tag from Rob Herring
- Add DTS changes as in [1/2] patch
- Link to v8: https://lore.kernel.org/r/20260113-k3_syscon_add_boot_mailboxes-v8-1-d43954527b5d@ti.com
Changes in v8:
- Refactored the patch to a simplified diff
- Link to v7: https://lore.kernel.org/r/20260107-k3_syscon_add_boot_mailboxes-v7-1-d97a943f0a52@ti.com
Changes in v7:
- Removed ti,am642-sci compatible
- Keep examples unchanged
- Modify ti,am654-sci ordering to ensure compliance with SoCs without a notify channel
- Link to v6: https://lore.kernel.org/r/20251222-k3_syscon_add_boot_mailboxes-v6-1-b93ada9f1d47@ti.com
Changes in v6:
- Added ti,am642-sci compatible to represent SoCs without a "notify" channel
- Added new examples instead of editing existing ones
- Link to v5: https://lore.kernel.org/r/20251215-k3_syscon_add_boot_mailboxes-v5-1-5a8fe567fd31@ti.com
Changes in v5:
- Added commit description for the optional mailboxes
- Link to v4: https://lore.kernel.org/r/20251205-k3_syscon_add_boot_mailboxes-v4-1-8e216fb88941@ti.com
Changes in v4:
- Make new boot_* mboxes conditional on ti,am654-sci compatible
- Link to v3: https://lore.kernel.org/r/20251112-k3_syscon_add_boot_mailboxes-v3-1-66155a4236dc@ti.com
Changes in v3:
- Drop [1/2] of the last patch series
- Update existing example with boot_* mailboxes instead of adding a new one
- Link to v2: https://lore.kernel.org/r/20251112-k3_syscon_add_boot_mailboxes-v2-0-aebc1e47b391@ti.com
Changes in v2:
- Remove maxItems entry
- Remove RFC tag from patch (added by mistake in v1)
- Document the new mailboxes in mboxes instead of mbox-names
- Provide example with all the mailboxes set
- Update commit title to have "ti,sci"
- Split into two patches
- Link to v1: https://lore.kernel.org/r/20251111-k3_syscon_add_boot_mailboxes-v1-1-529a27f21076@ti.com
---
Anshul Dalal (2):
dt-bindings: arm: keystone: add boot_* mboxes to ti,sci
arm64: dts: ti: update compatible to ti,am654-sci
.../devicetree/bindings/arm/keystone/ti,sci.yaml | 24 ++++++++++++++++++++++
arch/arm64/boot/dts/ti/k3-am62-main.dtsi | 9 +++++---
arch/arm64/boot/dts/ti/k3-am62a-main.dtsi | 9 +++++---
.../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 +++++---
.../dts/ti/k3-j784s4-j742s2-mcu-wakeup-common.dtsi | 9 +++++---
10 files changed, 72 insertions(+), 27 deletions(-)
---
base-commit: 9b7977f9e39b7768c70c2aa497f04e7569fd3e00
change-id: 20251105-k3_syscon_add_boot_mailboxes-8452bdd98962
Best regards,
--
Anshul Dalal <anshuld@ti.com>
^ permalink raw reply [flat|nested] 4+ messages in thread
* [PATCH v9 1/2] dt-bindings: arm: keystone: add boot_* mboxes to ti,sci
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 ` Anshul Dalal
2026-01-16 10:15 ` [PATCH v9 2/2] arm64: dts: ti: update compatible to ti,am654-sci Anshul Dalal
1 sibling, 0 replies; 4+ messages in thread
From: Anshul Dalal @ 2026-01-16 10:15 UTC (permalink / raw)
To: Nishanth Menon, Tero Kristo, Santosh Shilimkar, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Andrew Davis
Cc: linux-arm-kernel, devicetree, linux-kernel, Vignesh Raghavendra,
Dhruva Gole, Manorit Chawdhry, Anshul Dalal
The bootloader on K3 devices makes use of mailboxes as per the ROM spec
which might be different than one's available to the kernel (firmware
spec).
Therefore, this patch adds the missing mailbox entries to the DT binding
if the matching compatible is ti,am654-sci to represent the mailboxes
exposed by the hardware during boot for the purpose of loading the
firmware.
The newly added mboxes are made optional by keeping minItems as 2 to
remain compliant with existing device-trees. The new 'notify' channel is
not supported on all SoCs and is therefore kept at last in the list.
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
Signed-off-by: Anshul Dalal <anshuld@ti.com>
---
.../devicetree/bindings/arm/keystone/ti,sci.yaml | 24 ++++++++++++++++++++++
1 file changed, 24 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/keystone/ti,sci.yaml b/Documentation/devicetree/bindings/arm/keystone/ti,sci.yaml
index 25a2b42105e5..0e505b96e499 100644
--- a/Documentation/devicetree/bindings/arm/keystone/ti,sci.yaml
+++ b/Documentation/devicetree/bindings/arm/keystone/ti,sci.yaml
@@ -51,15 +51,27 @@ properties:
minItems: 1
mbox-names:
+ minItems: 2
description: |
Specifies the mailboxes used to communicate with TI-SCI Controller
made available from TI-SCI controller.
items:
- const: rx
- const: tx
+ - const: boot_rx
+ - const: boot_tx
+ - const: boot_notify
+ - const: notify
mboxes:
minItems: 2
+ items:
+ - description: RX thread
+ - description: TX thread
+ - description: boot stage RX thread
+ - description: boot stage TX thread
+ - description: boot stage Notify thread
+ - description: Notify thread
ti,host-id:
$ref: /schemas/types.yaml#/definitions/uint32
@@ -79,6 +91,18 @@ properties:
type: object
$ref: /schemas/reset/ti,sci-reset.yaml#
+if:
+ properties:
+ compatible:
+ contains:
+ const: ti,k2g-sci
+then:
+ properties:
+ mbox-names:
+ maxItems: 2
+ mboxes:
+ maxItems: 2
+
required:
- compatible
- mbox-names
--
2.52.0
^ permalink raw reply related [flat|nested] 4+ messages in thread
* [PATCH v9 2/2] arm64: dts: ti: update compatible to ti,am654-sci
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
2026-01-16 10:48 ` Nishanth Menon
1 sibling, 1 reply; 4+ messages in thread
From: Anshul Dalal @ 2026-01-16 10:15 UTC (permalink / raw)
To: Nishanth Menon, Tero Kristo, Santosh Shilimkar, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Andrew Davis
Cc: linux-arm-kernel, devicetree, linux-kernel, Vignesh Raghavendra,
Dhruva Gole, Manorit Chawdhry, Anshul Dalal
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
^ permalink raw reply related [flat|nested] 4+ messages in thread
* Re: [PATCH v9 2/2] arm64: dts: ti: update compatible to ti,am654-sci
2026-01-16 10:15 ` [PATCH v9 2/2] arm64: dts: ti: update compatible to ti,am654-sci Anshul Dalal
@ 2026-01-16 10:48 ` Nishanth Menon
0 siblings, 0 replies; 4+ messages in thread
From: Nishanth Menon @ 2026-01-16 10:48 UTC (permalink / raw)
To: Anshul Dalal
Cc: Tero Kristo, Santosh Shilimkar, Rob Herring, Krzysztof Kozlowski,
Conor Dooley, Andrew Davis, linux-arm-kernel, devicetree,
linux-kernel, Vignesh Raghavendra, Dhruva Gole, Manorit Chawdhry
On 15:45-20260116, Anshul Dalal wrote:
> 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 ++++++---
Split this into two patches at least:
a) tda4 arch devices -> with notify
b) am62 class devices without notify
All should have boot_notify, no?
Will also be good to point to reference docs where these came from.
> 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
>
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
https://ti.com/opensource
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2026-01-16 10:48 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 ` [PATCH v9 2/2] arm64: dts: ti: update compatible to ti,am654-sci Anshul Dalal
2026-01-16 10:48 ` Nishanth Menon
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox