1config SUSPEND 2 bool "Suspend to RAM and standby" 3 depends on ARCH_SUSPEND_POSSIBLE 4 default y 5 ---help--- 6 Allow the system to enter sleep states in which main memory is 7 powered and thus its contents are preserved, such as the 8 suspend-to-RAM state (e.g. the ACPI S3 state). 9 10config SUSPEND_FREEZER 11 bool "Enable freezer for suspend to RAM/standby" \ 12 if ARCH_WANTS_FREEZER_CONTROL || BROKEN 13 depends on SUSPEND 14 default y 15 help 16 This allows you to turn off the freezer for suspend. If this is 17 done, no tasks are frozen for suspend to RAM/standby. 18 19 Turning OFF this setting is NOT recommended! If in doubt, say Y. 20 21config WAKELOCK 22 bool "Android's method of preventing suspend" 23 default y 24 ---help--- 25 This allows applications to prevent the CPU from suspending while 26 they need it. 27 28 Say Y if you are running an android userspace. 29 30config HIBERNATE_CALLBACKS 31 bool 32 33config HIBERNATION 34 bool "Hibernation (aka 'suspend to disk')" 35 depends on SWAP && ARCH_HIBERNATION_POSSIBLE 36 select HIBERNATE_CALLBACKS 37 select LZO_COMPRESS 38 select LZO_DECOMPRESS 39 select CRC32 40 ---help--- 41 Enable the suspend to disk (STD) functionality, which is usually 42 called "hibernation" in user interfaces. STD checkpoints the 43 system and powers it off; and restores that checkpoint on reboot. 44 45 You can suspend your machine with 'echo disk > /sys/power/state' 46 after placing resume=/dev/swappartition on the kernel command line 47 in your bootloader's configuration file. 48 49 Alternatively, you can use the additional userland tools available 50 from <http://suspend.sf.net>. 51 52 In principle it does not require ACPI or APM, although for example 53 ACPI will be used for the final steps when it is available. One 54 of the reasons to use software suspend is that the firmware hooks 55 for suspend states like suspend-to-RAM (STR) often don't work very 56 well with Linux. 57 58 It creates an image which is saved in your active swap. Upon the next 59 boot, pass the 'resume=/dev/swappartition' argument to the kernel to 60 have it detect the saved image, restore memory state from it, and 61 continue to run as before. If you do not want the previous state to 62 be reloaded, then use the 'noresume' kernel command line argument. 63 Note, however, that fsck will be run on your filesystems and you will 64 need to run mkswap against the swap partition used for the suspend. 65 66 It also works with swap files to a limited extent (for details see 67 <file:Documentation/power/swsusp-and-swap-files.txt>). 68 69 Right now you may boot without resuming and resume later but in the 70 meantime you cannot use the swap partition(s)/file(s) involved in 71 suspending. Also in this case you must not use the filesystems 72 that were mounted before the suspend. In particular, you MUST NOT 73 MOUNT any journaled filesystems mounted before the suspend or they 74 will get corrupted in a nasty way. 75 76 For more information take a look at <file:Documentation/power/swsusp.txt>. 77 78config ARCH_SAVE_PAGE_KEYS 79 bool 80 81config PM_STD_PARTITION 82 string "Default resume partition" 83 depends on HIBERNATION 84 default "" 85 ---help--- 86 The default resume partition is the partition that the suspend- 87 to-disk implementation will look for a suspended disk image. 88 89 The partition specified here will be different for almost every user. 90 It should be a valid swap partition (at least for now) that is turned 91 on before suspending. 92 93 The partition specified can be overridden by specifying: 94 95 resume=/dev/<other device> 96 97 which will set the resume partition to the device specified. 98 99 Note there is currently not a way to specify which device to save the 100 suspended image to. It will simply pick the first available swap 101 device. 102 103config PM_SLEEP 104 def_bool y 105 depends on SUSPEND || HIBERNATE_CALLBACKS 106 107config PM_SLEEP_SMP 108 def_bool y 109 depends on SMP 110 depends on ARCH_SUSPEND_POSSIBLE || ARCH_HIBERNATION_POSSIBLE 111 depends on PM_SLEEP 112 select HOTPLUG_CPU 113 114config PM_AUTOSLEEP 115 bool "Opportunistic sleep" 116 depends on PM_SLEEP 117 default n 118 ---help--- 119 Allow the kernel to trigger a system transition into a global sleep 120 state automatically whenever there are no active wakeup sources. 121 122config PM_WAKELOCKS 123 bool "User space wakeup sources interface" 124 depends on PM_SLEEP 125 default n 126 ---help--- 127 Allow user space to create, activate and deactivate wakeup source 128 objects with the help of a sysfs-based interface. 129 130config PM_WAKELOCKS_LIMIT 131 int "Maximum number of user space wakeup sources (0 = no limit)" 132 range 0 100000 133 default 100 134 depends on PM_WAKELOCKS 135 136config PM_WAKELOCKS_GC 137 bool "Garbage collector for user space wakeup sources" 138 depends on PM_WAKELOCKS 139 default y 140 141config PM_RUNTIME 142 bool "Run-time PM core functionality" 143 depends on !IA64_HP_SIM 144 ---help--- 145 Enable functionality allowing I/O devices to be put into energy-saving 146 (low power) states at run time (or autosuspended) after a specified 147 period of inactivity and woken up in response to a hardware-generated 148 wake-up event or a driver's request. 149 150 Hardware support is generally required for this functionality to work 151 and the bus type drivers of the buses the devices are on are 152 responsible for the actual handling of the autosuspend requests and 153 wake-up events. 154 155config PM 156 def_bool y 157 depends on PM_SLEEP || PM_RUNTIME 158 159config PM_DEBUG 160 bool "Power Management Debug Support" 161 depends on PM 162 ---help--- 163 This option enables various debugging support in the Power Management 164 code. This is helpful when debugging and reporting PM bugs, like 165 suspend support. 166 167config PM_ADVANCED_DEBUG 168 bool "Extra PM attributes in sysfs for low-level debugging/testing" 169 depends on PM_DEBUG 170 ---help--- 171 Add extra sysfs attributes allowing one to access some Power Management 172 fields of device objects from user space. If you are not a kernel 173 developer interested in debugging/testing Power Management, say "no". 174 175config PM_TEST_SUSPEND 176 bool "Test suspend/resume and wakealarm during bootup" 177 depends on SUSPEND && PM_DEBUG && RTC_CLASS=y 178 ---help--- 179 This option will let you suspend your machine during bootup, and 180 make it wake up a few seconds later using an RTC wakeup alarm. 181 Enable this with a kernel parameter like "test_suspend=mem". 182 183 You probably want to have your system's RTC driver statically 184 linked, ensuring that it's available when this test runs. 185 186config PM_SLEEP_DEBUG 187 def_bool y 188 depends on PM_DEBUG && PM_SLEEP 189 190config DPM_WATCHDOG 191 bool "Device suspend/resume watchdog" 192 depends on PM_DEBUG && PSTORE 193 ---help--- 194 Sets up a watchdog timer to capture drivers that are 195 locked up attempting to suspend/resume a device. 196 A detected lockup causes system panic with message 197 captured in pstore device for inspection in subsequent 198 boot session. 199 200config DPM_WATCHDOG_TIMEOUT 201 int "Watchdog timeout in seconds" 202 range 1 120 203 default 60 204 depends on DPM_WATCHDOG 205 206config PM_TRACE 207 bool 208 help 209 This enables code to save the last PM event point across 210 reboot. The architecture needs to support this, x86 for 211 example does by saving things in the RTC, see below. 212 213 The architecture specific code must provide the extern 214 functions from <linux/resume-trace.h> as well as the 215 <asm/resume-trace.h> header with a TRACE_RESUME() macro. 216 217 The way the information is presented is architecture- 218 dependent, x86 will print the information during a 219 late_initcall. 220 221config PM_TRACE_RTC 222 bool "Suspend/resume event tracing" 223 depends on PM_SLEEP_DEBUG 224 depends on X86 225 select PM_TRACE 226 ---help--- 227 This enables some cheesy code to save the last PM event point in the 228 RTC across reboots, so that you can debug a machine that just hangs 229 during suspend (or more commonly, during resume). 230 231 To use this debugging feature you should attempt to suspend the 232 machine, reboot it and then run 233 234 dmesg -s 1000000 | grep 'hash matches' 235 236 CAUTION: this option will cause your machine's real-time clock to be 237 set to an invalid time after a resume. 238 239config APM_EMULATION 240 tristate "Advanced Power Management Emulation" 241 depends on PM && SYS_SUPPORTS_APM_EMULATION 242 help 243 APM is a BIOS specification for saving power using several different 244 techniques. This is mostly useful for battery powered laptops with 245 APM compliant BIOSes. If you say Y here, the system time will be 246 reset after a RESUME operation, the /proc/apm device will provide 247 battery status information, and user-space programs will receive 248 notification of APM "events" (e.g. battery status change). 249 250 In order to use APM, you will need supporting software. For location 251 and more information, read <file:Documentation/power/apm-acpi.txt> 252 and the Battery Powered Linux mini-HOWTO, available from 253 <http://www.tldp.org/docs.html#howto>. 254 255 This driver does not spin down disk drives (see the hdparm(8) 256 manpage ("man 8 hdparm") for that), and it doesn't turn off 257 VESA-compliant "green" monitors. 258 259 Generally, if you don't have a battery in your machine, there isn't 260 much point in using this driver and you should say N. If you get 261 random kernel OOPSes or reboots that don't seem to be related to 262 anything, try disabling/enabling this option (or disabling/enabling 263 APM in your BIOS). 264 265config PM_OPP 266 bool 267 ---help--- 268 SOCs have a standard set of tuples consisting of frequency and 269 voltage pairs that the device will support per voltage domain. This 270 is called Operating Performance Point or OPP. The actual definitions 271 of OPP varies over silicon within the same family of devices. 272 273 OPP layer organizes the data internally using device pointers 274 representing individual voltage domains and provides SOC 275 implementations a ready to use framework to manage OPPs. 276 For more information, read <file:Documentation/power/opp.txt> 277 278config PM_CLK 279 def_bool y 280 depends on PM && HAVE_CLK 281 282config PM_GENERIC_DOMAINS 283 bool 284 depends on PM 285 286config WQ_POWER_EFFICIENT_DEFAULT 287 bool "Enable workqueue power-efficient mode by default" 288 depends on PM 289 default n 290 help 291 Per-cpu workqueues are generally preferred because they show 292 better performance thanks to cache locality; unfortunately, 293 per-cpu workqueues tend to be more power hungry than unbound 294 workqueues. 295 296 Enabling workqueue.power_efficient kernel parameter makes the 297 per-cpu workqueues which were observed to contribute 298 significantly to power consumption unbound, leading to measurably 299 lower power usage at the cost of small performance overhead. 300 301 This config option determines whether workqueue.power_efficient 302 is enabled by default. 303 304 If in doubt, say N. 305 306config PM_GENERIC_DOMAINS_SLEEP 307 def_bool y 308 depends on PM_SLEEP && PM_GENERIC_DOMAINS 309 310config PM_GENERIC_DOMAINS_RUNTIME 311 def_bool y 312 depends on PM_RUNTIME && PM_GENERIC_DOMAINS 313 314config PM_GENERIC_DOMAINS_OF 315 def_bool y 316 depends on PM_GENERIC_DOMAINS && OF 317 318config CPU_PM 319 bool 320 depends on SUSPEND || CPU_IDLE 321 322config SUSPEND_TIME 323 bool "Log time spent in suspend" 324 ---help--- 325 Prints the time spent in suspend in the kernel log, and 326 keeps statistics on the time spent in suspend in 327 /sys/kernel/debug/suspend_time 328