summaryrefslogtreecommitdiff
path: root/arch/arm/boot/dts/am4372.dtsi
diff options
context:
space:
mode:
authorTony Lindgren <tony@atomide.com>2018-10-18 19:32:02 +0300
committerTony Lindgren <tony@atomide.com>2018-10-18 20:04:01 +0300
commit21c0607cc40d2ae169e2d3ddd10ed0e43206032f (patch)
tree6044b0a8deb592474edc281f711177ff2430044b /arch/arm/boot/dts/am4372.dtsi
parentb5f8ffbb6fad9151634805c2001af4afbb884eca (diff)
downloadlinux-21c0607cc40d2ae169e2d3ddd10ed0e43206032f.tar.xz
ARM: dts: am437x: 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/am4372.dtsi')
0 files changed, 0 insertions, 0 deletions