[PATCH 0/3] cpuidle: (powernv) cpuidle driver.

[Deepthi Dharwar]

Following patch series ports the cpuidle framework for powernv
platform and also implements a cpuidle back-end powernv 
idle driver calling on to power7_nap and snooze idle states.

Moving the idle states over to cpuidle framework can take advantage 
of advanced heuristics, tunables and features provided by cpuidle 
framework. Additional idle states can be exploited using the cpuidle 
framework. The statistics and tracing infrastructure provided by 
the cpuidle framework also helps in enabling power management 
related tools and help tune the system and applications.

This series aims to maintain compatibility and functionality to
existing powernv idle cpu management code.  There are no new functions
or idle states added as part of this series. This can be extended by 
adding more states to this existing framework.

With this patch series the powernv cpuidle functionalities
are on-par with pSeries idle management.

For POWERNV platform to hook into CPUIDLE framework, one
needs to enable CONFIG_POWERNV_IDLE and disable
CONFIG_PSERIES_IDLE 

 Deepthi Dharwar (3):
      cpuidle/powernv: cpuidle backend driver for powernv
      cpuidle/powernv: Enable idle powernv cpu to call into the cpuidle framework.
      cpuidle/powernv: Support smt-snooze-delay parameter in powernv idle.


 arch/powerpc/include/asm/processor.h            |    2 
 arch/powerpc/platforms/powernv/Kconfig          |    9 +
 arch/powerpc/platforms/powernv/Makefile         |    1 
 arch/powerpc/platforms/powernv/powernv.h        |    3 
 arch/powerpc/platforms/powernv/processor_idle.c |  275 +++++++++++++++++++++++
 arch/powerpc/platforms/powernv/setup.c          |   12 +
 6 files changed, 300 insertions(+), 2 deletions(-)
 create mode 100644 arch/powerpc/platforms/powernv/processor_idle.c


-- Deepthi

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/