summaryrefslogtreecommitdiffstats
path: root/arch/arm/mach-omap2/omap_hwmod.c
diff options
context:
space:
mode:
authorTony Lindgren <tony@atomide.com>2018-02-22 14:03:48 -0800
committerTony Lindgren <tony@atomide.com>2018-02-26 14:16:11 -0800
commita885f0fe209f262efa2c1cac9278a5774e5f7a80 (patch)
tree58e72236564523bc944d3c3f57332544f193f593 /arch/arm/mach-omap2/omap_hwmod.c
parentef70b0bdeaf893dd6d9c3a8d05d9b65d395506c0 (diff)
downloadtalos-obmc-linux-a885f0fe209f262efa2c1cac9278a5774e5f7a80.tar.gz
talos-obmc-linux-a885f0fe209f262efa2c1cac9278a5774e5f7a80.zip
bus: ti-sysc: Handle some devices in omap_device compatible way
Now that ti-sysc can manage child devices, we must also be backwards compatible with the current omap_device code. With omap_device, we assume that the child device manages the interconnect target module directly. The drivers needing special handling are the ones that still set pm_runtime_irq_safe(). In the long run we want to update those drivers as otherwise they will cause problems with genpd as a permanent PM runtime usage count is set on the parent device. We can handle omap_device these devices by improving the ti-sysc quirk handling to detect the devices needing special handling based on register map and revision register if usable. We also need to implement dev_pm_domain for these child devices just like omap_device does. Signed-off-by: Tony Lindgren <tony@atomide.com>
Diffstat (limited to 'arch/arm/mach-omap2/omap_hwmod.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud