Root/
1 | # |
2 | # ACPI Configuration |
3 | # |
4 | |
5 | menuconfig ACPI |
6 | bool "ACPI (Advanced Configuration and Power Interface) Support" |
7 | depends on !IA64_HP_SIM |
8 | depends on IA64 || X86 |
9 | depends on PCI |
10 | select PNP |
11 | default y |
12 | help |
13 | Advanced Configuration and Power Interface (ACPI) support for |
14 | Linux requires an ACPI-compliant platform (hardware/firmware), |
15 | and assumes the presence of OS-directed configuration and power |
16 | management (OSPM) software. This option will enlarge your |
17 | kernel by about 70K. |
18 | |
19 | Linux ACPI provides a robust functional replacement for several |
20 | legacy configuration and power management interfaces, including |
21 | the Plug-and-Play BIOS specification (PnP BIOS), the |
22 | MultiProcessor Specification (MPS), and the Advanced Power |
23 | Management (APM) specification. If both ACPI and APM support |
24 | are configured, ACPI is used. |
25 | |
26 | The project home page for the Linux ACPI subsystem is here: |
27 | <http://www.lesswatts.org/projects/acpi/> |
28 | |
29 | Linux support for ACPI is based on Intel Corporation's ACPI |
30 | Component Architecture (ACPI CA). For more information on the |
31 | ACPI CA, see: |
32 | <http://acpica.org/> |
33 | |
34 | ACPI is an open industry specification co-developed by |
35 | Hewlett-Packard, Intel, Microsoft, Phoenix, and Toshiba. |
36 | The specification is available at: |
37 | <http://www.acpi.info> |
38 | |
39 | if ACPI |
40 | |
41 | config ACPI_SLEEP |
42 | bool |
43 | depends on SUSPEND || HIBERNATION |
44 | default y |
45 | |
46 | config ACPI_PROCFS |
47 | bool "Deprecated /proc/acpi files" |
48 | depends on PROC_FS |
49 | help |
50 | For backwards compatibility, this option allows |
51 | deprecated /proc/acpi/ files to exist, even when |
52 | they have been replaced by functions in /sys. |
53 | |
54 | This option has no effect on /proc/acpi/ files |
55 | and functions which do not yet exist in /sys. |
56 | |
57 | Say N to delete /proc/acpi/ files that have moved to /sys/ |
58 | |
59 | config ACPI_PROCFS_POWER |
60 | bool "Deprecated power /proc/acpi directories" |
61 | depends on PROC_FS |
62 | help |
63 | For backwards compatibility, this option allows |
64 | deprecated power /proc/acpi/ directories to exist, even when |
65 | they have been replaced by functions in /sys. |
66 | The deprecated directories (and their replacements) include: |
67 | /proc/acpi/battery/* (/sys/class/power_supply/*) |
68 | /proc/acpi/ac_adapter/* (sys/class/power_supply/*) |
69 | This option has no effect on /proc/acpi/ directories |
70 | and functions, which do not yet exist in /sys |
71 | This option, together with the proc directories, will be |
72 | deleted in 2.6.39. |
73 | |
74 | Say N to delete power /proc/acpi/ directories that have moved to /sys/ |
75 | |
76 | config ACPI_EC_DEBUGFS |
77 | tristate "EC read/write access through /sys/kernel/debug/ec" |
78 | default n |
79 | help |
80 | Say N to disable Embedded Controller /sys/kernel/debug interface |
81 | |
82 | Be aware that using this interface can confuse your Embedded |
83 | Controller in a way that a normal reboot is not enough. You then |
84 | have to power off your system, and remove the laptop battery for |
85 | some seconds. |
86 | An Embedded Controller typically is available on laptops and reads |
87 | sensor values like battery state and temperature. |
88 | The kernel accesses the EC through ACPI parsed code provided by BIOS |
89 | tables. This option allows to access the EC directly without ACPI |
90 | code being involved. |
91 | Thus this option is a debug option that helps to write ACPI drivers |
92 | and can be used to identify ACPI code or EC firmware bugs. |
93 | |
94 | config ACPI_PROC_EVENT |
95 | bool "Deprecated /proc/acpi/event support" |
96 | depends on PROC_FS |
97 | default y |
98 | help |
99 | A user-space daemon, acpid, typically reads /proc/acpi/event |
100 | and handles all ACPI-generated events. |
101 | |
102 | These events are now delivered to user-space either |
103 | via the input layer or as netlink events. |
104 | |
105 | This build option enables the old code for legacy |
106 | user-space implementation. After some time, this will |
107 | be moved under CONFIG_ACPI_PROCFS, and then deleted. |
108 | |
109 | Say Y here to retain the old behaviour. Say N if your |
110 | user-space is newer than kernel 2.6.23 (September 2007). |
111 | |
112 | config ACPI_AC |
113 | tristate "AC Adapter" |
114 | depends on X86 |
115 | select POWER_SUPPLY |
116 | default y |
117 | help |
118 | This driver supports the AC Adapter object, which indicates |
119 | whether a system is on AC or not. If you have a system that can |
120 | switch between A/C and battery, say Y. |
121 | |
122 | To compile this driver as a module, choose M here: |
123 | the module will be called ac. |
124 | |
125 | config ACPI_BATTERY |
126 | tristate "Battery" |
127 | depends on X86 |
128 | select POWER_SUPPLY |
129 | default y |
130 | help |
131 | This driver adds support for battery information through |
132 | /proc/acpi/battery. If you have a mobile system with a battery, |
133 | say Y. |
134 | |
135 | To compile this driver as a module, choose M here: |
136 | the module will be called battery. |
137 | |
138 | config ACPI_BUTTON |
139 | tristate "Button" |
140 | depends on INPUT |
141 | default y |
142 | help |
143 | This driver handles events on the power, sleep, and lid buttons. |
144 | A daemon reads /proc/acpi/event and perform user-defined actions |
145 | such as shutting down the system. This is necessary for |
146 | software-controlled poweroff. |
147 | |
148 | To compile this driver as a module, choose M here: |
149 | the module will be called button. |
150 | |
151 | config ACPI_VIDEO |
152 | tristate "Video" |
153 | depends on X86 && BACKLIGHT_CLASS_DEVICE && VIDEO_OUTPUT_CONTROL |
154 | depends on INPUT |
155 | select THERMAL |
156 | help |
157 | This driver implements the ACPI Extensions For Display Adapters |
158 | for integrated graphics devices on motherboard, as specified in |
159 | ACPI 2.0 Specification, Appendix B. This supports basic operations |
160 | such as defining the video POST device, retrieving EDID information, |
161 | and setting up a video output. |
162 | |
163 | To compile this driver as a module, choose M here: |
164 | the module will be called video. |
165 | |
166 | config ACPI_FAN |
167 | tristate "Fan" |
168 | select THERMAL |
169 | default y |
170 | help |
171 | This driver supports ACPI fan devices, allowing user-mode |
172 | applications to perform basic fan control (on, off, status). |
173 | |
174 | To compile this driver as a module, choose M here: |
175 | the module will be called fan. |
176 | |
177 | config ACPI_DOCK |
178 | bool "Dock" |
179 | depends on EXPERIMENTAL |
180 | help |
181 | This driver supports ACPI-controlled docking stations and removable |
182 | drive bays such as the IBM Ultrabay and the Dell Module Bay. |
183 | |
184 | config ACPI_PROCESSOR |
185 | tristate "Processor" |
186 | select THERMAL |
187 | select CPU_IDLE |
188 | default y |
189 | help |
190 | This driver installs ACPI as the idle handler for Linux and uses |
191 | ACPI C2 and C3 processor states to save power on systems that |
192 | support it. It is required by several flavors of cpufreq |
193 | performance-state drivers. |
194 | |
195 | To compile this driver as a module, choose M here: |
196 | the module will be called processor. |
197 | config ACPI_IPMI |
198 | tristate "IPMI" |
199 | depends on EXPERIMENTAL && IPMI_SI && IPMI_HANDLER |
200 | default n |
201 | help |
202 | This driver enables the ACPI to access the BMC controller. And it |
203 | uses the IPMI request/response message to communicate with BMC |
204 | controller, which can be found on on the server. |
205 | |
206 | To compile this driver as a module, choose M here: |
207 | the module will be called as acpi_ipmi. |
208 | |
209 | config ACPI_HOTPLUG_CPU |
210 | bool |
211 | depends on EXPERIMENTAL && ACPI_PROCESSOR && HOTPLUG_CPU |
212 | select ACPI_CONTAINER |
213 | default y |
214 | |
215 | config ACPI_PROCESSOR_AGGREGATOR |
216 | tristate "Processor Aggregator" |
217 | depends on ACPI_PROCESSOR |
218 | depends on EXPERIMENTAL |
219 | depends on X86 |
220 | help |
221 | ACPI 4.0 defines processor Aggregator, which enables OS to perform |
222 | specific processor configuration and control that applies to all |
223 | processors in the platform. Currently only logical processor idling |
224 | is defined, which is to reduce power consumption. This driver |
225 | supports the new device. |
226 | |
227 | config ACPI_THERMAL |
228 | tristate "Thermal Zone" |
229 | depends on ACPI_PROCESSOR |
230 | select THERMAL |
231 | default y |
232 | help |
233 | This driver supports ACPI thermal zones. Most mobile and |
234 | some desktop systems support ACPI thermal zones. It is HIGHLY |
235 | recommended that this option be enabled, as your processor(s) |
236 | may be damaged without it. |
237 | |
238 | To compile this driver as a module, choose M here: |
239 | the module will be called thermal. |
240 | |
241 | config ACPI_NUMA |
242 | bool "NUMA support" |
243 | depends on NUMA |
244 | depends on (X86 || IA64) |
245 | default y if IA64_GENERIC || IA64_SGI_SN2 |
246 | |
247 | config ACPI_CUSTOM_DSDT_FILE |
248 | string "Custom DSDT Table file to include" |
249 | default "" |
250 | depends on !STANDALONE |
251 | help |
252 | This option supports a custom DSDT by linking it into the kernel. |
253 | See Documentation/acpi/dsdt-override.txt |
254 | |
255 | Enter the full path name to the file which includes the AmlCode |
256 | declaration. |
257 | |
258 | If unsure, don't enter a file name. |
259 | |
260 | config ACPI_CUSTOM_DSDT |
261 | bool |
262 | default ACPI_CUSTOM_DSDT_FILE != "" |
263 | |
264 | config ACPI_BLACKLIST_YEAR |
265 | int "Disable ACPI for systems before Jan 1st this year" if X86_32 |
266 | default 0 |
267 | help |
268 | Enter a 4-digit year, e.g., 2001, to disable ACPI by default |
269 | on platforms with DMI BIOS date before January 1st that year. |
270 | "acpi=force" can be used to override this mechanism. |
271 | |
272 | Enter 0 to disable this mechanism and allow ACPI to |
273 | run by default no matter what the year. (default) |
274 | |
275 | config ACPI_DEBUG |
276 | bool "Debug Statements" |
277 | default n |
278 | help |
279 | The ACPI subsystem can produce debug output. Saying Y enables this |
280 | output and increases the kernel size by around 50K. |
281 | |
282 | Use the acpi.debug_layer and acpi.debug_level kernel command-line |
283 | parameters documented in Documentation/acpi/debug.txt and |
284 | Documentation/kernel-parameters.txt to control the type and |
285 | amount of debug output. |
286 | |
287 | config ACPI_DEBUG_FUNC_TRACE |
288 | bool "Additionally enable ACPI function tracing" |
289 | default n |
290 | depends on ACPI_DEBUG |
291 | help |
292 | ACPI Debug Statements slow down ACPI processing. Function trace |
293 | is about half of the penalty and is rarely useful. |
294 | |
295 | config ACPI_PCI_SLOT |
296 | tristate "PCI slot detection driver" |
297 | depends on SYSFS |
298 | default n |
299 | help |
300 | This driver creates entries in /sys/bus/pci/slots/ for all PCI |
301 | slots in the system. This can help correlate PCI bus addresses, |
302 | i.e., segment/bus/device/function tuples, with physical slots in |
303 | the system. If you are unsure, say N. |
304 | |
305 | To compile this driver as a module, choose M here: |
306 | the module will be called pci_slot. |
307 | |
308 | config X86_PM_TIMER |
309 | bool "Power Management Timer Support" if EXPERT |
310 | depends on X86 |
311 | default y |
312 | help |
313 | The Power Management Timer is available on all ACPI-capable, |
314 | in most cases even if ACPI is unusable or blacklisted. |
315 | |
316 | This timing source is not affected by power management features |
317 | like aggressive processor idling, throttling, frequency and/or |
318 | voltage scaling, unlike the commonly used Time Stamp Counter |
319 | (TSC) timing source. |
320 | |
321 | You should nearly always say Y here because many modern |
322 | systems require this timer. |
323 | |
324 | config ACPI_CONTAINER |
325 | tristate "Container and Module Devices (EXPERIMENTAL)" |
326 | depends on EXPERIMENTAL |
327 | default (ACPI_HOTPLUG_MEMORY || ACPI_HOTPLUG_CPU || ACPI_HOTPLUG_IO) |
328 | help |
329 | This driver supports ACPI Container and Module devices (IDs |
330 | ACPI0004, PNP0A05, and PNP0A06). |
331 | |
332 | This helps support hotplug of nodes, CPUs, and memory. |
333 | |
334 | To compile this driver as a module, choose M here: |
335 | the module will be called container. |
336 | |
337 | config ACPI_HOTPLUG_MEMORY |
338 | tristate "Memory Hotplug" |
339 | depends on MEMORY_HOTPLUG |
340 | default n |
341 | help |
342 | This driver supports ACPI memory hotplug. The driver |
343 | fields notifications on ACPI memory devices (PNP0C80), |
344 | which represent memory ranges that may be onlined or |
345 | offlined during runtime. |
346 | |
347 | If your hardware and firmware do not support adding or |
348 | removing memory devices at runtime, you need not enable |
349 | this driver. |
350 | |
351 | To compile this driver as a module, choose M here: |
352 | the module will be called acpi_memhotplug. |
353 | |
354 | config ACPI_SBS |
355 | tristate "Smart Battery System" |
356 | depends on X86 |
357 | select POWER_SUPPLY |
358 | help |
359 | This driver supports the Smart Battery System, another |
360 | type of access to battery information, found on some laptops. |
361 | |
362 | To compile this driver as a module, choose M here: |
363 | the modules will be called sbs and sbshc. |
364 | |
365 | config ACPI_HED |
366 | tristate "Hardware Error Device" |
367 | help |
368 | This driver supports the Hardware Error Device (PNP0C33), |
369 | which is used to report some hardware errors notified via |
370 | SCI, mainly the corrected errors. |
371 | |
372 | config ACPI_CUSTOM_METHOD |
373 | tristate "Allow ACPI methods to be inserted/replaced at run time" |
374 | depends on DEBUG_FS |
375 | default n |
376 | help |
377 | This debug facility allows ACPI AML methods to be inserted and/or |
378 | replaced without rebooting the system. For details refer to: |
379 | Documentation/acpi/method-customizing.txt. |
380 | |
381 | NOTE: This option is security sensitive, because it allows arbitrary |
382 | kernel memory to be written to by root (uid=0) users, allowing them |
383 | to bypass certain security measures (e.g. if root is not allowed to |
384 | load additional kernel modules after boot, this feature may be used |
385 | to override that restriction). |
386 | |
387 | config ACPI_BGRT |
388 | tristate "Boottime Graphics Resource Table support" |
389 | default n |
390 | help |
391 | This driver adds support for exposing the ACPI Boottime Graphics |
392 | Resource Table, which allows the operating system to obtain |
393 | data from the firmware boot splash. It will appear under |
394 | /sys/firmware/acpi/bgrt/ . |
395 | |
396 | source "drivers/acpi/apei/Kconfig" |
397 | |
398 | endif # ACPI |
399 |
Branches:
ben-wpan
ben-wpan-stefan
javiroman/ks7010
jz-2.6.34
jz-2.6.34-rc5
jz-2.6.34-rc6
jz-2.6.34-rc7
jz-2.6.35
jz-2.6.36
jz-2.6.37
jz-2.6.38
jz-2.6.39
jz-3.0
jz-3.1
jz-3.11
jz-3.12
jz-3.13
jz-3.15
jz-3.16
jz-3.18-dt
jz-3.2
jz-3.3
jz-3.4
jz-3.5
jz-3.6
jz-3.6-rc2-pwm
jz-3.9
jz-3.9-clk
jz-3.9-rc8
jz47xx
jz47xx-2.6.38
master
Tags:
od-2011-09-04
od-2011-09-18
v2.6.34-rc5
v2.6.34-rc6
v2.6.34-rc7
v3.9