On Wed, Aug 30, 2017 at 08:19:39AM -0700, Tony Lindgren wrote:
On omap4, we are missing several ti,hwmods properties and IO
ranges for system control modules. These are needed by the SoC
interconnect code.
Note that this will only show up as a bug with "doesn't have
mpu register target base" boot errors when the legacy platform
data is removed.
In order to add these, we need to move omap4_pmx_wkup to be a
child of omap4_padconf_wkup.
On omap4 there are separate modules for control module and
control module pads. For control module core, we have this
already configured except for the missing ti,hwmods and reg
entries.
Cc: Mark Rutland <redacted>
Cc: Rob Herring <redacted>
Signed-off-by: Tony Lindgren <redacted>
---
.../devicetree/bindings/arm/omap/ctrl.txt | 2 ++
arch/arm/boot/dts/omap4.dtsi | 39 ++++++++++++++++------
2 files changed, 31 insertions(+), 10 deletions(-)
Acked-by: Rob Herring <redacted>
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html