Kconfig 9.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265
  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_ADVANCED_DEBUG
  27. bool "Extra PM attributes in sysfs for low-level debugging/testing"
  28. depends on PM_DEBUG
  29. default n
  30. ---help---
  31. Add extra sysfs attributes allowing one to access some Power Management
  32. fields of device objects from user space. If you are not a kernel
  33. developer interested in debugging/testing Power Management, say "no".
  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
  76. select HOTPLUG_CPU
  77. default y
  78. config PM_SLEEP
  79. bool
  80. depends on SUSPEND || HIBERNATION || XEN_SAVE_RESTORE
  81. default y
  82. config PM_SLEEP_ADVANCED_DEBUG
  83. bool
  84. depends on PM_ADVANCED_DEBUG
  85. default n
  86. config SUSPEND_NVS
  87. bool
  88. config SUSPEND
  89. bool "Suspend to RAM and standby"
  90. depends on PM && ARCH_SUSPEND_POSSIBLE
  91. select SUSPEND_NVS if HAS_IOMEM
  92. default y
  93. ---help---
  94. Allow the system to enter sleep states in which main memory is
  95. powered and thus its contents are preserved, such as the
  96. suspend-to-RAM state (e.g. the ACPI S3 state).
  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. You probably want to have your system's RTC driver statically
  105. linked, ensuring that it's available when this test runs.
  106. config SUSPEND_FREEZER
  107. bool "Enable freezer for suspend to RAM/standby" \
  108. if ARCH_WANTS_FREEZER_CONTROL || BROKEN
  109. depends on SUSPEND
  110. default y
  111. help
  112. This allows you to turn off the freezer for suspend. If this is
  113. done, no tasks are frozen for suspend to RAM/standby.
  114. Turning OFF this setting is NOT recommended! If in doubt, say Y.
  115. config HIBERNATION
  116. bool "Hibernation (aka 'suspend to disk')"
  117. depends on PM && SWAP && ARCH_HIBERNATION_POSSIBLE
  118. select LZO_COMPRESS
  119. select LZO_DECOMPRESS
  120. select SUSPEND_NVS if HAS_IOMEM
  121. ---help---
  122. Enable the suspend to disk (STD) functionality, which is usually
  123. called "hibernation" in user interfaces. STD checkpoints the
  124. system and powers it off; and restores that checkpoint on reboot.
  125. You can suspend your machine with 'echo disk > /sys/power/state'
  126. after placing resume=/dev/swappartition on the kernel command line
  127. in your bootloader's configuration file.
  128. Alternatively, you can use the additional userland tools available
  129. from <http://suspend.sf.net>.
  130. In principle it does not require ACPI or APM, although for example
  131. ACPI will be used for the final steps when it is available. One
  132. of the reasons to use software suspend is that the firmware hooks
  133. for suspend states like suspend-to-RAM (STR) often don't work very
  134. well with Linux.
  135. It creates an image which is saved in your active swap. Upon the next
  136. boot, pass the 'resume=/dev/swappartition' argument to the kernel to
  137. have it detect the saved image, restore memory state from it, and
  138. continue to run as before. If you do not want the previous state to
  139. be reloaded, then use the 'noresume' kernel command line argument.
  140. Note, however, that fsck will be run on your filesystems and you will
  141. need to run mkswap against the swap partition used for the suspend.
  142. It also works with swap files to a limited extent (for details see
  143. <file:Documentation/power/swsusp-and-swap-files.txt>).
  144. Right now you may boot without resuming and resume later but in the
  145. meantime you cannot use the swap partition(s)/file(s) involved in
  146. suspending. Also in this case you must not use the filesystems
  147. that were mounted before the suspend. In particular, you MUST NOT
  148. MOUNT any journaled filesystems mounted before the suspend or they
  149. will get corrupted in a nasty way.
  150. For more information take a look at <file:Documentation/power/swsusp.txt>.
  151. config PM_STD_PARTITION
  152. string "Default resume partition"
  153. depends on HIBERNATION
  154. default ""
  155. ---help---
  156. The default resume partition is the partition that the suspend-
  157. to-disk implementation will look for a suspended disk image.
  158. The partition specified here will be different for almost every user.
  159. It should be a valid swap partition (at least for now) that is turned
  160. on before suspending.
  161. The partition specified can be overridden by specifying:
  162. resume=/dev/<other device>
  163. which will set the resume partition to the device specified.
  164. Note there is currently not a way to specify which device to save the
  165. suspended image to. It will simply pick the first available swap
  166. device.
  167. config APM_EMULATION
  168. tristate "Advanced Power Management Emulation"
  169. depends on PM && SYS_SUPPORTS_APM_EMULATION
  170. help
  171. APM is a BIOS specification for saving power using several different
  172. techniques. This is mostly useful for battery powered laptops with
  173. APM compliant BIOSes. If you say Y here, the system time will be
  174. reset after a RESUME operation, the /proc/apm device will provide
  175. battery status information, and user-space programs will receive
  176. notification of APM "events" (e.g. battery status change).
  177. In order to use APM, you will need supporting software. For location
  178. and more information, read <file:Documentation/power/pm.txt> and the
  179. Battery Powered Linux mini-HOWTO, available from
  180. <http://www.tldp.org/docs.html#howto>.
  181. This driver does not spin down disk drives (see the hdparm(8)
  182. manpage ("man 8 hdparm") for that), and it doesn't turn off
  183. VESA-compliant "green" monitors.
  184. Generally, if you don't have a battery in your machine, there isn't
  185. much point in using this driver and you should say N. If you get
  186. random kernel OOPSes or reboots that don't seem to be related to
  187. anything, try disabling/enabling this option (or disabling/enabling
  188. APM in your BIOS).
  189. config PM_RUNTIME
  190. bool "Run-time PM core functionality"
  191. depends on PM
  192. ---help---
  193. Enable functionality allowing I/O devices to be put into energy-saving
  194. (low power) states at run time (or autosuspended) after a specified
  195. period of inactivity and woken up in response to a hardware-generated
  196. wake-up event or a driver's request.
  197. Hardware support is generally required for this functionality to work
  198. and the bus type drivers of the buses the devices are on are
  199. responsible for the actual handling of the autosuspend requests and
  200. wake-up events.
  201. config PM_OPS
  202. bool
  203. depends on PM_SLEEP || PM_RUNTIME
  204. default y
  205. config ARCH_HAS_OPP
  206. bool
  207. config PM_OPP
  208. bool "Operating Performance Point (OPP) Layer library"
  209. depends on PM
  210. depends on ARCH_HAS_OPP
  211. ---help---
  212. SOCs have a standard set of tuples consisting of frequency and
  213. voltage pairs that the device will support per voltage domain. This
  214. is called Operating Performance Point or OPP. The actual definitions
  215. of OPP varies over silicon within the same family of devices.
  216. OPP layer organizes the data internally using device pointers
  217. representing individual voltage domains and provides SOC
  218. implementations a ready to use framework to manage OPPs.
  219. For more information, read <file:Documentation/power/opp.txt>