{am62,am62a}-phycore-som: Add R5F and C7xv device nodes
Subsystems (2)
v2 cover {am62,am62a}-phycore-som: Add R5F and C7xv device nodes
This patch series is based on [1] and adds these R5F and C7xv device nodes to the am62- and am62a-phycore-som device-trees. It also reserves main_timer2 as well as main_rti4 for the C7 DSP firmware.
1: https://lore.kernel.org/linux-arm-kernel/[email protected]/T/#t
Changes in v2:
* Rebased to latest master branch.
Daniel Schultz (4):
arm64: dts: ti: k3-am62-phycore-som: Enable Co-processors
arm64: dts: ti: k3-am62a-phycore-som: Enable Co-processors
arm64: dts: ti: k3-am62a-phycore-som: Reserve main_rti4 for C7x DSP
arm64: dts: ti: k3-am62a-phycore-som: Reserve main_timer2 for C7x DSP
.../boot/dts/ti/k3-am62-phycore-som.dtsi | 35 +++++- .../boot/dts/ti/k3-am62a-phycore-som.dtsi | 106 +++++++++++++++++- 2 files changed, 129 insertions(+), 12 deletions(-)
Signature · 1 line
2.25.1
PATCH v2 1/4 arm64: dts: ti: k3-am62-phycore-som: Enable Co-processors
For every remote processor, set up dedicated memory regions and associate the required mailbox channels. Allocate two memory areas per remote core: one 1MB region for vring shared buffers, and another for external memory used by the remote processor for its resource table and trace buffer.
--- .../boot/dts/ti/k3-am62-phycore-som.dtsi | 35 +++++++++++++++---- 1 file changed, 29 insertions(+), 6 deletions(-)
arch/arm64/boot/dts/ti/k3-am62-phycore-som.dtsi +29 -6
@@ -64,6 +64,18 @@ mcu_m4fss_memory_region: m4f-memory@9cc00000 { no-map; }; + wkup_r5fss0_core0_dma_memory_region: r5f-dma-memory@9da00000 { + compatible = "shared-dma-pool"; + reg = <0x00 0x9da00000 0x00 0x100000>; + no-map; + }; + + wkup_r5fss0_core0_memory_region: r5f-memory@9db00000 { + compatible = "shared-dma-pool"; + reg = <0x00 0x9db00000 0x00 0xc00000>; + no-map; + }; + secure_tfa_ddr: tfa@9e780000 { reg = <0x00 0x9e780000 0x00 0x80000>; alignment = <0x1000>;
@@ -75,12 +87,6 @@ secure_ddr: optee@9e800000 { alignment = <0x1000>; no-map; }; - - wkup_r5fss0_core0_dma_memory_region: r5f-dma-memory@9db00000 { - compatible = "shared-dma-pool"; - reg = <0x00 0x9db00000 0x00 0x00c00000>; - no-map; - }; }; vcc_5v0_som: regulator-vcc-5v0-som {
@@ -240,10 +246,17 @@ cpsw3g_phy1: ethernet-phy@1 { }; &mailbox0_cluster0 { + status = "okay"; + mbox_m4_0: mbox-m4-0 { ti,mbox-rx = <0 0 0>; ti,mbox-tx = <1 0 0>; }; + + mbox_r5_0: mbox-r5-0 { + ti,mbox-rx = <2 0 0>; + ti,mbox-tx = <3 0 0>; + }; }; &main_pktdma {
@@ -386,3 +399,13 @@ &sdhci0 { bootph-all; status = "okay"; }; + +&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>; +};
Signature · 1 line
2.25.1
Re: [PATCH v2 1/4] arm64: dts: ti: k3-am62-phycore-som: Enable Co-processors
Am 06.05.25 um 16:36 schrieb Daniel Schultz:
Quoted 7 lines
For every remote processor, set up dedicated memory regions and associate the required mailbox channels. Allocate two memory areas per remote core: one 1MB region for vring shared buffers, and another for external memory used by the remote processor for its resource table and trace buffer.
Signed-off-by Daniel Schultz <[email protected]>
Quoted 72 lines
--- .../boot/dts/ti/k3-am62-phycore-som.dtsi | 35 +++++++++++++++---- 1 file changed, 29 insertions(+), 6 deletions(-)arch/arm64/boot/dts/ti/k3-am62-phycore-som.dtsi +29
-6@@ -64,6 +64,18 @@ mcu_m4fss_memory_region: m4f-memory@9cc00000 { no-map; }; + wkup_r5fss0_core0_dma_memory_region: r5f-dma-memory@9da00000 { + compatible = "shared-dma-pool"; + reg = <0x00 0x9da00000 0x00 0x100000>; + no-map; + }; + + wkup_r5fss0_core0_memory_region: r5f-memory@9db00000 { + compatible = "shared-dma-pool"; + reg = <0x00 0x9db00000 0x00 0xc00000>; + no-map; + }; + secure_tfa_ddr: tfa@9e780000 { reg = <0x00 0x9e780000 0x00 0x80000>; alignment = <0x1000>;@@ -75,12 +87,6 @@ secure_ddr: optee@9e800000 { alignment = <0x1000>; no-map; }; - - wkup_r5fss0_core0_dma_memory_region: r5f-dma-memory@9db00000 { - compatible = "shared-dma-pool"; - reg = <0x00 0x9db00000 0x00 0x00c00000>; - no-map; - }; }; vcc_5v0_som: regulator-vcc-5v0-som {@@ -240,10 +246,17 @@ cpsw3g_phy1: ethernet-phy@1 { }; &mailbox0_cluster0 { + status = "okay"; + mbox_m4_0: mbox-m4-0 { ti,mbox-rx = <0 0 0>; ti,mbox-tx = <1 0 0>; }; + + mbox_r5_0: mbox-r5-0 { + ti,mbox-rx = <2 0 0>; + ti,mbox-tx = <3 0 0>; + }; }; &main_pktdma {@@ -386,3 +399,13 @@ &sdhci0 { bootph-all; status = "okay"; }; + +&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>; +};
PATCH v2 2/4 arm64: dts: ti: k3-am62a-phycore-som: Enable Co-processors
In reply to Daniel SchultzFor every remote processor, set up dedicated memory regions and associate the required mailbox channels. Allocate two memory areas per remote core: one 1MB region for vring shared buffers, and another for external memory used by the remote processor for its resource table and trace buffer.
--- .../boot/dts/ti/k3-am62a-phycore-som.dtsi | 96 +++++++++++++++++-- 1 file changed, 90 insertions(+), 6 deletions(-)
arch/arm64/boot/dts/ti/k3-am62a-phycore-som.dtsi +90 -6
@@ -59,6 +59,42 @@ linux,cma { linux,cma-default; }; + c7x_0_dma_memory_region: c7x-dma-memory@99800000 { + compatible = "shared-dma-pool"; + reg = <0x00 0x99800000 0x00 0x100000>; + no-map; + }; + + c7x_0_memory_region: c7x-memory@99900000 { + compatible = "shared-dma-pool"; + reg = <0x00 0x99900000 0x00 0xf00000>; + no-map; + }; + + mcu_r5fss0_core0_dma_memory_region: r5f-dma-memory@9b800000 { + compatible = "shared-dma-pool"; + reg = <0x00 0x9b800000 0x00 0x100000>; + no-map; + }; + + mcu_r5fss0_core0_memory_region: r5f-dma-memory@9b900000 { + compatible = "shared-dma-pool"; + reg = <0x00 0x9b900000 0x00 0xf00000>; + no-map; + }; + + wkup_r5fss0_core0_dma_memory_region: r5f-dma-memory@9c800000 { + compatible = "shared-dma-pool"; + reg = <0x00 0x9c800000 0x00 0x100000>; + no-map; + }; + + wkup_r5fss0_core0_memory_region: r5f-dma-memory@9c900000 { + compatible = "shared-dma-pool"; + reg = <0x00 0x9c900000 0x00 0xf00000>; + no-map; + }; + secure_tfa_ddr: tfa@9e780000 { reg = <0x00 0x9e780000 0x00 0x80000>; alignment = <0x1000>;
@@ -70,12 +106,6 @@ secure_ddr: optee@9e800000 { alignment = <0x1000>; no-map; }; - - wkup_r5fss0_core0_memory_region: r5f-dma-memory@9c900000 { - compatible = "shared-dma-pool"; - reg = <0x00 0x9c900000 0x00 0x01e00000>; - no-map; - }; }; vcc_5v0_som: regulator-vcc-5v0-som {
@@ -170,6 +200,13 @@ AM62AX_IOPAD(0x1f4, PIN_INPUT, 0) /* (D16) EXTINTn */ }; }; +&c7x_0 { + mboxes = <&mailbox0_cluster1>, <&mbox_c7x_0>; + memory-region = <&c7x_0_dma_memory_region>, + <&c7x_0_memory_region>; + status = "okay"; +}; + &cpsw3g { pinctrl-names = "default"; pinctrl-0 = <&main_rgmii1_pins_default>;
@@ -200,6 +237,33 @@ &fss { status = "okay"; }; +&mailbox0_cluster0 { + status = "okay"; + + mbox_r5_0: mbox-r5-0 { + ti,mbox-rx = <0 0 0>; + ti,mbox-tx = <1 0 0>; + }; +}; + +&mailbox0_cluster1 { + status = "okay"; + + mbox_c7x_0: mbox-c7x-0 { + ti,mbox-rx = <0 0 0>; + ti,mbox-tx = <1 0 0>; + }; +}; + +&mailbox0_cluster2 { + status = "okay"; + + mbox_mcu_r5_0: mbox-mcu-r5-0 { + ti,mbox-rx = <0 0 0>; + ti,mbox-tx = <1 0 0>; + }; +}; + &main_i2c0 { pinctrl-names = "default"; pinctrl-0 = <&main_i2c0_pins_default>;
@@ -315,6 +379,16 @@ &main_pktdma { bootph-all; }; +&mcu_r5fss0 { + status = "okay"; +}; + +&mcu_r5fss0_core0 { + mboxes = <&mailbox0_cluster2>, <&mbox_mcu_r5_0>; + memory-region = <&mcu_r5fss0_core0_dma_memory_region>, + <&mcu_r5fss0_core0_memory_region>; +}; + &ospi0 { pinctrl-names = "default"; pinctrl-0 = <&ospi0_pins_default>;
@@ -343,3 +417,13 @@ &sdhci0 { bootph-all; status = "okay"; }; + +&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>; +};
Signature · 1 line
2.25.1
Re: [PATCH v2 2/4] arm64: dts: ti: k3-am62a-phycore-som: Enable Co-processors
Quoted 120 lines · Daniel Schultz
For every remote processor, set up dedicated memory regions and associate the required mailbox channels. Allocate two memory areas per remote core: one 1MB region for vring shared buffers, and another for external memory used by the remote processor for its resource table and trace buffer.
Signed-off-by Daniel Schultz <[email protected]>--- .../boot/dts/ti/k3-am62a-phycore-som.dtsi | 96 +++++++++++++++++-- 1 file changed, 90 insertions(+), 6 deletions(-)arch/arm64/boot/dts/ti/k3-am62a-phycore-som.dtsi +70
-6@@ -59,6 +59,42 @@ linux,cma { linux,cma-default; }; + c7x_0_dma_memory_region: c7x-dma-memory@99800000 { + compatible = "shared-dma-pool"; + reg = <0x00 0x99800000 0x00 0x100000>; + no-map; + }; + + c7x_0_memory_region: c7x-memory@99900000 { + compatible = "shared-dma-pool"; + reg = <0x00 0x99900000 0x00 0xf00000>; + no-map; + }; + + mcu_r5fss0_core0_dma_memory_region: r5f-dma-memory@9b800000 { + compatible = "shared-dma-pool"; + reg = <0x00 0x9b800000 0x00 0x100000>; + no-map; + }; + + mcu_r5fss0_core0_memory_region: r5f-dma-memory@9b900000 { + compatible = "shared-dma-pool"; + reg = <0x00 0x9b900000 0x00 0xf00000>; + no-map; + }; + + wkup_r5fss0_core0_dma_memory_region: r5f-dma-memory@9c800000 { + compatible = "shared-dma-pool"; + reg = <0x00 0x9c800000 0x00 0x100000>; + no-map; + }; + + wkup_r5fss0_core0_memory_region: r5f-dma-memory@9c900000 { + compatible = "shared-dma-pool"; + reg = <0x00 0x9c900000 0x00 0xf00000>; + no-map; + }; + secure_tfa_ddr: tfa@9e780000 { reg = <0x00 0x9e780000 0x00 0x80000>; alignment = <0x1000>;@@ -70,12 +106,6 @@ secure_ddr: optee@9e800000 { alignment = <0x1000>; no-map; }; - - wkup_r5fss0_core0_memory_region: r5f-dma-memory@9c900000 { - compatible = "shared-dma-pool"; - reg = <0x00 0x9c900000 0x00 0x01e00000>; - no-map; - }; }; vcc_5v0_som: regulator-vcc-5v0-som {@@ -170,6 +200,13 @@ AM62AX_IOPAD(0x1f4, PIN_INPUT, 0) /* (D16) EXTINTn */ }; }; +&c7x_0 { + mboxes = <&mailbox0_cluster1>, <&mbox_c7x_0>; + memory-region = <&c7x_0_dma_memory_region>, + <&c7x_0_memory_region>; + status = "okay"; +}; + &cpsw3g { pinctrl-names = "default"; pinctrl-0 = <&main_rgmii1_pins_default>;@@ -200,6 +237,33 @@ &fss { status = "okay"; }; +&mailbox0_cluster0 { + status = "okay"; + + mbox_r5_0: mbox-r5-0 { + ti,mbox-rx = <0 0 0>; + ti,mbox-tx = <1 0 0>; + }; +}; + +&mailbox0_cluster1 { + status = "okay"; + + mbox_c7x_0: mbox-c7x-0 { + ti,mbox-rx = <0 0 0>; + ti,mbox-tx = <1 0 0>; + }; +}; + +&mailbox0_cluster2 { + status = "okay"; + + mbox_mcu_r5_0: mbox-mcu-r5-0 { + ti,mbox-rx = <0 0 0>; + ti,mbox-tx = <1 0 0>; + }; +}; + &main_i2c0 { pinctrl-names = "default"; pinctrl-0 = <&main_i2c0_pins_default>;
arch/arm64/boot/dts/ti/k3-am62a-phycore-som.dtsi &main_pktdma { · line 387
Quoted 9 lines
arch/arm64/boot/dts/ti/k3-am62a-phycore-som.dtsi +6
-0@@ -315,6 +379,16 @@ &main_pktdma { bootph-all; }; +&mcu_r5fss0 { + status = "okay"; +}; + +&mcu_r5fss0_core0 { + mboxes = <&mailbox0_cluster2>, <&mbox_mcu_r5_0>;
These mboxes items should be combined as they are both part of a single two-element item, not a big deal for now as the output DTB is the same,
Quoted 21 lines
arch/arm64/boot/dts/ti/k3-am62a-phycore-som.dtsi +14
-0+ memory-region = <&mcu_r5fss0_core0_dma_memory_region>, + <&mcu_r5fss0_core0_memory_region>; +}; + &ospi0 { pinctrl-names = "default"; pinctrl-0 = <&ospi0_pins_default>;@@ -343,3 +417,13 @@ &sdhci0 { bootph-all; status = "okay"; }; + +&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>; +};
Re: [PATCH v2 2/4] arm64: dts: ti: k3-am62a-phycore-som: Enable Co-processors
Quoted 121 lines · Andrew Davis
Quoted 120 lines · Daniel Schultz
For every remote processor, set up dedicated memory regions and associate the required mailbox channels. Allocate two memory areas per remote core: one 1MB region for vring shared buffers, and another for external memory used by the remote processor for its resource table and trace buffer.
Signed-off-by Daniel Schultz <[email protected]>---
.../boot/dts/ti/k3-am62a-phycore-som.dtsi | 96 +++++++++++++++++--1 file changed, 90 insertions(+), 6 deletions(-)arch/arm64/boot/dts/ti/k3-am62a-phycore-som.dtsi +35
-6@@ -59,6 +59,42 @@ linux,cma { linux,cma-default; }; + c7x_0_dma_memory_region: c7x-dma-memory@99800000 { + compatible = "shared-dma-pool"; + reg = <0x00 0x99800000 0x00 0x100000>; + no-map; + }; + + c7x_0_memory_region: c7x-memory@99900000 { + compatible = "shared-dma-pool"; + reg = <0x00 0x99900000 0x00 0xf00000>; + no-map; + }; + + mcu_r5fss0_core0_dma_memory_region: r5f-dma-memory@9b800000 { + compatible = "shared-dma-pool"; + reg = <0x00 0x9b800000 0x00 0x100000>; + no-map; + }; + + mcu_r5fss0_core0_memory_region: r5f-dma-memory@9b900000 { + compatible = "shared-dma-pool"; + reg = <0x00 0x9b900000 0x00 0xf00000>; + no-map; + }; + + wkup_r5fss0_core0_dma_memory_region: r5f-dma-memory@9c800000 { + compatible = "shared-dma-pool"; + reg = <0x00 0x9c800000 0x00 0x100000>; + no-map; + }; + + wkup_r5fss0_core0_memory_region: r5f-dma-memory@9c900000 { + compatible = "shared-dma-pool"; + reg = <0x00 0x9c900000 0x00 0xf00000>; + no-map; + }; + secure_tfa_ddr: tfa@9e780000 { reg = <0x00 0x9e780000 0x00 0x80000>; alignment = <0x1000>;@@ -70,12 +106,6 @@ secure_ddr: optee@9e800000 { alignment = <0x1000>; no-map; }; - - wkup_r5fss0_core0_memory_region: r5f-dma-memory@9c900000 { - compatible = "shared-dma-pool"; - reg = <0x00 0x9c900000 0x00 0x01e00000>; - no-map; - }; }; vcc_5v0_som: regulator-vcc-5v0-som {@@ -170,6 +200,13 @@ AM62AX_IOPAD(0x1f4, PIN_INPUT, 0) /* (D16)EXTINTn */
};
};
+&c7x_0 {
+ mboxes = <&mailbox0_cluster1>, <&mbox_c7x_0>; + memory-region = <&c7x_0_dma_memory_region>, + <&c7x_0_memory_region>;
+ status = "okay";arch/arm64/boot/dts/ti/k3-am62a-phycore-som.dtsi +2
-0+}; +&cpsw3g {
pinctrl-names = "default";
pinctrl-0 = <&main_rgmii1_pins_default>;arch/arm64/boot/dts/ti/k3-am62a-phycore-som.dtsi +26
-0@@ -200,6 +237,33 @@ &fss { status = "okay"; }; +&mailbox0_cluster0 { + status = "okay"; + + mbox_r5_0: mbox-r5-0 { + ti,mbox-rx = <0 0 0>; + ti,mbox-tx = <1 0 0>; + }; +}; + +&mailbox0_cluster1 { + status = "okay"; + + mbox_c7x_0: mbox-c7x-0 { + ti,mbox-rx = <0 0 0>; + ti,mbox-tx = <1 0 0>; + }; +}; + +&mailbox0_cluster2 { + status = "okay"; + + mbox_mcu_r5_0: mbox-mcu-r5-0 { + ti,mbox-rx = <0 0 0>; + ti,mbox-tx = <1 0 0>; + }; +}; + &main_i2c0 { pinctrl-names = "default"; pinctrl-0 = <&main_i2c0_pins_default>;@@ -315,6 +379,16 @@ &main_pktdma { bootph-all; }; +&mcu_r5fss0 {
Quoted 8 lines
arch/arm64/boot/dts/ti/k3-am62a-phycore-som.dtsi &main_pktdma { · line 387
Quoted 5 lines
arch/arm64/boot/dts/ti/k3-am62a-phycore-som.dtsi +5
-0+ status = "okay"; +}; + +&mcu_r5fss0_core0 { + mboxes = <&mailbox0_cluster2>, <&mbox_mcu_r5_0>;These mboxes items should be combined as they are both part of a single two-element item, not a big deal for now as the output DTB is the same,
Yes, I can do that. Heads up this is copied from the recent k3-am62a7-sk update. You might wanna consider updating this board too.
- Daniel
Quoted 24 lines
Reviewed-by Andrew Davis <[email protected]>Quoted 21 lines
arch/arm64/boot/dts/ti/k3-am62a-phycore-som.dtsi +14
-0+ memory-region = <&mcu_r5fss0_core0_dma_memory_region>, + <&mcu_r5fss0_core0_memory_region>; +}; + &ospi0 { pinctrl-names = "default"; pinctrl-0 = <&ospi0_pins_default>;@@ -343,3 +417,13 @@ &sdhci0 { bootph-all; status = "okay"; }; + +&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>; +};
Re: [PATCH v2 2/4] arm64: dts: ti: k3-am62a-phycore-som: Enable Co-processors
In reply to Daniel SchultzAm 06.05.25 um 16:36 schrieb Daniel Schultz:
Quoted 18 lines
For every remote processor, set up dedicated memory regions and associate the required mailbox channels. Allocate two memory areas per remote core: one 1MB region for vring shared buffers, and another for external memory used by the remote processor for its resource table and trace buffer.
Signed-off-by Daniel Schultz <[email protected]>--- .../boot/dts/ti/k3-am62a-phycore-som.dtsi | 96 +++++++++++++++++-- 1 file changed, 90 insertions(+), 6 deletions(-)arch/arm64/boot/dts/ti/k3-am62a-phycore-som.dtsi +0
-0@@ -59,6 +59,42 @@ linux,cma { linux,cma-default; };
arch/arm64/boot/dts/ti/k3-am62a-phycore-som.dtsi linux,cma { · line 70
Quoted 10 lines
arch/arm64/boot/dts/ti/k3-am62a-phycore-som.dtsi +9
-0+ c7x_0_dma_memory_region: c7x-dma-memory@99800000 { + compatible = "shared-dma-pool"; + reg = <0x00 0x99800000 0x00 0x100000>; + no-map; + }; + + c7x_0_memory_region: c7x-memory@99900000 { + compatible = "shared-dma-pool"; + reg = <0x00 0x99900000 0x00 0xf00000>;
Just checked the origin of this for the am62a7-sk, which is https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/commit/?h=10.01.10&id=a82cef91b301e3a03a4efe0f49e6cb8cf50f43af
The size for the c7x-memory is 0x01f00000 and not 0xf00000
arch/arm64/boot/dts/ti/k3-am62a-phycore-som.dtsi linux,cma { · line 74
Quoted 4 lines
arch/arm64/boot/dts/ti/k3-am62a-phycore-som.dtsi +4
-0+ no-map; + }; + + mcu_r5fss0_core0_dma_memory_region: r5f-dma-memory@9b800000 {
which is relevant because your next reserved memory area starts at 0x9b800000 (would be fine with a size of 0x1f00000). If you really want to have a size of 0xf00000, your next block should start at 9A800000.
Can you please double check and use the free memory inbetween if 0xf00000 is correct.
Quoted 118 lines
arch/arm64/boot/dts/ti/k3-am62a-phycore-som.dtsi +77
-6+ compatible = "shared-dma-pool"; + reg = <0x00 0x9b800000 0x00 0x100000>; + no-map; + }; + + mcu_r5fss0_core0_memory_region: r5f-dma-memory@9b900000 { + compatible = "shared-dma-pool"; + reg = <0x00 0x9b900000 0x00 0xf00000>; + no-map; + }; + + wkup_r5fss0_core0_dma_memory_region: r5f-dma-memory@9c800000 { + compatible = "shared-dma-pool"; + reg = <0x00 0x9c800000 0x00 0x100000>; + no-map; + }; + + wkup_r5fss0_core0_memory_region: r5f-dma-memory@9c900000 { + compatible = "shared-dma-pool"; + reg = <0x00 0x9c900000 0x00 0xf00000>; + no-map; + }; + secure_tfa_ddr: tfa@9e780000 { reg = <0x00 0x9e780000 0x00 0x80000>; alignment = <0x1000>;@@ -70,12 +106,6 @@ secure_ddr: optee@9e800000 { alignment = <0x1000>; no-map; }; - - wkup_r5fss0_core0_memory_region: r5f-dma-memory@9c900000 { - compatible = "shared-dma-pool"; - reg = <0x00 0x9c900000 0x00 0x01e00000>; - no-map; - }; }; vcc_5v0_som: regulator-vcc-5v0-som {@@ -170,6 +200,13 @@ AM62AX_IOPAD(0x1f4, PIN_INPUT, 0) /* (D16) EXTINTn */ }; }; +&c7x_0 { + mboxes = <&mailbox0_cluster1>, <&mbox_c7x_0>; + memory-region = <&c7x_0_dma_memory_region>, + <&c7x_0_memory_region>; + status = "okay"; +}; + &cpsw3g { pinctrl-names = "default"; pinctrl-0 = <&main_rgmii1_pins_default>;@@ -200,6 +237,33 @@ &fss { status = "okay"; }; +&mailbox0_cluster0 { + status = "okay"; + + mbox_r5_0: mbox-r5-0 { + ti,mbox-rx = <0 0 0>; + ti,mbox-tx = <1 0 0>; + }; +}; + +&mailbox0_cluster1 { + status = "okay"; + + mbox_c7x_0: mbox-c7x-0 { + ti,mbox-rx = <0 0 0>; + ti,mbox-tx = <1 0 0>; + }; +}; + +&mailbox0_cluster2 { + status = "okay"; + + mbox_mcu_r5_0: mbox-mcu-r5-0 { + ti,mbox-rx = <0 0 0>; + ti,mbox-tx = <1 0 0>; + }; +}; + &main_i2c0 { pinctrl-names = "default"; pinctrl-0 = <&main_i2c0_pins_default>;@@ -315,6 +379,16 @@ &main_pktdma { bootph-all; }; +&mcu_r5fss0 { + status = "okay"; +}; + +&mcu_r5fss0_core0 { + mboxes = <&mailbox0_cluster2>, <&mbox_mcu_r5_0>; + memory-region = <&mcu_r5fss0_core0_dma_memory_region>, + <&mcu_r5fss0_core0_memory_region>; +}; + &ospi0 { pinctrl-names = "default"; pinctrl-0 = <&ospi0_pins_default>;@@ -343,3 +417,13 @@ &sdhci0 { bootph-all; status = "okay"; }; + +&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>; +};
Re: [PATCH v2 2/4] arm64: dts: ti: k3-am62a-phycore-som: Enable Co-processors
Quoted 33 lines · Wadim Egorov
Am 06.05.25 um 16:36 schrieb Daniel Schultz:
Quoted 17 lines
For every remote processor, set up dedicated memory regions and associate the required mailbox channels. Allocate two memory areas per remote core: one 1MB region for vring shared buffers, and another for external memory used by the remote processor for its resource table and trace buffer.
Signed-off-by Daniel Schultz <[email protected]>---
.../boot/dts/ti/k3-am62a-phycore-som.dtsi | 96 +++++++++++++++++--1 file changed, 90 insertions(+), 6 deletions(-)arch/arm64/boot/dts/ti/k3-am62a-phycore-som.dtsi +0
-0@@ -59,6 +59,42 @@ linux,cma { linux,cma-default;arch/arm64/boot/dts/ti/k3-am62a-phycore-som.dtsi linux,cma { · line 69
Quoted 10 lines
arch/arm64/boot/dts/ti/k3-am62a-phycore-som.dtsi +8
-0}; + c7x_0_dma_memory_region: c7x-dma-memory@99800000 { + compatible = "shared-dma-pool"; + reg = <0x00 0x99800000 0x00 0x100000>; + no-map; + }; + + c7x_0_memory_region: c7x-memory@99900000 { + compatible = "shared-dma-pool"; + reg = <0x00 0x99900000 0x00 0xf00000>;Just checked the origin of this for the am62a7-sk, which is https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/commit/?h=10.01.10&id=a82cef91b301e3a03a4efe0f49e6cb8cf50f43af
The size for the c7x-memory is
0x01f00000and not0xf00000
Quoted 8 lines
arch/arm64/boot/dts/ti/k3-am62a-phycore-som.dtsi linux,cma { · line 74
Quoted 4 lines
arch/arm64/boot/dts/ti/k3-am62a-phycore-som.dtsi +4
-0+ no-map; + }; + + mcu_r5fss0_core0_dma_memory_region: r5f-dma-memory@9b800000 {which is relevant because your next reserved memory area starts at
0x9b800000(would be fine with a size of0x1f00000). If you really want to have a size of0xf00000, your next block should start at 9A800000.Can you please double check and use the free memory inbetween if
0xf00000is correct.
Hi Wadim,
I copied all those nodes from the k3-am62a7-sk board update which just got merged [1]. I don't want to change that now because I'm afraid the default TI mcu firmware won't work with different addresses anymore.
@Andrew: FYI there is a gap now in reserved memory but I assume you're already aware.
- Daniel
Quoted 117 lines
Quoted 116 lines
arch/arm64/boot/dts/ti/k3-am62a-phycore-som.dtsi +23
-6+ compatible = "shared-dma-pool"; + reg = <0x00 0x9b800000 0x00 0x100000>; + no-map; + }; + + mcu_r5fss0_core0_memory_region: r5f-dma-memory@9b900000 { + compatible = "shared-dma-pool"; + reg = <0x00 0x9b900000 0x00 0xf00000>; + no-map; + }; + + wkup_r5fss0_core0_dma_memory_region: r5f-dma-memory@9c800000 { + compatible = "shared-dma-pool"; + reg = <0x00 0x9c800000 0x00 0x100000>; + no-map; + }; + + wkup_r5fss0_core0_memory_region: r5f-dma-memory@9c900000 { + compatible = "shared-dma-pool"; + reg = <0x00 0x9c900000 0x00 0xf00000>; + no-map; + }; + secure_tfa_ddr: tfa@9e780000 { reg = <0x00 0x9e780000 0x00 0x80000>; alignment = <0x1000>;@@ -70,12 +106,6 @@ secure_ddr: optee@9e800000 { alignment = <0x1000>; no-map; }; - - wkup_r5fss0_core0_memory_region: r5f-dma-memory@9c900000 { - compatible = "shared-dma-pool"; - reg = <0x00 0x9c900000 0x00 0x01e00000>; - no-map; - }; }; vcc_5v0_som: regulator-vcc-5v0-som {@@ -170,6 +200,13 @@ AM62AX_IOPAD(0x1f4, PIN_INPUT, 0) /* (D16)EXTINTn */
};
};
+&c7x_0 {
+ mboxes = <&mailbox0_cluster1>, <&mbox_c7x_0>; + memory-region = <&c7x_0_dma_memory_region>, + <&c7x_0_memory_region>;
+ status = "okay";arch/arm64/boot/dts/ti/k3-am62a-phycore-som.dtsi +2
-0+}; +&cpsw3g {
pinctrl-names = "default";
pinctrl-0 = <&main_rgmii1_pins_default>;arch/arm64/boot/dts/ti/k3-am62a-phycore-som.dtsi +45
-0@@ -200,6 +237,33 @@ &fss { status = "okay"; }; +&mailbox0_cluster0 { + status = "okay"; + + mbox_r5_0: mbox-r5-0 { + ti,mbox-rx = <0 0 0>; + ti,mbox-tx = <1 0 0>; + }; +}; + +&mailbox0_cluster1 { + status = "okay"; + + mbox_c7x_0: mbox-c7x-0 { + ti,mbox-rx = <0 0 0>; + ti,mbox-tx = <1 0 0>; + }; +}; + +&mailbox0_cluster2 { + status = "okay"; + + mbox_mcu_r5_0: mbox-mcu-r5-0 { + ti,mbox-rx = <0 0 0>; + ti,mbox-tx = <1 0 0>; + }; +}; + &main_i2c0 { pinctrl-names = "default"; pinctrl-0 = <&main_i2c0_pins_default>;@@ -315,6 +379,16 @@ &main_pktdma { bootph-all; }; +&mcu_r5fss0 { + status = "okay"; +}; + +&mcu_r5fss0_core0 { + mboxes = <&mailbox0_cluster2>, <&mbox_mcu_r5_0>; + memory-region = <&mcu_r5fss0_core0_dma_memory_region>, + <&mcu_r5fss0_core0_memory_region>; +}; + &ospi0 { pinctrl-names = "default"; pinctrl-0 = <&ospi0_pins_default>;@@ -343,3 +417,13 @@ &sdhci0 { bootph-all; status = "okay"; }; + +&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>; +};
PATCH v2 3/4 arm64: dts: ti: k3-am62a-phycore-som: Reserve main_rti4 for C7x DSP
In reply to Daniel SchultzThe main rti4 watchdog timer is used by the C7x DSP, so reserve the timer in the linux device tree.
--- arch/arm64/boot/dts/ti/k3-am62a-phycore-som.dtsi | 5 +++++ 1 file changed, 5 insertions(+)
arch/arm64/boot/dts/ti/k3-am62a-phycore-som.dtsi +5 -0
@@ -379,6 +379,11 @@ &main_pktdma { bootph-all; }; +/* main_rti4 is used by C7x DSP */ +&main_rti4 { + status = "reserved"; +}; + &mcu_r5fss0 { status = "okay"; };
Signature · 1 line
2.25.1
PATCH v2 4/4 arm64: dts: ti: k3-am62a-phycore-som: Reserve main_timer2 for C7x DSP
In reply to Daniel SchultzC7x DSP uses main_timer2, so mark it as reserved in linux DT.
--- arch/arm64/boot/dts/ti/k3-am62a-phycore-som.dtsi | 5 +++++ 1 file changed, 5 insertions(+)
arch/arm64/boot/dts/ti/k3-am62a-phycore-som.dtsi +5 -0
@@ -384,6 +384,11 @@ &main_rti4 { status = "reserved"; }; +/* main_timer2 is used by C7x DSP */ +&main_timer2 { + status = "reserved"; +}; + &mcu_r5fss0 { status = "okay"; };
Signature · 1 line
2.25.1