6 bool "ACPI (Advanced Configuration and Power Interface) Support"
7 depends on !IA64_HP_SIM
8 depends on IA64 || X86 || (ARM64 && EXPERT)
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
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.
26 The project home page for the Linux ACPI subsystem is here:
27 <https://01.org/linux-acpi>
29 Linux support for ACPI is based on Intel Corporation's ACPI
30 Component Architecture (ACPI CA). For more information on the
34 ACPI is an open industry specification originally co-developed by
35 Hewlett-Packard, Intel, Microsoft, Phoenix, and Toshiba. Currently,
36 it is developed by the ACPI Specification Working Group (ASWG) under
37 the UEFI Forum and any UEFI member can join the ASWG and contribute
38 to the ACPI specification.
39 The specification is available at:
40 <http://www.acpi.info>
41 <http://www.uefi.org/acpi/specs>
45 config ACPI_LEGACY_TABLES_LOOKUP
48 config ARCH_MIGHT_HAVE_ACPI_PDC
51 config ACPI_GENERIC_GSI
54 config ACPI_SYSTEM_POWER_STATES_SUPPORT
57 config ACPI_CCA_REQUIRED
61 bool "AML debugger interface"
64 Enable in-kernel debugging of AML facilities: statistics,
65 internal object dump, single step control method execution.
66 This is still under development, currently enabling this only
67 results in the compilation of the ACPICA debugger files.
71 config ACPI_DEBUGGER_USER
72 tristate "Userspace debugger accessiblity"
75 Export /sys/kernel/debug/acpi/acpidbg for userspace utilities
76 to access the debugger functionalities.
82 depends on SUSPEND || HIBERNATION
83 depends on ACPI_SYSTEM_POWER_STATES_SUPPORT
86 config ACPI_PROCFS_POWER
87 bool "Deprecated power /proc/acpi directories"
88 depends on X86 && PROC_FS
90 For backwards compatibility, this option allows
91 deprecated power /proc/acpi/ directories to exist, even when
92 they have been replaced by functions in /sys.
93 The deprecated directories (and their replacements) include:
94 /proc/acpi/battery/* (/sys/class/power_supply/*)
95 /proc/acpi/ac_adapter/* (sys/class/power_supply/*)
96 This option has no effect on /proc/acpi/ directories
97 and functions, which do not yet exist in /sys
98 This option, together with the proc directories, will be
99 deleted in the future.
101 Say N to delete power /proc/acpi/ directories that have moved to /sys/
103 config ACPI_REV_OVERRIDE_POSSIBLE
104 bool "Allow supported ACPI revision to be overriden"
108 The platform firmware on some systems expects Linux to return "5" as
109 the supported ACPI revision which makes it expose system configuration
110 information in a special way.
112 For example, based on what ACPI exports as the supported revision,
113 Dell XPS 13 (2015) configures its audio device to either work in HDA
114 mode or in I2S mode, where the former is supposed to be used on Linux
115 until the latter is fully supported (in the kernel as well as in user
118 This option enables a DMI-based quirk for the above Dell machine (so
119 that HDA audio is exposed by the platform firmware to the kernel) and
120 makes it possible to force the kernel to return "5" as the supported
121 ACPI revision via the "acpi_rev_override" command line switch.
123 config ACPI_EC_DEBUGFS
124 tristate "EC read/write access through /sys/kernel/debug/ec"
127 Say N to disable Embedded Controller /sys/kernel/debug interface
129 Be aware that using this interface can confuse your Embedded
130 Controller in a way that a normal reboot is not enough. You then
131 have to power off your system, and remove the laptop battery for
133 An Embedded Controller typically is available on laptops and reads
134 sensor values like battery state and temperature.
135 The kernel accesses the EC through ACPI parsed code provided by BIOS
136 tables. This option allows to access the EC directly without ACPI
138 Thus this option is a debug option that helps to write ACPI drivers
139 and can be used to identify ACPI code or EC firmware bugs.
142 tristate "AC Adapter"
147 This driver supports the AC Adapter object, which indicates
148 whether a system is on AC or not. If you have a system that can
149 switch between A/C and battery, say Y.
151 To compile this driver as a module, choose M here:
152 the module will be called ac.
160 This driver adds support for battery information through
161 /proc/acpi/battery. If you have a mobile system with a battery,
164 To compile this driver as a module, choose M here:
165 the module will be called battery.
172 This driver handles events on the power, sleep, and lid buttons.
173 A daemon reads events from input devices or via netlink and
174 performs user-defined actions such as shutting down the system.
175 This is necessary for software-controlled poweroff.
177 To compile this driver as a module, choose M here:
178 the module will be called button.
182 depends on X86 && BACKLIGHT_CLASS_DEVICE
186 This driver implements the ACPI Extensions For Display Adapters
187 for integrated graphics devices on motherboard, as specified in
188 ACPI 2.0 Specification, Appendix B. This supports basic operations
189 such as defining the video POST device, retrieving EDID information,
190 and setting up a video output.
192 To compile this driver as a module, choose M here:
193 the module will be called video.
200 This driver supports ACPI fan devices, allowing user-mode
201 applications to perform basic fan control (on, off, status).
203 To compile this driver as a module, choose M here:
204 the module will be called fan.
209 This driver supports ACPI-controlled docking stations and removable
210 drive bays such as the IBM Ultrabay and the Dell Module Bay.
212 config ACPI_CPU_FREQ_PSS
216 config ACPI_PROCESSOR_IDLE
222 depends on ACPI_PROCESSOR
223 depends on !ACPI_CPU_FREQ_PSS
227 If this option is enabled, this file implements common functionality
228 to parse CPPC tables as described in the ACPI 5.1+ spec. The
229 routines implemented are meant to be used by other
230 drivers to control CPU performance using CPPC semantics.
231 If your platform does not support CPPC in firmware,
232 leave this option disabled.
234 config ACPI_PROCESSOR
236 depends on X86 || IA64 || ARM64
237 select ACPI_PROCESSOR_IDLE if X86 || IA64
238 select ACPI_CPU_FREQ_PSS if X86 || IA64
241 This driver adds support for the ACPI Processor package. It is required
242 by several flavors of cpufreq performance-state, thermal, throttling and
245 To compile this driver as a module, choose M here:
246 the module will be called processor.
253 This driver enables the ACPI to access the BMC controller. And it
254 uses the IPMI request/response message to communicate with BMC
255 controller, which can be found on on the server.
257 To compile this driver as a module, choose M here:
258 the module will be called as acpi_ipmi.
260 config ACPI_HOTPLUG_CPU
262 depends on ACPI_PROCESSOR && HOTPLUG_CPU
263 select ACPI_CONTAINER
266 config ACPI_PROCESSOR_AGGREGATOR
267 tristate "Processor Aggregator"
268 depends on ACPI_PROCESSOR
271 ACPI 4.0 defines processor Aggregator, which enables OS to perform
272 specific processor configuration and control that applies to all
273 processors in the platform. Currently only logical processor idling
274 is defined, which is to reduce power consumption. This driver
275 supports the new device.
278 tristate "Thermal Zone"
279 depends on ACPI_PROCESSOR
283 This driver supports ACPI thermal zones. Most mobile and
284 some desktop systems support ACPI thermal zones. It is HIGHLY
285 recommended that this option be enabled, as your processor(s)
286 may be damaged without it.
288 To compile this driver as a module, choose M here:
289 the module will be called thermal.
294 depends on (X86 || IA64)
295 default y if IA64_GENERIC || IA64_SGI_SN2
297 config ACPI_CUSTOM_DSDT_FILE
298 string "Custom DSDT Table file to include"
300 depends on !STANDALONE
302 This option supports a custom DSDT by linking it into the kernel.
303 See Documentation/acpi/dsdt-override.txt
305 Enter the full path name to the file which includes the AmlCode
308 If unsure, don't enter a file name.
310 config ACPI_CUSTOM_DSDT
312 default ACPI_CUSTOM_DSDT_FILE != ""
314 config ACPI_INITRD_TABLE_OVERRIDE
315 bool "ACPI tables override via initrd"
316 depends on BLK_DEV_INITRD && X86
319 This option provides functionality to override arbitrary ACPI tables
320 via initrd. No functional change if no ACPI tables are passed via
321 initrd, therefore it's safe to say Y.
322 See Documentation/acpi/initrd_table_override.txt for details
325 bool "Debug Statements"
328 The ACPI subsystem can produce debug output. Saying Y enables this
329 output and increases the kernel size by around 50K.
331 Use the acpi.debug_layer and acpi.debug_level kernel command-line
332 parameters documented in Documentation/acpi/debug.txt and
333 Documentation/kernel-parameters.txt to control the type and
334 amount of debug output.
337 bool "PCI slot detection driver"
341 This driver creates entries in /sys/bus/pci/slots/ for all PCI
342 slots in the system. This can help correlate PCI bus addresses,
343 i.e., segment/bus/device/function tuples, with physical slots in
344 the system. If you are unsure, say N.
347 bool "Power Management Timer Support" if EXPERT
351 The Power Management Timer is available on all ACPI-capable,
352 in most cases even if ACPI is unusable or blacklisted.
354 This timing source is not affected by power management features
355 like aggressive processor idling, throttling, frequency and/or
356 voltage scaling, unlike the commonly used Time Stamp Counter
359 You should nearly always say Y here because many modern
360 systems require this timer.
362 config ACPI_CONTAINER
363 bool "Container and Module Devices"
364 default (ACPI_HOTPLUG_MEMORY || ACPI_HOTPLUG_CPU)
366 This driver supports ACPI Container and Module devices (IDs
367 ACPI0004, PNP0A05, and PNP0A06).
369 This helps support hotplug of nodes, CPUs, and memory.
371 To compile this driver as a module, choose M here:
372 the module will be called container.
374 config ACPI_HOTPLUG_MEMORY
375 bool "Memory Hotplug"
376 depends on MEMORY_HOTPLUG
378 This driver supports ACPI memory hotplug. The driver
379 fields notifications on ACPI memory devices (PNP0C80),
380 which represent memory ranges that may be onlined or
381 offlined during runtime.
383 If your hardware and firmware do not support adding or
384 removing memory devices at runtime, you need not enable
387 To compile this driver as a module, choose M here:
388 the module will be called acpi_memhotplug.
390 config ACPI_HOTPLUG_IOAPIC
393 depends on X86_IO_APIC
397 tristate "Smart Battery System"
401 This driver supports the Smart Battery System, another
402 type of access to battery information, found on some laptops.
404 To compile this driver as a module, choose M here:
405 the modules will be called sbs and sbshc.
408 tristate "Hardware Error Device"
410 This driver supports the Hardware Error Device (PNP0C33),
411 which is used to report some hardware errors notified via
412 SCI, mainly the corrected errors.
414 config ACPI_CUSTOM_METHOD
415 tristate "Allow ACPI methods to be inserted/replaced at run time"
419 This debug facility allows ACPI AML methods to be inserted and/or
420 replaced without rebooting the system. For details refer to:
421 Documentation/acpi/method-customizing.txt.
423 NOTE: This option is security sensitive, because it allows arbitrary
424 kernel memory to be written to by root (uid=0) users, allowing them
425 to bypass certain security measures (e.g. if root is not allowed to
426 load additional kernel modules after boot, this feature may be used
427 to override that restriction).
430 bool "Boottime Graphics Resource Table support"
431 depends on EFI && X86
433 This driver adds support for exposing the ACPI Boottime Graphics
434 Resource Table, which allows the operating system to obtain
435 data from the firmware boot splash. It will appear under
436 /sys/firmware/acpi/bgrt/ .
438 config ACPI_REDUCED_HARDWARE_ONLY
439 bool "Hardware-reduced ACPI support only" if EXPERT
442 This config item changes the way the ACPI code is built. When this
443 option is selected, the kernel will use a specialized version of
444 ACPICA that ONLY supports the ACPI "reduced hardware" mode. The
445 resulting kernel will be smaller but it will also be restricted to
446 running in ACPI reduced hardware mode ONLY.
448 If you are unsure what to do, do not enable this option.
451 tristate "ACPI NVDIMM Firmware Interface Table (NFIT)"
452 depends on PHYS_ADDR_T_64BIT
454 depends on ARCH_HAS_MMIO_FLUSH
457 Infrastructure to probe ACPI 6 compliant platforms for
458 NVDIMMs (NFIT) and register a libnvdimm device tree. In
459 addition to storage devices this also enables libnvdimm to pass
460 ACPI._DSM messages for platform/dimm configuration.
462 To compile this driver as a module, choose M here:
463 the module will be called nfit.
465 config ACPI_NFIT_DEBUG
466 bool "NFIT DSM debug"
468 depends on DYNAMIC_DEBUG
471 Enabling this option causes the nfit driver to dump the
472 input and output buffers of _DSM operations on the ACPI0012
473 device and its children. This can be very verbose, so leave
474 it disabled unless you are debugging a hardware / firmware
477 source "drivers/acpi/apei/Kconfig"
480 tristate "Extended Error Log support"
481 depends on X86_MCE && X86_LOCAL_APIC
486 Certain usages such as Predictive Failure Analysis (PFA) require
487 more information about the error than what can be described in
488 processor machine check banks. Most server processors log
489 additional information about the error in processor uncore
490 registers. Since the addresses and layout of these registers vary
491 widely from one processor to another, system software cannot
492 readily make use of them. To complicate matters further, some of
493 the additional error information cannot be constructed without
494 detailed knowledge about platform topology.
496 Enhanced MCA Logging allows firmware to provide additional error
497 information to system software, synchronous with MCE or CMCI. This
498 driver adds support for that functionality with corresponding
499 tracepoint which carries that information to userspace.
501 menuconfig PMIC_OPREGION
502 bool "PMIC (Power Management Integrated Circuit) operation region support"
504 Select this option to enable support for ACPI operation
505 region of the PMIC chip. The operation region can be used
506 to control power rails and sensor reading/writing on the
510 config CRC_PMIC_OPREGION
511 bool "ACPI operation region support for CrystalCove PMIC"
512 depends on INTEL_SOC_PMIC
514 This config adds ACPI operation region support for CrystalCove PMIC.
516 config XPOWER_PMIC_OPREGION
517 bool "ACPI operation region support for XPower AXP288 PMIC"
518 depends on AXP288_ADC = y
520 This config adds ACPI operation region support for XPower AXP288 PMIC.