On 8/8/24 4:29 PM, Jonathan Humphreys wrote:
Upstream DTS added explicit ranges to the fss node. It did not include the
32 bit memory space needed by the R5 to access OSPI. With the upstream DTS
sync, OSPI boot no longer works.
Adding the missing range here. It is also being added in the upstream DTS,
so after the next upstream DTS sync, this patch can be removed. See
f062a015f4 (arm64: dts: ti: k3-j784s4: Use exact ranges for FSS node)
Fixes: 5024a96db8e (Subtree merge tag 'v6.10-dts' of devicetree-rebasing
repo [1] into dts/upstream)
Signed-off-by: Jonathan Humphreys <j-humphr...@ti.com>
---
arch/arm/dts/k3-j784s4-r5-evm.dts | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/dts/k3-j784s4-r5-evm.dts
b/arch/arm/dts/k3-j784s4-r5-evm.dts
index bef4573d3d2..26af72d73f4 100644
--- a/arch/arm/dts/k3-j784s4-r5-evm.dts
+++ b/arch/arm/dts/k3-j784s4-r5-evm.dts
@@ -97,6 +97,12 @@
<0x0 0x58000000 0x0 0x8000000>;
};
+&fss {
+ /* enable ranges missing from the fss node */
+ ranges = <0x0 0x47000000 0x0 0x47000000 0x0 0x00068400>,
+ <0x0 0x50000000 0x0 0x50000000 0x0
0x08000000>;
Looks like way too many tabs, do you have your editor set to 8 space tabs for
DTS files?
Otherwise, LGTM,
Reviewed-by: Andrew Davis <a...@ti.com>
+};
+
&mcu_ringacc {
ti,sci = <&dm_tifs>;
};
