Kconfig 7.7 KB

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