Mailing List Archive: [PATCH 1/4] arm64: dts: ti: k3-am65: Use exact ranges for FSS node

The FSS bus contains several register ranges. Using an empty
ranges property works but causes a DT warning when we give
this node an address. Fix this by explicitly defining the
memory ranges in use.

Signed-off-by: Andrew Davis <afd@ti.com>
---
arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi b/arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi
index 6ff3ccc39fb44..babfcbb9ecf56 100644
--- a/arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi
@@ -286,7 +286,11 @@ fss: bus@47000000 {
compatible = "simple-bus";
#address-cells = <2>;
#size-cells = <2>;
- ranges;
+ ranges = <0x0 0x47000000 0x0 0x47000000 0x0 0x100>, /* FSS Control */
+ <0x0 0x47040000 0x0 0x47040000 0x0 0x100>, /* OSPI0 Control */
+ <0x0 0x47050000 0x0 0x47050000 0x0 0x100>, /* OSPI1 Control */
+ <0x5 0x00000000 0x5 0x00000000 0x1 0x0000000>, /* OSPI0 Memory */
+ <0x7 0x00000000 0x7 0x00000000 0x1 0x0000000>; /* OSPI1 Memory */

ospi0: spi@47040000 {
compatible = "ti,am654-ospi", "cdns,qspi-nor";
--
2.39.2

Hi Andrew Davis,

On Tue, 26 Mar 2024 15:59:17 -0500, Andrew Davis wrote:
> The FSS bus contains several register ranges. Using an empty
> ranges property works but causes a DT warning when we give
> this node an address. Fix this by explicitly defining the
> memory ranges in use.
>
>

I have applied the following to branch ti-k3-dts-next on [1].
Thank you!

[1/4] arm64: dts: ti: k3-am65: Use exact ranges for FSS node
commit: 8ec19dbe9217edbb564b16a5f68465b8cd42a167
[2/4] arm64: dts: ti: k3-j7200: Use exact ranges for FSS node
commit: 98b939a9b3204120bd3a96015d74cbe818a3a2e9
[3/4] arm64: dts: ti: k3-j721e: Use exact ranges for FSS node
commit: 74904fc1f1f1c802eaed10edc3744f0997c154ff
[4/4] arm64: dts: ti: k3-j784s4: Use exact ranges for FSS node
commit: b3f629482cade3a6ada44d2e83dd65f0f1ed1293

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D