Start using ti-sysc with device tree data for omap4 l4 devices

With ti-sysc driver working for most use cases, we can start converting
the omap variant SoCs to use device tree data for the interconnect target
modules instead of the legacy hwmod platform data.

We start with omap4 l4 devices excluding the ones that still depend on
a reset controller driver like DSP MMU. And we don't yet convert the l4
ABE instance as that needs a bit more work.

We also add a proper interconnect hierarchy for the devices while at it
to make further work on genpd easier and to avoid most deferred probe
issues.

At this point we are not dropping any platform data, and we initially
still use it to validate the dts data. Then in later merge cycles we
can start dropping the related platform data.
-----BEGIN PGP SIGNATURE-----

iQJFBAABCAAvFiEEkgNvrZJU/QSQYIcQG9Q+yVyrpXMFAltS0McRHHRvbnlAYXRv
bWlkZS5jb20ACgkQG9Q+yVyrpXPzMRAAzU9qSt0HLJfP8P+8iHX3Lm6TJgslDNqP
tOkifKoL1ELfieiJhcNfMTHhXwgwzYLhjHV+YuVyBKwMdiaJmkP9P7V3SGTEwX3c
shAdK/+OsFJLpqXSZZqi2VApfGCjHJULICiDtalbNRYUyrZ6q9fm0C5nFxa6gH9z
ZIrURQClfHYlPFUIQW+LBvv3oUkV5JxTn8DksOlF1MvqMqxgVYSbcZ032mEowuNG
4j1mUk6ZMcKHmWhKpR2iGj3DGhDjvJGJ1J45WZViN7/Vbct41YLeJ9lSNLY+60R7
6KdxoBM1G/G01t73wcoQrSReIuk7NV4lx2H1z1KxuWYMnATCBOgPg1Ug82PdkGdP
EBMilB30rPhi/RQFKmhVYymHSn7falnUrE3CfErOGshyhdywdzdHCohSQZjizdjc
npW46R0XhQjBkY8+JQjAliPNa6JvMlilDd9dKFaucL5pFd35QDn/6NQ7rQu8EIWM
QpANfOEU2yLQ2m6GFUVz5JOwLojyD3LEKv5HkZRLXd5CzLrn2uW/TyrICIBp8/Pv
bNQhtYaMm6T8407zMjUWGyCqiY0rDuAr6mLtY8JpHgbBMTL8hssmpfSFQW69o0KI
ciWOu/KYVetl8nUodVobWY3rkpirHv2WqOU+9AjeiXqO+147HqzUteHV9ZpYRHS0
tSU6+383Jkc=
=ATsi
-----END PGP SIGNATURE-----