diff options
author | Tony Lindgren <tony@atomide.com> | 2018-11-09 13:41:13 -0800 |
---|---|---|
committer | Tony Lindgren <tony@atomide.com> | 2018-11-09 13:41:13 -0800 |
commit | 4c387984618fe65d87384ca2725661715607bec9 (patch) | |
tree | fb5d806c41934c1706966d41feeb580a5fffb31f /arch/arm/boot/dts/am33xx.dtsi | |
parent | ARM: dts: Use dra7 mcasp compatible for mcasp instances (diff) | |
download | linux-dev-4c387984618fe65d87384ca2725661715607bec9.tar.xz linux-dev-4c387984618fe65d87384ca2725661715607bec9.zip |
ARM: dts: omap5: 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.
Cc: devicetree@vger.kernel.org
Signed-off-by: Tony Lindgren <tony@atomide.com>
Diffstat (limited to 'arch/arm/boot/dts/am33xx.dtsi')
0 files changed, 0 insertions, 0 deletions