[PATCH v2 0/5] arch: arm: dts: ti: Add missing fss range
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, these patches can be removed.
Fixes: 5024a96db8e (Subtree merge tag 'v6.10-dts' of devicetree-rebasing repo [1] into dts/upstream)
Changes from v1: - Fixup tab whitespace alignment Link to v1: https://lore.kernel.org/r/20240808212926.3790223-1-j-humphreys@ti.com
Jonathan Humphreys (5): arch: arm: dts: k3-j784s4-r5-evm: Add missing fss range arch: arm: dts: k3-am69-r5-sk: Add missing fss range arch: arm: dts: k3-j7200-r5-evm: Add missing fss range arch: arm: dts: k3-j721e-r5-evm: Add missing fss range arch: arm: dts: k3-j721e-r5-sk: Add missing fss range
arch/arm/dts/k3-am69-r5-sk.dts | 6 ++++++ arch/arm/dts/k3-j7200-r5-common-proc-board.dts | 6 ++++++ arch/arm/dts/k3-j721e-r5-common-proc-board.dts | 6 ++++++ arch/arm/dts/k3-j721e-r5-sk.dts | 6 ++++++ arch/arm/dts/k3-j784s4-r5-evm.dts | 6 ++++++ 5 files changed, 30 insertions(+)
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-humphreys@ti.com Reviewed-by: Andrew Davis afd@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..db963828916 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>; +}; + &mcu_ringacc { ti,sci = <&dm_tifs>; };
On 8/9/24 4:17 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
Fixes tags have "" around the name of the offending commit, and the name does not linewrap, even if it is more than 80 chars.
repo [1] into dts/upstream)
No newline.
Signed-off-by: Jonathan Humphreys j-humphreys@ti.com Reviewed-by: Andrew Davis afd@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..db963828916 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 */
s/fss/FSS/
Andrew
- ranges = <0x0 0x47000000 0x0 0x47000000 0x0 0x00068400>,
<0x0 0x50000000 0x0 0x50000000 0x0 0x08000000>;+};
- &mcu_ringacc { ti,sci = <&dm_tifs>; };
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-humphreys@ti.com --- arch/arm/dts/k3-am69-r5-sk.dts | 6 ++++++ 1 file changed, 6 insertions(+)
diff --git a/arch/arm/dts/k3-am69-r5-sk.dts b/arch/arm/dts/k3-am69-r5-sk.dts index f177f563527..cbf51a8aed5 100644 --- a/arch/arm/dts/k3-am69-r5-sk.dts +++ b/arch/arm/dts/k3-am69-r5-sk.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>; +}; + &mcu_ringacc { ti,sci = <&dm_tifs>; };
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 f00e626085 (arm64: dts: ti: k3-j7200: 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-humphreys@ti.com --- arch/arm/dts/k3-j7200-r5-common-proc-board.dts | 6 ++++++ 1 file changed, 6 insertions(+)
diff --git a/arch/arm/dts/k3-j7200-r5-common-proc-board.dts b/arch/arm/dts/k3-j7200-r5-common-proc-board.dts index fb7e2e50239..2061adbcea3 100644 --- a/arch/arm/dts/k3-j7200-r5-common-proc-board.dts +++ b/arch/arm/dts/k3-j7200-r5-common-proc-board.dts @@ -89,6 +89,12 @@ <0x0 0x50000000 0x0 0x8000000>; };
+&fss { + /* enable ranges missing from the fss node */ + ranges = <0x0 0x47000000 0x0 0x47000000 0x0 0x00068400>, + <0x0 0x50000000 0x0 0x50000000 0x0 0x08000000>; +}; + &mcu_ringacc { ti,sci = <&dm_tifs>; };
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 0c0e03ec22 (arm64: dts: ti: k3-j721e: 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-humphreys@ti.com --- arch/arm/dts/k3-j721e-r5-common-proc-board.dts | 6 ++++++ 1 file changed, 6 insertions(+)
diff --git a/arch/arm/dts/k3-j721e-r5-common-proc-board.dts b/arch/arm/dts/k3-j721e-r5-common-proc-board.dts index c7e344350c8..73c0382c519 100644 --- a/arch/arm/dts/k3-j721e-r5-common-proc-board.dts +++ b/arch/arm/dts/k3-j721e-r5-common-proc-board.dts @@ -62,3 +62,9 @@ reg = <0x0 0x47050000 0x0 0x100>, <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>; +};
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 0c0e03ec22 (arm64: dts: ti: k3-j721e: 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-humphreys@ti.com --- arch/arm/dts/k3-j721e-r5-sk.dts | 6 ++++++ 1 file changed, 6 insertions(+)
diff --git a/arch/arm/dts/k3-j721e-r5-sk.dts b/arch/arm/dts/k3-j721e-r5-sk.dts index 96a13b2cb2b..a21812c4c5b 100644 --- a/arch/arm/dts/k3-j721e-r5-sk.dts +++ b/arch/arm/dts/k3-j721e-r5-sk.dts @@ -57,3 +57,9 @@ reg = <0x0 0x47040000 0x0 0x100>, <0x0 0x50000000 0x0 0x8000000>; }; + +&fss { + /* enable ranges missing from the fss node */ + ranges = <0x0 0x47000000 0x0 0x47000000 0x0 0x00068400>, + <0x0 0x50000000 0x0 0x50000000 0x0 0x08000000>; +};
participants (2)
-
Andrew Davis -
Jonathan Humphreys