OMAP3 has PM_<processor_name>GRPSEL_<domain_name> registers
which can be programmed to allow a peripheral to choose a
processor group which it expects to wake up.
This RFC series is an attempt to provide omap_device layer
api's for drivers to be able to do this instead of direct
PRCM accesses within drivers which is the case today.
Something similar exists on OMAP4, in the form of
wakeup dependencies, which are not addressed in this
series for now.
Rajendra Nayak (3):
OMAP3: PRM: Add grpsel programming support
OMAP3: hwmod: Add support to associate an initiator with a hwmod
OMAP3: omap_device: Add support to associate a device with an
initiator
arch/arm/mach-omap2/omap_hwmod.c | 33 ++++++++++++
arch/arm/mach-omap2/prcm-common.h | 1 -
arch/arm/mach-omap2/prm2xxx_3xxx.c | 70 ++++++++++++++++++++++++++
arch/arm/mach-omap2/prm2xxx_3xxx.h | 4 ++
arch/arm/plat-omap/include/plat/omap_hwmod.h | 9 +++
arch/arm/plat-omap/omap_device.c | 54 ++++++++++++++++++++
6 files changed, 170 insertions(+), 1 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
