2
bool "Power Management support"
3
depends on !IA64_HP_SIM
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.
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>.
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.
23
bool "Power Management Debug Support"
26
This option enables various debugging support in the Power Management
27
code. This is helpful when debugging and reporting PM bugs, like
30
config PM_ADVANCED_DEBUG
31
bool "Extra PM attributes in sysfs for low-level debugging/testing"
35
Add extra sysfs attributes allowing one to access some Power Management
36
fields of device objects from user space. If you are not a kernel
37
developer interested in debugging/testing Power Management, say "no".
40
bool "Verbose Power Management debugging"
44
This option enables verbose messages from the Power Management code.
48
depends on PM_DEBUG && PM_SLEEP && EXPERIMENTAL
53
This enables code to save the last PM event point across
54
reboot. The architecture needs to support this, x86 for
55
example does by saving things in the RTC, see below.
57
The architecture specific code must provide the extern
58
functions from <linux/resume-trace.h> as well as the
59
<asm/resume-trace.h> header with a TRACE_RESUME() macro.
61
The way the information is presented is architecture-
62
dependent, x86 will print the information during a
66
bool "Suspend/resume event tracing"
67
depends on CAN_PM_TRACE
72
This enables some cheesy code to save the last PM event point in the
73
RTC across reboots, so that you can debug a machine that just hangs
74
during suspend (or more commonly, during resume).
76
To use this debugging feature you should attempt to suspend the
77
machine, reboot it and then run
79
dmesg -s 1000000 | grep 'hash matches'
81
CAUTION: this option will cause your machine's real-time clock to be
82
set to an invalid time after a resume.
87
depends on ARCH_SUSPEND_POSSIBLE || ARCH_HIBERNATION_POSSIBLE
95
depends on SUSPEND || HIBERNATION || XEN_SAVE_RESTORE
98
config PM_SLEEP_ADVANCED_DEBUG
100
depends on PM_ADVANCED_DEBUG
104
2
bool "Suspend to RAM and standby"
105
depends on PM && ARCH_SUSPEND_POSSIBLE
3
depends on ARCH_SUSPEND_POSSIBLE
108
6
Allow the system to enter sleep states in which main memory is
109
7
powered and thus its contents are preserved, such as the
110
8
suspend-to-RAM state (e.g. the ACPI S3 state).
112
config PM_TEST_SUSPEND
113
bool "Test suspend/resume and wakealarm during bootup"
114
depends on SUSPEND && PM_DEBUG && RTC_CLASS=y
116
This option will let you suspend your machine during bootup, and
117
make it wake up a few seconds later using an RTC wakeup alarm.
118
Enable this with a kernel parameter like "test_suspend=mem".
120
You probably want to have your system's RTC driver statically
121
linked, ensuring that it's available when this test runs.
123
10
config SUSPEND_FREEZER
124
11
bool "Enable freezer for suspend to RAM/standby" \
125
12
if ARCH_WANTS_FREEZER_CONTROL || BROKEN
196
87
suspended image to. It will simply pick the first available swap
92
depends on SUSPEND || HIBERNATE_CALLBACKS
97
depends on ARCH_SUSPEND_POSSIBLE || ARCH_HIBERNATION_POSSIBLE
103
bool "Run-time PM core functionality"
104
depends on !IA64_HP_SIM
106
Enable functionality allowing I/O devices to be put into energy-saving
107
(low power) states at run time (or autosuspended) after a specified
108
period of inactivity and woken up in response to a hardware-generated
109
wake-up event or a driver's request.
111
Hardware support is generally required for this functionality to work
112
and the bus type drivers of the buses the devices are on are
113
responsible for the actual handling of the autosuspend requests and
118
depends on PM_SLEEP || PM_RUNTIME
121
bool "Power Management Debug Support"
124
This option enables various debugging support in the Power Management
125
code. This is helpful when debugging and reporting PM bugs, like
128
config PM_ADVANCED_DEBUG
129
bool "Extra PM attributes in sysfs for low-level debugging/testing"
132
Add extra sysfs attributes allowing one to access some Power Management
133
fields of device objects from user space. If you are not a kernel
134
developer interested in debugging/testing Power Management, say "no".
136
config PM_TEST_SUSPEND
137
bool "Test suspend/resume and wakealarm during bootup"
138
depends on SUSPEND && PM_DEBUG && RTC_CLASS=y
140
This option will let you suspend your machine during bootup, and
141
make it wake up a few seconds later using an RTC wakeup alarm.
142
Enable this with a kernel parameter like "test_suspend=mem".
144
You probably want to have your system's RTC driver statically
145
linked, ensuring that it's available when this test runs.
149
depends on PM_DEBUG && PM_SLEEP
154
This enables code to save the last PM event point across
155
reboot. The architecture needs to support this, x86 for
156
example does by saving things in the RTC, see below.
158
The architecture specific code must provide the extern
159
functions from <linux/resume-trace.h> as well as the
160
<asm/resume-trace.h> header with a TRACE_RESUME() macro.
162
The way the information is presented is architecture-
163
dependent, x86 will print the information during a
167
bool "Suspend/resume event tracing"
168
depends on CAN_PM_TRACE
172
This enables some cheesy code to save the last PM event point in the
173
RTC across reboots, so that you can debug a machine that just hangs
174
during suspend (or more commonly, during resume).
176
To use this debugging feature you should attempt to suspend the
177
machine, reboot it and then run
179
dmesg -s 1000000 | grep 'hash matches'
181
CAUTION: this option will cause your machine's real-time clock to be
182
set to an invalid time after a resume.
199
184
config APM_EMULATION
200
185
tristate "Advanced Power Management Emulation"
201
186
depends on PM && SYS_SUPPORTS_APM_EMULATION
222
207
anything, try disabling/enabling this option (or disabling/enabling
223
208
APM in your BIOS).
226
bool "Run-time PM core functionality"
229
Enable functionality allowing I/O devices to be put into energy-saving
230
(low power) states at run time (or autosuspended) after a specified
231
period of inactivity and woken up in response to a hardware-generated
232
wake-up event or a driver's request.
234
Hardware support is generally required for this functionality to work
235
and the bus type drivers of the buses the devices are on are
236
responsible for the actual handling of the autosuspend requests and
241
depends on PM_SLEEP || PM_RUNTIME
244
210
config ARCH_HAS_OPP
248
214
bool "Operating Performance Point (OPP) Layer library"
250
215
depends on ARCH_HAS_OPP
252
217
SOCs have a standard set of tuples consisting of frequency and