From: Kevin Hilman <[email protected]>

This series is a cleanup/reorg/streamline of the core idle path.

The goal is to remove all device-specific idle management out of the
core idle path into device-specific code.  

This series starts with some of the device-specific hacks currently in
the idle path, and also moves GPIO handling out of the core idle loop.

Eventually, all device-specific idle management should be done using
the runtime PM hooks of the driver for that device.  Until then,
temporary hacks belong in the new omap3_device_[idle|resume] functions.

Note that for debug purposes, UART is still managed inside the
interrupt-disabled idle path.  This is for debug purposes only so that
any panic/BUG code that gets triggered before the device resume code
is run will not crash the system.  As soon as the new omap-serial
driver is converted to runtime PM, the UART management can be removed
from the idle path as well.

Patch 1 will be queued in my pm-next branch for .37 and patch 2 should
be incorporated into baseline for the GPIO hwmod conversion.

Kevin Hilman (2):
  OMAP3: PM: move device-specific special cases from PM core into
    CPUidle
  OMAP2+: GPIO: move late PM out of interrupts-disabled idle path

 arch/arm/mach-omap2/cpuidle34xx.c      |   54 ++++++++++++++++++++++++++++--
 arch/arm/mach-omap2/pm.h               |    2 +
 arch/arm/mach-omap2/pm24xx.c           |    2 +-
 arch/arm/mach-omap2/pm34xx.c           |   48 ++++++++------------------
 arch/arm/plat-omap/gpio.c              |   57 ++++++++++++++++++++++++--------
 arch/arm/plat-omap/include/plat/gpio.h |    4 +--
 6 files changed, 113 insertions(+), 54 deletions(-)

-- 
1.7.2.1

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to