ARM: dts: am437x: Move l4 child devices to probe them with ti-sysc
authorTony Lindgren <tony@atomide.com>
Mon, 24 Sep 2018 23:22:37 +0000 (16:22 -0700)
committerTony Lindgren <tony@atomide.com>
Thu, 18 Oct 2018 17:04:01 +0000 (10:04 -0700)
commitd95adfd4585305ba52f56b8351cdd21842f9354a
tree536f9cdecb6964be41123178553b0210ebad6b4c
parent21c0607cc40d2ae169e2d3ddd10ed0e43206032f
ARM: dts: am437x: Move l4 child devices to probe them with ti-sysc

With l4 interconnect hierarchy and ti-sysc interconnect target module
data in place, we can simply move all the related child devices to
their proper location and enable probing using ti-sysc.

In general the first child device address range starts at range 0
from the ti-sysc interconnect target so the move involves adjusting
the child device reg properties for that.

In case of any regressions, problem devices can be reverted to probe
with legacy platform data as needed by moving them back and removing
the related interconnect target module node.

Note that we are not yet moving dss or wkup_m3, those will be moved
later after some related driver changes.

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>
arch/arm/boot/dts/am4372.dtsi
arch/arm/boot/dts/am437x-l4.dtsi