aboutsummaryrefslogtreecommitdiffstats
path: root/arch/arm/boot/dts/am33xx.dtsi
diff options
context:
space:
mode:
authorTony Lindgren <tony@atomide.com>2018-09-24 16:20:37 -0700
committerTony Lindgren <tony@atomide.com>2018-10-18 10:04:02 -0700
commitf711c575cfeca820b97bbec8d05c958e82f5fec4 (patch)
treeaa95861813131ce049b28cd9d20c8026c243e92a /arch/arm/boot/dts/am33xx.dtsi
parentARM: dts: am437x: Move l4 child devices to probe them with ti-sysc (diff)
downloadlinux-dev-f711c575cfeca820b97bbec8d05c958e82f5fec4.tar.xz
linux-dev-f711c575cfeca820b97bbec8d05c958e82f5fec4.zip
ARM: dts: am335x: Add l4 interconnect hierarchy and ti-sysc data
Similar to commit 8f42cb7f64c7 ("ARM: dts: omap4: Add l4 interconnect hierarchy and ti-sysc data"), let's add proper interconnect hierarchy for l4 interconnect instances with the related ti-sysc interconnect module data as in Documentation/devicetree/bindings/bus/ti-sysc.txt. Using ti-sysc driver binding allows us to start dropping legacy platform data in arch/arm/mach-omap2/omap*hwmod*data.c files later on in favor of ti-sysc dts data. This data is generated based on platform data from a booted system and the interconnect acces protection registers for ranges. To avoid regressions, we initially validate the device tree provided data against the existing platform data on boot. Note that we cannot yet include this file from the SoC dtsi file until the child devices are moved to their proper locations in the interconnect hierarchy in the following patch. Otherwise we would have the each module probed twice. Cc: Dave Gerlach <d-gerlach@ti.com> Cc: Keerthy <j-keerthy@ti.com> Cc: Tero Kristo <t-kristo@ti.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
Diffstat (limited to 'arch/arm/boot/dts/am33xx.dtsi')
0 files changed, 0 insertions, 0 deletions