Kconfig 7.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205
  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. Power Management is most important for battery powered laptop
  11. computers; if you have a laptop, check out the Linux Laptop home
  12. page on the WWW at <http://www.linux-on-laptops.com/> or
  13. Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>
  14. and the Battery Powered Linux mini-HOWTO, available from
  15. <http://www.tldp.org/docs.html#howto>.
  16. Note that, even if you say N here, Linux on the x86 architecture
  17. will issue the hlt instruction if nothing is to be done, thereby
  18. sending the processor to sleep and saving power.
  19. config PM_LEGACY
  20. bool "Legacy Power Management API (DEPRECATED)"
  21. depends on PM
  22. default n
  23. ---help---
  24. Support for pm_register() and friends. This old API is obsoleted
  25. by the driver model.
  26. If unsure, say N.
  27. config PM_DEBUG
  28. bool "Power Management Debug Support"
  29. depends on PM
  30. ---help---
  31. This option enables various debugging support in the Power Management
  32. code. This is helpful when debugging and reporting PM bugs, like
  33. suspend support.
  34. config PM_VERBOSE
  35. bool "Verbose Power Management debugging"
  36. depends on PM_DEBUG
  37. default n
  38. ---help---
  39. This option enables verbose messages from the Power Management code.
  40. config CAN_PM_TRACE
  41. def_bool y
  42. depends on PM_DEBUG && PM_SLEEP && EXPERIMENTAL
  43. config PM_TRACE
  44. bool
  45. help
  46. This enables code to save the last PM event point across
  47. reboot. The architecture needs to support this, x86 for
  48. example does by saving things in the RTC, see below.
  49. The architecture specific code must provide the extern
  50. functions from <linux/resume-trace.h> as well as the
  51. <asm/resume-trace.h> header with a TRACE_RESUME() macro.
  52. The way the information is presented is architecture-
  53. dependent, x86 will print the information during a
  54. late_initcall.
  55. config PM_TRACE_RTC
  56. bool "Suspend/resume event tracing"
  57. depends on CAN_PM_TRACE
  58. depends on X86
  59. select PM_TRACE
  60. default n
  61. ---help---
  62. This enables some cheesy code to save the last PM event point in the
  63. RTC across reboots, so that you can debug a machine that just hangs
  64. during suspend (or more commonly, during resume).
  65. To use this debugging feature you should attempt to suspend the
  66. machine, reboot it and then run
  67. dmesg -s 1000000 | grep 'hash matches'
  68. CAUTION: this option will cause your machine's real-time clock to be
  69. set to an invalid time after a resume.
  70. config PM_SLEEP_SMP
  71. bool
  72. depends on SMP
  73. depends on ARCH_SUSPEND_POSSIBLE || ARCH_HIBERNATION_POSSIBLE
  74. depends on PM_SLEEP
  75. select HOTPLUG_CPU
  76. default y
  77. config PM_SLEEP
  78. bool
  79. depends on SUSPEND || HIBERNATION
  80. default y
  81. config SUSPEND
  82. bool "Suspend to RAM and standby"
  83. depends on PM && ARCH_SUSPEND_POSSIBLE
  84. default y
  85. ---help---
  86. Allow the system to enter sleep states in which main memory is
  87. powered and thus its contents are preserved, such as the
  88. suspend-to-RAM state (e.g. the ACPI S3 state).
  89. config SUSPEND_FREEZER
  90. bool "Enable freezer for suspend to RAM/standby" \
  91. if ARCH_WANTS_FREEZER_CONTROL || BROKEN
  92. depends on SUSPEND
  93. default y
  94. help
  95. This allows you to turn off the freezer for suspend. If this is
  96. done, no tasks are frozen for suspend to RAM/standby.
  97. Turning OFF this setting is NOT recommended! If in doubt, say Y.
  98. config HIBERNATION
  99. bool "Hibernation (aka 'suspend to disk')"
  100. depends on PM && SWAP && ARCH_HIBERNATION_POSSIBLE
  101. ---help---
  102. Enable the suspend to disk (STD) functionality, which is usually
  103. called "hibernation" in user interfaces. STD checkpoints the
  104. system and powers it off; and restores that checkpoint on reboot.
  105. You can suspend your machine with 'echo disk > /sys/power/state'
  106. after placing resume=/dev/swappartition on the kernel command line
  107. in your bootloader's configuration file.
  108. Alternatively, you can use the additional userland tools available
  109. from <http://suspend.sf.net>.
  110. In principle it does not require ACPI or APM, although for example
  111. ACPI will be used for the final steps when it is available. One
  112. of the reasons to use software suspend is that the firmware hooks
  113. for suspend states like suspend-to-RAM (STR) often don't work very
  114. well with Linux.
  115. It creates an image which is saved in your active swap. Upon the next
  116. boot, pass the 'resume=/dev/swappartition' argument to the kernel to
  117. have it detect the saved image, restore memory state from it, and
  118. continue to run as before. If you do not want the previous state to
  119. be reloaded, then use the 'noresume' kernel command line argument.
  120. Note, however, that fsck will be run on your filesystems and you will
  121. need to run mkswap against the swap partition used for the suspend.
  122. It also works with swap files to a limited extent (for details see
  123. <file:Documentation/power/swsusp-and-swap-files.txt>).
  124. Right now you may boot without resuming and resume later but in the
  125. meantime you cannot use the swap partition(s)/file(s) involved in
  126. suspending. Also in this case you must not use the filesystems
  127. that were mounted before the suspend. In particular, you MUST NOT
  128. MOUNT any journaled filesystems mounted before the suspend or they
  129. will get corrupted in a nasty way.
  130. For more information take a look at <file:Documentation/power/swsusp.txt>.
  131. config PM_STD_PARTITION
  132. string "Default resume partition"
  133. depends on HIBERNATION
  134. default ""
  135. ---help---
  136. The default resume partition is the partition that the suspend-
  137. to-disk implementation will look for a suspended disk image.
  138. The partition specified here will be different for almost every user.
  139. It should be a valid swap partition (at least for now) that is turned
  140. on before suspending.
  141. The partition specified can be overridden by specifying:
  142. resume=/dev/<other device>
  143. which will set the resume partition to the device specified.
  144. Note there is currently not a way to specify which device to save the
  145. suspended image to. It will simply pick the first available swap
  146. device.
  147. config APM_EMULATION
  148. tristate "Advanced Power Management Emulation"
  149. depends on PM && SYS_SUPPORTS_APM_EMULATION
  150. help
  151. APM is a BIOS specification for saving power using several different
  152. techniques. This is mostly useful for battery powered laptops with
  153. APM compliant BIOSes. If you say Y here, the system time will be
  154. reset after a RESUME operation, the /proc/apm device will provide
  155. battery status information, and user-space programs will receive
  156. notification of APM "events" (e.g. battery status change).
  157. In order to use APM, you will need supporting software. For location
  158. and more information, read <file:Documentation/power/pm.txt> and the
  159. Battery Powered Linux mini-HOWTO, available from
  160. <http://www.tldp.org/docs.html#howto>.
  161. This driver does not spin down disk drives (see the hdparm(8)
  162. manpage ("man 8 hdparm") for that), and it doesn't turn off
  163. VESA-compliant "green" monitors.
  164. Generally, if you don't have a battery in your machine, there isn't
  165. much point in using this driver and you should say N. If you get
  166. random kernel OOPSes or reboots that don't seem to be related to
  167. anything, try disabling/enabling this option (or disabling/enabling
  168. APM in your BIOS).