diff options
author | Tony Lindgren <tony@atomide.com> | 2017-10-11 00:23:27 +0300 |
---|---|---|
committer | Tony Lindgren <tony@atomide.com> | 2017-10-11 00:23:27 +0300 |
commit | 6c72b35506728b2669835cfa8c245ac3f1c15659 (patch) | |
tree | 87fc2ea46f054f73a9560c08178e7c41f1c93da9 /arch/arm/mach-omap2/omap_device.c | |
parent | f09de60e0ae3440a139b516d579d866890ff3101 (diff) | |
download | linux-6c72b35506728b2669835cfa8c245ac3f1c15659.tar.xz |
ARM: OMAP2+: Parse module IO range from dts for legacy "ti,hwmods" support
When removing legacy platform data for IO ranges for the hwmod
interconnect code, we still need to support the "ti,hwmods"
property.
And as we're going to use a generic sysc device driver to handle the
interconnect target instances, we can parse the information needed
for legacy "ti,hwmods" IO range from the dts. It's always the first
range the interconnect target module provides.
Note that we want to parse the range instead of the first child
device IO regs as the child device may not always be defined.
The child IP device node may not exist in cases where there is no
driver binding for the device, or when the child IP block may not
even be functional for some SoC revisions. But the IO range of the
interconnect target module is always known.
Cc: "BenoƮt Cousson" <bcousson@baylibre.com>
Cc: Lokesh Vutla <lokeshvutla@ti.com>
Cc: Paul Walmsley <paul@pwsan.com>
Cc: Tero Kristo <t-kristo@ti.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
Diffstat (limited to 'arch/arm/mach-omap2/omap_device.c')
0 files changed, 0 insertions, 0 deletions