diff options
| author | Rafael J. Wysocki <rjw@sisk.pl> | 2009-08-18 23:38:32 +0200 |
|---|---|---|
| committer | Rafael J. Wysocki <rjw@sisk.pl> | 2009-08-23 00:04:44 +0200 |
| commit | 5e928f77a09a07f9dd595bb8a489965d69a83458 (patch) | |
| tree | ef53ec90fa3214fd22e36b07c11c06b09e373d8d /kernel/power/Kconfig | |
| parent | 8400146d0dc03590bba051399e4bb7e1cbf1c010 (diff) | |
| download | kernel_samsung_smdk4412-5e928f77a09a07f9dd595bb8a489965d69a83458.tar.gz kernel_samsung_smdk4412-5e928f77a09a07f9dd595bb8a489965d69a83458.tar.bz2 kernel_samsung_smdk4412-5e928f77a09a07f9dd595bb8a489965d69a83458.zip | |
PM: Introduce core framework for run-time PM of I/O devices (rev. 17)
Introduce a core framework for run-time power management of I/O
devices. Add device run-time PM fields to 'struct dev_pm_info'
and device run-time PM callbacks to 'struct dev_pm_ops'. Introduce
a run-time PM workqueue and define some device run-time PM helper
functions at the core level. Document all these things.
Special thanks to Alan Stern for his help with the design and
multiple detailed reviews of the pereceding versions of this patch
and to Magnus Damm for testing feedback.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Acked-by: Magnus Damm <damm@igel.co.jp>
Diffstat (limited to 'kernel/power/Kconfig')
| -rw-r--r-- | kernel/power/Kconfig | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/kernel/power/Kconfig b/kernel/power/Kconfig index 72067cbdb37..91e09d3b2eb 100644 --- a/kernel/power/Kconfig +++ b/kernel/power/Kconfig @@ -208,3 +208,17 @@ config APM_EMULATION random kernel OOPSes or reboots that don't seem to be related to anything, try disabling/enabling this option (or disabling/enabling APM in your BIOS). + +config PM_RUNTIME + bool "Run-time PM core functionality" + depends on PM + ---help--- + Enable functionality allowing I/O devices to be put into energy-saving + (low power) states at run time (or autosuspended) after a specified + period of inactivity and woken up in response to a hardware-generated + wake-up event or a driver's request. + + Hardware support is generally required for this functionality to work + and the bus type drivers of the buses the devices are on are + responsible for the actual handling of the autosuspend requests and + wake-up events. |