Kconfig 10 KB

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