Linux/kernel/power/Kconfig

Version: ~ [ linux-6.12-rc7 ] ~ [ linux-6.11.7 ] ~ [ linux-6.10.14 ] ~ [ linux-6.9.12 ] ~ [ linux-6.8.12 ] ~ [ linux-6.7.12 ] ~ [ linux-6.6.60 ] ~ [ linux-6.5.13 ] ~ [ linux-6.4.16 ] ~ [ linux-6.3.13 ] ~ [ linux-6.2.16 ] ~ [ linux-6.1.116 ] ~ [ linux-6.0.19 ] ~ [ linux-5.19.17 ] ~ [ linux-5.18.19 ] ~ [ linux-5.17.15 ] ~ [ linux-5.16.20 ] ~ [ linux-5.15.171 ] ~ [ linux-5.14.21 ] ~ [ linux-5.13.19 ] ~ [ linux-5.12.19 ] ~ [ linux-5.11.22 ] ~ [ linux-5.10.229 ] ~ [ linux-5.9.16 ] ~ [ linux-5.8.18 ] ~ [ linux-5.7.19 ] ~ [ linux-5.6.19 ] ~ [ linux-5.5.19 ] ~ [ linux-5.4.285 ] ~ [ linux-5.3.18 ] ~ [ linux-5.2.21 ] ~ [ linux-5.1.21 ] ~ [ linux-5.0.21 ] ~ [ linux-4.20.17 ] ~ [ linux-4.19.323 ] ~ [ linux-4.18.20 ] ~ [ linux-4.17.19 ] ~ [ linux-4.16.18 ] ~ [ linux-4.15.18 ] ~ [ linux-4.14.336 ] ~ [ linux-4.13.16 ] ~ [ linux-4.12.14 ] ~ [ linux-4.11.12 ] ~ [ linux-4.10.17 ] ~ [ linux-4.9.337 ] ~ [ linux-4.4.302 ] ~ [ linux-3.10.108 ] ~ [ linux-2.6.32.71 ] ~ [ linux-2.6.0 ] ~ [ linux-2.4.37.11 ] ~ [ unix-v6-master ] ~ [ ccs-tools-1.8.12 ] ~ [ policy-sample ] ~
Architecture: ~ [ i386 ] ~ [ alpha ] ~ [ m68k ] ~ [ mips ] ~ [ ppc ] ~ [ sparc ] ~ [ sparc64 ] ~

Diff markup

1 # SPDX-License-Identifier: GPL-2.0-only !! 1 config PM >> 2 bool "Power Management support" >> 3 depends on !IA64_HP_SIM >> 4 ---help--- >> 5 "Power Management" means that parts of your computer are shut >> 6 off or put into a power conserving "sleep" mode if they are not >> 7 being used. There are two competing standards for doing this: APM >> 8 and ACPI. If you want to use either one, say Y here and then also >> 9 to the requisite support below. >> 10 >> 11 Power Management is most important for battery powered laptop >> 12 computers; if you have a laptop, check out the Linux Laptop home >> 13 page on the WWW at <http://www.linux-on-laptops.com/> or >> 14 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/> >> 15 and the Battery Powered Linux mini-HOWTO, available from >> 16 <http://www.tldp.org/docs.html#howto>. >> 17 >> 18 Note that, even if you say N here, Linux on the x86 architecture >> 19 will issue the hlt instruction if nothing is to be done, thereby >> 20 sending the processor to sleep and saving power. >> 21 >> 22 config PM_DEBUG >> 23 bool "Power Management Debug Support" >> 24 depends on PM >> 25 ---help--- >> 26 This option enables various debugging support in the Power Management >> 27 code. This is helpful when debugging and reporting PM bugs, like >> 28 suspend support. >> 29 >> 30 config PM_VERBOSE >> 31 bool "Verbose Power Management debugging" >> 32 depends on PM_DEBUG >> 33 default n >> 34 ---help--- >> 35 This option enables verbose messages from the Power Management code. >> 36 >> 37 config CAN_PM_TRACE >> 38 def_bool y >> 39 depends on PM_DEBUG && PM_SLEEP && EXPERIMENTAL >> 40 >> 41 config PM_TRACE >> 42 bool >> 43 help >> 44 This enables code to save the last PM event point across >> 45 reboot. The architecture needs to support this, x86 for >> 46 example does by saving things in the RTC, see below. >> 47 >> 48 The architecture specific code must provide the extern >> 49 functions from <linux/resume-trace.h> as well as the >> 50 <asm/resume-trace.h> header with a TRACE_RESUME() macro. >> 51 >> 52 The way the information is presented is architecture- >> 53 dependent, x86 will print the information during a >> 54 late_initcall. >> 55 >> 56 config PM_TRACE_RTC >> 57 bool "Suspend/resume event tracing" >> 58 depends on CAN_PM_TRACE >> 59 depends on X86 >> 60 select PM_TRACE >> 61 default n >> 62 ---help--- >> 63 This enables some cheesy code to save the last PM event point in the >> 64 RTC across reboots, so that you can debug a machine that just hangs >> 65 during suspend (or more commonly, during resume). >> 66 >> 67 To use this debugging feature you should attempt to suspend the >> 68 machine, reboot it and then run >> 69 >> 70 dmesg -s 1000000 | grep 'hash matches' >> 71 >> 72 CAUTION: this option will cause your machine's real-time clock to be >> 73 set to an invalid time after a resume. >> 74 >> 75 config PM_SLEEP_SMP >> 76 bool >> 77 depends on SMP >> 78 depends on ARCH_SUSPEND_POSSIBLE || ARCH_HIBERNATION_POSSIBLE >> 79 depends on PM_SLEEP >> 80 select HOTPLUG_CPU >> 81 default y >> 82 >> 83 config PM_SLEEP >> 84 bool >> 85 depends on SUSPEND || HIBERNATION || XEN_SAVE_RESTORE >> 86 default y >> 87 2 config SUSPEND 88 config SUSPEND 3 bool "Suspend to RAM and standby" 89 bool "Suspend to RAM and standby" 4 depends on ARCH_SUSPEND_POSSIBLE !! 90 depends on PM && ARCH_SUSPEND_POSSIBLE 5 default y 91 default y 6 help !! 92 ---help--- 7 Allow the system to enter sleep stat 93 Allow the system to enter sleep states in which main memory is 8 powered and thus its contents are pr 94 powered and thus its contents are preserved, such as the 9 suspend-to-RAM state (e.g. the ACPI 95 suspend-to-RAM state (e.g. the ACPI S3 state). 10 96 >> 97 config PM_TEST_SUSPEND >> 98 bool "Test suspend/resume and wakealarm during bootup" >> 99 depends on SUSPEND && PM_DEBUG && RTC_CLASS=y >> 100 ---help--- >> 101 This option will let you suspend your machine during bootup, and >> 102 make it wake up a few seconds later using an RTC wakeup alarm. >> 103 Enable this with a kernel parameter like "test_suspend=mem". >> 104 >> 105 You probably want to have your system's RTC driver statically >> 106 linked, ensuring that it's available when this test runs. >> 107 11 config SUSPEND_FREEZER 108 config SUSPEND_FREEZER 12 bool "Enable freezer for suspend to RA 109 bool "Enable freezer for suspend to RAM/standby" \ 13 if ARCH_WANTS_FREEZER_CONTROL 110 if ARCH_WANTS_FREEZER_CONTROL || BROKEN 14 depends on SUSPEND 111 depends on SUSPEND 15 default y 112 default y 16 help 113 help 17 This allows you to turn off the free 114 This allows you to turn off the freezer for suspend. If this is 18 done, no tasks are frozen for suspen 115 done, no tasks are frozen for suspend to RAM/standby. 19 116 20 Turning OFF this setting is NOT reco 117 Turning OFF this setting is NOT recommended! If in doubt, say Y. 21 118 22 config SUSPEND_SKIP_SYNC !! 119 config HIBERNATION_NVS 23 bool "Skip kernel's sys_sync() on susp << 24 depends on SUSPEND << 25 depends on EXPERT << 26 help << 27 Skip the kernel sys_sync() before fr << 28 Some systems prefer not to pay this << 29 of suspend, or they are content with << 30 user-space before invoking suspend. << 31 at '/sys/power/sync_on_suspend' to c << 32 This setting changes the default for << 33 to change the default to disable the << 34 << 35 config HIBERNATE_CALLBACKS << 36 bool 120 bool 37 121 38 config HIBERNATION 122 config HIBERNATION 39 bool "Hibernation (aka 'suspend to dis 123 bool "Hibernation (aka 'suspend to disk')" 40 depends on SWAP && ARCH_HIBERNATION_PO !! 124 depends on PM && SWAP && ARCH_HIBERNATION_POSSIBLE 41 select HIBERNATE_CALLBACKS !! 125 select HIBERNATION_NVS if HAS_IOMEM 42 select CRC32 !! 126 ---help--- 43 select CRYPTO << 44 select CRYPTO_LZO << 45 help << 46 Enable the suspend to disk (STD) fun 127 Enable the suspend to disk (STD) functionality, which is usually 47 called "hibernation" in user interfa 128 called "hibernation" in user interfaces. STD checkpoints the 48 system and powers it off; and restor 129 system and powers it off; and restores that checkpoint on reboot. 49 130 50 You can suspend your machine with 'e 131 You can suspend your machine with 'echo disk > /sys/power/state' 51 after placing resume=/dev/swappartit 132 after placing resume=/dev/swappartition on the kernel command line 52 in your bootloader's configuration f 133 in your bootloader's configuration file. 53 134 54 Alternatively, you can use the addit 135 Alternatively, you can use the additional userland tools available 55 from <http://suspend.sf.net>. 136 from <http://suspend.sf.net>. 56 137 57 In principle it does not require ACP 138 In principle it does not require ACPI or APM, although for example 58 ACPI will be used for the final step 139 ACPI will be used for the final steps when it is available. One 59 of the reasons to use software suspe 140 of the reasons to use software suspend is that the firmware hooks 60 for suspend states like suspend-to-R 141 for suspend states like suspend-to-RAM (STR) often don't work very 61 well with Linux. 142 well with Linux. 62 143 63 It creates an image which is saved i 144 It creates an image which is saved in your active swap. Upon the next 64 boot, pass the 'resume=/dev/swappart 145 boot, pass the 'resume=/dev/swappartition' argument to the kernel to 65 have it detect the saved image, rest 146 have it detect the saved image, restore memory state from it, and 66 continue to run as before. If you do 147 continue to run as before. If you do not want the previous state to 67 be reloaded, then use the 'noresume' 148 be reloaded, then use the 'noresume' kernel command line argument. 68 Note, however, that fsck will be run 149 Note, however, that fsck will be run on your filesystems and you will 69 need to run mkswap against the swap 150 need to run mkswap against the swap partition used for the suspend. 70 151 71 It also works with swap files to a l 152 It also works with swap files to a limited extent (for details see 72 <file:Documentation/power/swsusp-and !! 153 <file:Documentation/power/swsusp-and-swap-files.txt>). 73 154 74 Right now you may boot without resum 155 Right now you may boot without resuming and resume later but in the 75 meantime you cannot use the swap par 156 meantime you cannot use the swap partition(s)/file(s) involved in 76 suspending. Also in this case you m 157 suspending. Also in this case you must not use the filesystems 77 that were mounted before the suspend 158 that were mounted before the suspend. In particular, you MUST NOT 78 MOUNT any journaled filesystems moun 159 MOUNT any journaled filesystems mounted before the suspend or they 79 will get corrupted in a nasty way. 160 will get corrupted in a nasty way. 80 161 81 For more information take a look at !! 162 For more information take a look at <file:Documentation/power/swsusp.txt>. 82 << 83 config HIBERNATION_SNAPSHOT_DEV << 84 bool "Userspace snapshot device" << 85 depends on HIBERNATION << 86 default y << 87 help << 88 Device used by the uswsusp tools. << 89 << 90 Say N if no snapshotting from usersp << 91 reduces the attack surface of the ke << 92 << 93 If in doubt, say Y. << 94 << 95 choice << 96 prompt "Default compressor" << 97 default HIBERNATION_COMP_LZO << 98 depends on HIBERNATION << 99 << 100 config HIBERNATION_COMP_LZO << 101 bool "lzo" << 102 depends on CRYPTO_LZO << 103 << 104 config HIBERNATION_COMP_LZ4 << 105 bool "lz4" << 106 depends on CRYPTO_LZ4 << 107 << 108 endchoice << 109 << 110 config HIBERNATION_DEF_COMP << 111 string << 112 default "lzo" if HIBERNATION_COMP_LZO << 113 default "lz4" if HIBERNATION_COMP_LZ4 << 114 help << 115 Default compressor to be used for hi << 116 163 117 config PM_STD_PARTITION 164 config PM_STD_PARTITION 118 string "Default resume partition" 165 string "Default resume partition" 119 depends on HIBERNATION 166 depends on HIBERNATION 120 default "" 167 default "" 121 help !! 168 ---help--- 122 The default resume partition is the 169 The default resume partition is the partition that the suspend- 123 to-disk implementation will look for !! 170 to-disk implementation will look for a suspended disk image. 124 171 125 The partition specified here will be !! 172 The partition specified here will be different for almost every user. 126 It should be a valid swap partition 173 It should be a valid swap partition (at least for now) that is turned 127 on before suspending. !! 174 on before suspending. 128 175 129 The partition specified can be overr 176 The partition specified can be overridden by specifying: 130 177 131 resume=/dev/<other device> !! 178 resume=/dev/<other device> 132 179 133 which will set the resume partition !! 180 which will set the resume partition to the device specified. 134 181 135 Note there is currently not a way to 182 Note there is currently not a way to specify which device to save the 136 suspended image to. It will simply p !! 183 suspended image to. It will simply pick the first available swap 137 device. 184 device. 138 185 139 config PM_SLEEP << 140 def_bool y << 141 depends on SUSPEND || HIBERNATE_CALLBA << 142 select PM << 143 << 144 config PM_SLEEP_SMP << 145 def_bool y << 146 depends on SMP << 147 depends on ARCH_SUSPEND_POSSIBLE || AR << 148 depends on PM_SLEEP << 149 select HOTPLUG_CPU << 150 << 151 config PM_SLEEP_SMP_NONZERO_CPU << 152 def_bool y << 153 depends on PM_SLEEP_SMP << 154 depends on ARCH_SUSPEND_NONZERO_CPU << 155 help << 156 If an arch can suspend (for suspend, h << 157 non-zero numbered CPU, it may define A << 158 will allow nohz_full mask to include C << 159 << 160 config PM_AUTOSLEEP << 161 bool "Opportunistic sleep" << 162 depends on PM_SLEEP << 163 help << 164 Allow the kernel to trigger a system t << 165 state automatically whenever there are << 166 << 167 config PM_USERSPACE_AUTOSLEEP << 168 bool "Userspace opportunistic sleep" << 169 depends on PM_SLEEP << 170 help << 171 Notify kernel of aggressive userspace << 172 << 173 This option changes the behavior of va << 174 with frequent userspace-initiated tran << 175 << 176 Saying Y here, disables code paths tha << 177 enabled. In particular, only enable th << 178 asleep/awake for very short periods of << 179 << 180 Only platforms, such as Android, that << 181 a userspace power manager service shou << 182 other machines. Therefore, you should << 183 extremely certain that this is what yo << 184 bad, undesirable effects, and should n << 185 << 186 << 187 config PM_WAKELOCKS << 188 bool "User space wakeup sources interf << 189 depends on PM_SLEEP << 190 help << 191 Allow user space to create, activate a << 192 objects with the help of a sysfs-based << 193 << 194 config PM_WAKELOCKS_LIMIT << 195 int "Maximum number of user space wake << 196 range 0 100000 << 197 default 100 << 198 depends on PM_WAKELOCKS << 199 << 200 config PM_WAKELOCKS_GC << 201 bool "Garbage collector for user space << 202 depends on PM_WAKELOCKS << 203 default y << 204 << 205 config PM << 206 bool "Device power management core fun << 207 help << 208 Enable functionality allowing I/O de << 209 (low power) states, for example afte << 210 (autosuspended), and woken up in res << 211 wake-up event or a driver's request. << 212 << 213 Hardware support is generally requir << 214 and the bus type drivers of the buse << 215 responsible for the actual handling << 216 wake-up events. << 217 << 218 config PM_DEBUG << 219 bool "Power Management Debug Support" << 220 depends on PM << 221 help << 222 This option enables various debugging << 223 code. This is helpful when debugging a << 224 suspend support. << 225 << 226 config PM_ADVANCED_DEBUG << 227 bool "Extra PM attributes in sysfs for << 228 depends on PM_DEBUG << 229 help << 230 Add extra sysfs attributes allowing on << 231 fields of device objects from user spa << 232 developer interested in debugging/test << 233 << 234 config PM_TEST_SUSPEND << 235 bool "Test suspend/resume and wakealar << 236 depends on SUSPEND && PM_DEBUG && RTC_ << 237 help << 238 This option will let you suspend your << 239 make it wake up a few seconds later us << 240 Enable this with a kernel parameter li << 241 << 242 You probably want to have your system' << 243 linked, ensuring that it's available w << 244 << 245 config PM_SLEEP_DEBUG << 246 def_bool y << 247 depends on PM_DEBUG && PM_SLEEP << 248 << 249 config DPM_WATCHDOG << 250 bool "Device suspend/resume watchdog" << 251 depends on PM_DEBUG && PSTORE && EXPER << 252 help << 253 Sets up a watchdog timer to capture << 254 locked up attempting to suspend/resu << 255 A detected lockup causes system pani << 256 captured in pstore device for inspec << 257 boot session. << 258 << 259 config DPM_WATCHDOG_TIMEOUT << 260 int "Watchdog timeout in seconds" << 261 range 1 120 << 262 default 120 << 263 depends on DPM_WATCHDOG << 264 << 265 config PM_TRACE << 266 bool << 267 help << 268 This enables code to save the last P << 269 reboot. The architecture needs to su << 270 example does by saving things in the << 271 << 272 The architecture specific code must << 273 functions from <linux/resume-trace.h << 274 <asm/resume-trace.h> header with a T << 275 << 276 The way the information is presented << 277 dependent, x86 will print the inform << 278 late_initcall. << 279 << 280 config PM_TRACE_RTC << 281 bool "Suspend/resume event tracing" << 282 depends on PM_SLEEP_DEBUG << 283 depends on X86 << 284 select PM_TRACE << 285 help << 286 This enables some cheesy code to save << 287 RTC across reboots, so that you can de << 288 during suspend (or more commonly, duri << 289 << 290 To use this debugging feature you shou << 291 machine, reboot it and then run << 292 << 293 dmesg -s 1000000 | grep 'hash << 294 << 295 CAUTION: this option will cause your m << 296 set to an invalid time after a resume. << 297 << 298 config APM_EMULATION 186 config APM_EMULATION 299 tristate "Advanced Power Management Em 187 tristate "Advanced Power Management Emulation" 300 depends on SYS_SUPPORTS_APM_EMULATION !! 188 depends on PM && SYS_SUPPORTS_APM_EMULATION 301 help 189 help 302 APM is a BIOS specification for savi 190 APM is a BIOS specification for saving power using several different 303 techniques. This is mostly useful fo 191 techniques. This is mostly useful for battery powered laptops with 304 APM compliant BIOSes. If you say Y h 192 APM compliant BIOSes. If you say Y here, the system time will be 305 reset after a RESUME operation, the 193 reset after a RESUME operation, the /proc/apm device will provide 306 battery status information, and user 194 battery status information, and user-space programs will receive 307 notification of APM "events" (e.g. b 195 notification of APM "events" (e.g. battery status change). 308 196 309 In order to use APM, you will need s 197 In order to use APM, you will need supporting software. For location 310 and more information, read <file:Doc !! 198 and more information, read <file:Documentation/power/pm.txt> and the 311 and the Battery Powered Linux mini-H !! 199 Battery Powered Linux mini-HOWTO, available from 312 <http://www.tldp.org/docs.html#howto 200 <http://www.tldp.org/docs.html#howto>. 313 201 314 This driver does not spin down disk 202 This driver does not spin down disk drives (see the hdparm(8) 315 manpage ("man 8 hdparm") for that), 203 manpage ("man 8 hdparm") for that), and it doesn't turn off 316 VESA-compliant "green" monitors. 204 VESA-compliant "green" monitors. 317 205 318 Generally, if you don't have a batte 206 Generally, if you don't have a battery in your machine, there isn't 319 much point in using this driver and 207 much point in using this driver and you should say N. If you get 320 random kernel OOPSes or reboots that 208 random kernel OOPSes or reboots that don't seem to be related to 321 anything, try disabling/enabling thi 209 anything, try disabling/enabling this option (or disabling/enabling 322 APM in your BIOS). 210 APM in your BIOS). 323 211 324 config PM_CLK !! 212 config PM_RUNTIME 325 def_bool y !! 213 bool "Run-time PM core functionality" 326 depends on PM && HAVE_CLK << 327 << 328 config PM_GENERIC_DOMAINS << 329 bool << 330 depends on PM << 331 << 332 config WQ_POWER_EFFICIENT_DEFAULT << 333 bool "Enable workqueue power-efficient << 334 depends on PM 214 depends on PM 335 help !! 215 ---help--- 336 Per-cpu workqueues are generally pre !! 216 Enable functionality allowing I/O devices to be put into energy-saving 337 better performance thanks to cache l !! 217 (low power) states at run time (or autosuspended) after a specified 338 per-cpu workqueues tend to be more p !! 218 period of inactivity and woken up in response to a hardware-generated 339 workqueues. !! 219 wake-up event or a driver's request. 340 << 341 Enabling workqueue.power_efficient k << 342 per-cpu workqueues which were observ << 343 significantly to power consumption u << 344 lower power usage at the cost of sma << 345 << 346 This config option determines whethe << 347 is enabled by default. << 348 << 349 If in doubt, say N. << 350 << 351 config PM_GENERIC_DOMAINS_SLEEP << 352 def_bool y << 353 depends on PM_SLEEP && PM_GENERIC_DOMA << 354 << 355 config PM_GENERIC_DOMAINS_OF << 356 def_bool y << 357 depends on PM_GENERIC_DOMAINS && OF << 358 << 359 config CPU_PM << 360 bool << 361 << 362 config ENERGY_MODEL << 363 bool "Energy Model for devices with DV << 364 depends on SMP << 365 depends on CPU_FREQ << 366 help << 367 Several subsystems (thermal and/or t << 368 can leverage information about the e << 369 make smarter decisions. This config << 370 from which subsystems can access the << 371 << 372 The exact usage of the energy model << 373 220 374 If in doubt, say N. !! 221 Hardware support is generally required for this functionality to work >> 222 and the bus type drivers of the buses the devices are on are >> 223 responsible for the actual handling of the autosuspend requests and >> 224 wake-up events.

Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.

TOMOYO Linux Cross Reference
Linux/kernel/power/Kconfig

Diff markup

Differences between /kernel/power/Kconfig (Version linux-6.12-rc7) and /kernel/power/Kconfig (Version linux-2.6.32.71)

TOMOYO Linux Cross Reference Linux/kernel/power/Kconfig

Diff markup

Differences between /kernel/power/Kconfig (Version linux-6.12-rc7) and /kernel/power/Kconfig (Version linux-2.6.32.71)

TOMOYO Linux Cross Reference
Linux/kernel/power/Kconfig