diff options
author | Rafael J. Wysocki <rjw@sisk.pl> | 2011-02-10 18:06:42 -0500 |
---|---|---|
committer | Rafael J. Wysocki <rjw@sisk.pl> | 2011-03-14 19:43:15 -0400 |
commit | 196ec243224bb38fc5c41d9fa4050f70708b7fb4 (patch) | |
tree | 691695deb4098c2bc2aedee45f8fb0d38e14555c /kernel/power/Kconfig | |
parent | 1eb208aea3179dd2fc0cdeea45ef869d75b4fe70 (diff) |
PM: Reorder power management Kconfig options
Reorder configuration options in kernel/power/Kconfig so that
the options depended on are at the top of the list.
This patch doesn't introduce any functional changes.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Diffstat (limited to 'kernel/power/Kconfig')
-rw-r--r-- | kernel/power/Kconfig | 222 |
1 files changed, 111 insertions, 111 deletions
diff --git a/kernel/power/Kconfig b/kernel/power/Kconfig index d739cf612e50..1e4d9238c5da 100644 --- a/kernel/power/Kconfig +++ b/kernel/power/Kconfig | |||
@@ -1,89 +1,3 @@ | |||
1 | config PM | ||
2 | bool | ||
3 | depends on PM_SLEEP || PM_RUNTIME | ||
4 | default y | ||
5 | |||
6 | config PM_DEBUG | ||
7 | bool "Power Management Debug Support" | ||
8 | depends on PM | ||
9 | ---help--- | ||
10 | This option enables various debugging support in the Power Management | ||
11 | code. This is helpful when debugging and reporting PM bugs, like | ||
12 | suspend support. | ||
13 | |||
14 | config PM_ADVANCED_DEBUG | ||
15 | bool "Extra PM attributes in sysfs for low-level debugging/testing" | ||
16 | depends on PM_DEBUG | ||
17 | default n | ||
18 | ---help--- | ||
19 | Add extra sysfs attributes allowing one to access some Power Management | ||
20 | fields of device objects from user space. If you are not a kernel | ||
21 | developer interested in debugging/testing Power Management, say "no". | ||
22 | |||
23 | config PM_VERBOSE | ||
24 | bool "Verbose Power Management debugging" | ||
25 | depends on PM_DEBUG | ||
26 | default n | ||
27 | ---help--- | ||
28 | This option enables verbose messages from the Power Management code. | ||
29 | |||
30 | config CAN_PM_TRACE | ||
31 | def_bool y | ||
32 | depends on PM_DEBUG && PM_SLEEP && EXPERIMENTAL | ||
33 | |||
34 | config PM_TRACE | ||
35 | bool | ||
36 | help | ||
37 | This enables code to save the last PM event point across | ||
38 | reboot. The architecture needs to support this, x86 for | ||
39 | example does by saving things in the RTC, see below. | ||
40 | |||
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 | |||
45 | The way the information is presented is architecture- | ||
46 | dependent, x86 will print the information during a | ||
47 | late_initcall. | ||
48 | |||
49 | config PM_TRACE_RTC | ||
50 | bool "Suspend/resume event tracing" | ||
51 | depends on CAN_PM_TRACE | ||
52 | depends on X86 | ||
53 | select PM_TRACE | ||
54 | default n | ||
55 | ---help--- | ||
56 | This enables some cheesy code to save the last PM event point in the | ||
57 | RTC across reboots, so that you can debug a machine that just hangs | ||
58 | during suspend (or more commonly, during resume). | ||
59 | |||
60 | To use this debugging feature you should attempt to suspend the | ||
61 | machine, reboot it and then run | ||
62 | |||
63 | dmesg -s 1000000 | grep 'hash matches' | ||
64 | |||
65 | CAUTION: this option will cause your machine's real-time clock to be | ||
66 | set to an invalid time after a resume. | ||
67 | |||
68 | config PM_SLEEP_SMP | ||
69 | bool | ||
70 | depends on SMP | ||
71 | depends on ARCH_SUSPEND_POSSIBLE || ARCH_HIBERNATION_POSSIBLE | ||
72 | depends on PM_SLEEP | ||
73 | select HOTPLUG | ||
74 | select HOTPLUG_CPU | ||
75 | default y | ||
76 | |||
77 | config PM_SLEEP | ||
78 | bool | ||
79 | depends on SUSPEND || HIBERNATION || XEN_SAVE_RESTORE | ||
80 | default y | ||
81 | |||
82 | config PM_SLEEP_ADVANCED_DEBUG | ||
83 | bool | ||
84 | depends on PM_ADVANCED_DEBUG | ||
85 | default n | ||
86 | |||
87 | config SUSPEND | 1 | config SUSPEND |
88 | bool "Suspend to RAM and standby" | 2 | bool "Suspend to RAM and standby" |
89 | depends on ARCH_SUSPEND_POSSIBLE | 3 | depends on ARCH_SUSPEND_POSSIBLE |
@@ -93,17 +7,6 @@ config SUSPEND | |||
93 | powered and thus its contents are preserved, such as the | 7 | powered and thus its contents are preserved, such as the |
94 | suspend-to-RAM state (e.g. the ACPI S3 state). | 8 | suspend-to-RAM state (e.g. the ACPI S3 state). |
95 | 9 | ||
96 | config PM_TEST_SUSPEND | ||
97 | bool "Test suspend/resume and wakealarm during bootup" | ||
98 | depends on SUSPEND && PM_DEBUG && RTC_CLASS=y | ||
99 | ---help--- | ||
100 | This option will let you suspend your machine during bootup, and | ||
101 | make it wake up a few seconds later using an RTC wakeup alarm. | ||
102 | Enable this with a kernel parameter like "test_suspend=mem". | ||
103 | |||
104 | You probably want to have your system's RTC driver statically | ||
105 | linked, ensuring that it's available when this test runs. | ||
106 | |||
107 | config SUSPEND_FREEZER | 10 | config SUSPEND_FREEZER |
108 | bool "Enable freezer for suspend to RAM/standby" \ | 11 | bool "Enable freezer for suspend to RAM/standby" \ |
109 | if ARCH_WANTS_FREEZER_CONTROL || BROKEN | 12 | if ARCH_WANTS_FREEZER_CONTROL || BROKEN |
@@ -180,6 +83,117 @@ config PM_STD_PARTITION | |||
180 | suspended image to. It will simply pick the first available swap | 83 | suspended image to. It will simply pick the first available swap |
181 | device. | 84 | device. |
182 | 85 | ||
86 | config PM_SLEEP | ||
87 | bool | ||
88 | depends on SUSPEND || HIBERNATION || XEN_SAVE_RESTORE | ||
89 | default y | ||
90 | |||
91 | config PM_SLEEP_SMP | ||
92 | bool | ||
93 | depends on SMP | ||
94 | depends on ARCH_SUSPEND_POSSIBLE || ARCH_HIBERNATION_POSSIBLE | ||
95 | depends on PM_SLEEP | ||
96 | select HOTPLUG | ||
97 | select HOTPLUG_CPU | ||
98 | default y | ||
99 | |||
100 | config PM_RUNTIME | ||
101 | bool "Run-time PM core functionality" | ||
102 | depends on !IA64_HP_SIM | ||
103 | ---help--- | ||
104 | Enable functionality allowing I/O devices to be put into energy-saving | ||
105 | (low power) states at run time (or autosuspended) after a specified | ||
106 | period of inactivity and woken up in response to a hardware-generated | ||
107 | wake-up event or a driver's request. | ||
108 | |||
109 | Hardware support is generally required for this functionality to work | ||
110 | and the bus type drivers of the buses the devices are on are | ||
111 | responsible for the actual handling of the autosuspend requests and | ||
112 | wake-up events. | ||
113 | |||
114 | config PM | ||
115 | bool | ||
116 | depends on PM_SLEEP || PM_RUNTIME | ||
117 | default y | ||
118 | |||
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 | |||
127 | config PM_VERBOSE | ||
128 | bool "Verbose Power Management debugging" | ||
129 | depends on PM_DEBUG | ||
130 | default n | ||
131 | ---help--- | ||
132 | This option enables verbose messages from the Power Management code. | ||
133 | |||
134 | config PM_ADVANCED_DEBUG | ||
135 | bool "Extra PM attributes in sysfs for low-level debugging/testing" | ||
136 | depends on PM_DEBUG | ||
137 | default n | ||
138 | ---help--- | ||
139 | Add extra sysfs attributes allowing one to access some Power Management | ||
140 | fields of device objects from user space. If you are not a kernel | ||
141 | developer interested in debugging/testing Power Management, say "no". | ||
142 | |||
143 | config PM_SLEEP_ADVANCED_DEBUG | ||
144 | bool | ||
145 | depends on PM_ADVANCED_DEBUG | ||
146 | default n | ||
147 | |||
148 | config PM_TEST_SUSPEND | ||
149 | bool "Test suspend/resume and wakealarm during bootup" | ||
150 | depends on SUSPEND && PM_DEBUG && RTC_CLASS=y | ||
151 | ---help--- | ||
152 | This option will let you suspend your machine during bootup, and | ||
153 | make it wake up a few seconds later using an RTC wakeup alarm. | ||
154 | Enable this with a kernel parameter like "test_suspend=mem". | ||
155 | |||
156 | You probably want to have your system's RTC driver statically | ||
157 | linked, ensuring that it's available when this test runs. | ||
158 | |||
159 | config CAN_PM_TRACE | ||
160 | def_bool y | ||
161 | depends on PM_DEBUG && PM_SLEEP && EXPERIMENTAL | ||
162 | |||
163 | config PM_TRACE | ||
164 | bool | ||
165 | help | ||
166 | This enables code to save the last PM event point across | ||
167 | reboot. The architecture needs to support this, x86 for | ||
168 | example does by saving things in the RTC, see below. | ||
169 | |||
170 | The architecture specific code must provide the extern | ||
171 | functions from <linux/resume-trace.h> as well as the | ||
172 | <asm/resume-trace.h> header with a TRACE_RESUME() macro. | ||
173 | |||
174 | The way the information is presented is architecture- | ||
175 | dependent, x86 will print the information during a | ||
176 | late_initcall. | ||
177 | |||
178 | config PM_TRACE_RTC | ||
179 | bool "Suspend/resume event tracing" | ||
180 | depends on CAN_PM_TRACE | ||
181 | depends on X86 | ||
182 | select PM_TRACE | ||
183 | default n | ||
184 | ---help--- | ||
185 | This enables some cheesy code to save the last PM event point in the | ||
186 | RTC across reboots, so that you can debug a machine that just hangs | ||
187 | during suspend (or more commonly, during resume). | ||
188 | |||
189 | To use this debugging feature you should attempt to suspend the | ||
190 | machine, reboot it and then run | ||
191 | |||
192 | dmesg -s 1000000 | grep 'hash matches' | ||
193 | |||
194 | CAUTION: this option will cause your machine's real-time clock to be | ||
195 | set to an invalid time after a resume. | ||
196 | |||
183 | config APM_EMULATION | 197 | config APM_EMULATION |
184 | tristate "Advanced Power Management Emulation" | 198 | tristate "Advanced Power Management Emulation" |
185 | depends on PM && SYS_SUPPORTS_APM_EMULATION | 199 | depends on PM && SYS_SUPPORTS_APM_EMULATION |
@@ -206,20 +220,6 @@ config APM_EMULATION | |||
206 | anything, try disabling/enabling this option (or disabling/enabling | 220 | anything, try disabling/enabling this option (or disabling/enabling |
207 | APM in your BIOS). | 221 | APM in your BIOS). |
208 | 222 | ||
209 | config PM_RUNTIME | ||
210 | bool "Run-time PM core functionality" | ||
211 | depends on !IA64_HP_SIM | ||
212 | ---help--- | ||
213 | Enable functionality allowing I/O devices to be put into energy-saving | ||
214 | (low power) states at run time (or autosuspended) after a specified | ||
215 | period of inactivity and woken up in response to a hardware-generated | ||
216 | wake-up event or a driver's request. | ||
217 | |||
218 | Hardware support is generally required for this functionality to work | ||
219 | and the bus type drivers of the buses the devices are on are | ||
220 | responsible for the actual handling of the autosuspend requests and | ||
221 | wake-up events. | ||
222 | |||
223 | config PM_OPS | 223 | config PM_OPS |
224 | bool | 224 | bool |
225 | depends on PM_SLEEP || PM_RUNTIME | 225 | depends on PM_SLEEP || PM_RUNTIME |