ARM: dts: am335x: Move l4 child devices to probe them with ti-sysc
authorTony Lindgren <tony@atomide.com>
Mon, 24 Sep 2018 23:20:54 +0000 (16:20 -0700)
committerTony Lindgren <tony@atomide.com>
Thu, 18 Oct 2018 17:04:02 +0000 (10:04 -0700)
commit87fc89ced3a78f7f0845afab1934d509ef4ad0f2
treecabbb9da3d0df7112b8b606e00daa0ef09491b40
parentf711c575cfeca820b97bbec8d05c958e82f5fec4
ARM: dts: am335x: 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/am335x-shc.dts
arch/arm/boot/dts/am33xx-l4.dtsi
arch/arm/boot/dts/am33xx.dtsi