summaryrefslogtreecommitdiff
path: root/arch/arm64/boot/dts/ti/k3-j7200-main.dtsi
diff options
context:
space:
mode:
authorNishanth Menon <nm@ti.com>2021-05-10 17:54:29 +0300
committerNishanth Menon <nm@ti.com>2021-05-14 20:47:48 +0300
commit9ecdb6d6b11434494af4bad11b03f0dcda1eebbd (patch)
treebbce9d4461f0010fb9052010536dcbc469f2d3e2 /arch/arm64/boot/dts/ti/k3-j7200-main.dtsi
parent9d3c9378f96a95f15881ee3373d2c2f773273fc2 (diff)
downloadlinux-9ecdb6d6b11434494af4bad11b03f0dcda1eebbd.tar.xz
arm64: dts: ti: k3-am65|j721e|am64: Map the dma / navigator subsystem via explicit ranges
Instead of using empty ranges property, lets map explicitly the address range that is mapped onto the dma / navigator subsystems (navss/dmss). This is also exposed via the dtbs_check with dt-schema newer than 2021.03 version by throwing out following: arch/arm64/boot/dts/ti/k3-am654-base-board.dt.yaml: bus@100000: main-navss: {'type': 'object'} is not allowed for {'compatible': ['simple-mfd'], '#address-cells': [[2]], ..... This has already been correctly done for J7200, however was missed for other k3 SoCs. Fix that oversight. Signed-off-by: Nishanth Menon <nm@ti.com> Reviewed-by: Tero Kristo <kristo@kernel.org> Acked-by: Vignesh Raghavendra <vigneshr@ti.com> Link: https://lore.kernel.org/r/20210510145429.8752-1-nm@ti.com
Diffstat (limited to 'arch/arm64/boot/dts/ti/k3-j7200-main.dtsi')
0 files changed, 0 insertions, 0 deletions