arm64: dts: ti: k3-j721e-sk: Fix reversed C6x carveout locations

[ Upstream commit 9f3814a7c06b7c7296cf8c1622078ad71820454b ]

The DMA carveout for the C6x core 0 is at 0xa6000000 and core 1 is at
0xa7000000. These are reversed in DT. While both C6x can access either
region, so this is not normally a problem, but if we start restricting
the memory each core can access (such as with firewalls) the cores
accessing the regions for the wrong core will not work. Fix this here.

Fixes: f46d16cf5b43 ("arm64: dts: ti: k3-j721e-sk: Add DDR carveout memory nodes")
Signed-off-by: Andrew Davis <afd@ti.com>
Link: https://lore.kernel.org/r/20240801181232.55027-1-afd@ti.com
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>

diff --git a/arch/arm64/boot/dts/ti/k3-j721e-sk.dts b/arch/arm64/boot/dts/ti/k3-j721e-sk.dts
index 42fe8eee9ec8c7e15a149725e49cbc04109c6770..ccacb65683b5b09f4c0e693726c1d81c9037e8d8 100644 (file)
--- a/arch/arm64/boot/dts/ti/k3-j721e-sk.dts
+++ b/arch/arm64/boot/dts/ti/k3-j721e-sk.dts
@@ -119,7 +119,7 @@
                        no-map;
                };
 
-               c66_1_dma_memory_region: c66-dma-memory@a6000000 {
+               c66_0_dma_memory_region: c66-dma-memory@a6000000 {
                        compatible = "shared-dma-pool";
                        reg = <0x00 0xa6000000 0x00 0x100000>;
                        no-map;
@@ -131,7 +131,7 @@
                        no-map;
                };
 
-               c66_0_dma_memory_region: c66-dma-memory@a7000000 {
+               c66_1_dma_memory_region: c66-dma-memory@a7000000 {
                        compatible = "shared-dma-pool";
                        reg = <0x00 0xa7000000 0x00 0x100000>;
                        no-map;