6 bool "ACPI (Advanced Configuration and Power Interface) Support"
7 depends on !IA64_HP_SIM
8 depends on IA64 || X86 || ARM64
11 default y if (IA64 || X86)
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.
80 config ACPI_SPCR_TABLE
85 depends on SUSPEND || HIBERNATION
86 depends on ACPI_SYSTEM_POWER_STATES_SUPPORT
89 config ACPI_PROCFS_POWER
90 bool "Deprecated power /proc/acpi directories"
91 depends on X86 && PROC_FS
93 For backwards compatibility, this option allows
94 deprecated power /proc/acpi/ directories to exist, even when
95 they have been replaced by functions in /sys.
96 The deprecated directories (and their replacements) include:
97 /proc/acpi/battery/* (/sys/class/power_supply/*)
98 /proc/acpi/ac_adapter/* (sys/class/power_supply/*)
99 This option has no effect on /proc/acpi/ directories
100 and functions, which do not yet exist in /sys
101 This option, together with the proc directories, will be
102 deleted in the future.
104 Say N to delete power /proc/acpi/ directories that have moved to /sys/
106 config ACPI_REV_OVERRIDE_POSSIBLE
107 bool "Allow supported ACPI revision to be overridden"
111 The platform firmware on some systems expects Linux to return "5" as
112 the supported ACPI revision which makes it expose system configuration
113 information in a special way.
115 For example, based on what ACPI exports as the supported revision,
116 Dell XPS 13 (2015) configures its audio device to either work in HDA
117 mode or in I2S mode, where the former is supposed to be used on Linux
118 until the latter is fully supported (in the kernel as well as in user
121 This option enables a DMI-based quirk for the above Dell machine (so
122 that HDA audio is exposed by the platform firmware to the kernel) and
123 makes it possible to force the kernel to return "5" as the supported
124 ACPI revision via the "acpi_rev_override" command line switch.
126 config ACPI_EC_DEBUGFS
127 tristate "EC read/write access through /sys/kernel/debug/ec"
130 Say N to disable Embedded Controller /sys/kernel/debug interface
132 Be aware that using this interface can confuse your Embedded
133 Controller in a way that a normal reboot is not enough. You then
134 have to power off your system, and remove the laptop battery for
136 An Embedded Controller typically is available on laptops and reads
137 sensor values like battery state and temperature.
138 The kernel accesses the EC through ACPI parsed code provided by BIOS
139 tables. This option allows to access the EC directly without ACPI
141 Thus this option is a debug option that helps to write ACPI drivers
142 and can be used to identify ACPI code or EC firmware bugs.
145 tristate "AC Adapter"
150 This driver supports the AC Adapter object, which indicates
151 whether a system is on AC or not. If you have a system that can
152 switch between A/C and battery, say Y.
154 To compile this driver as a module, choose M here:
155 the module will be called ac.
163 This driver adds support for battery information through
164 /proc/acpi/battery. If you have a mobile system with a battery,
167 To compile this driver as a module, choose M here:
168 the module will be called battery.
175 This driver handles events on the power, sleep, and lid buttons.
176 A daemon reads events from input devices or via netlink and
177 performs user-defined actions such as shutting down the system.
178 This is necessary for software-controlled poweroff.
180 To compile this driver as a module, choose M here:
181 the module will be called button.
185 depends on X86 && BACKLIGHT_CLASS_DEVICE
189 This driver implements the ACPI Extensions For Display Adapters
190 for integrated graphics devices on motherboard, as specified in
191 ACPI 2.0 Specification, Appendix B. This supports basic operations
192 such as defining the video POST device, retrieving EDID information,
193 and setting up a video output.
195 To compile this driver as a module, choose M here:
196 the module will be called video.
203 This driver supports ACPI fan devices, allowing user-mode
204 applications to perform basic fan control (on, off, status).
206 To compile this driver as a module, choose M here:
207 the module will be called fan.
212 This driver supports ACPI-controlled docking stations and removable
213 drive bays such as the IBM Ultrabay and the Dell Module Bay.
215 config ACPI_CPU_FREQ_PSS
219 config ACPI_PROCESSOR_CSTATE
221 depends on IA64 || X86
223 config ACPI_PROCESSOR_IDLE
232 depends on ACPI_PROCESSOR
236 If this option is enabled, this file implements common functionality
237 to parse CPPC tables as described in the ACPI 5.1+ spec. The
238 routines implemented are meant to be used by other
239 drivers to control CPU performance using CPPC semantics.
240 If your platform does not support CPPC in firmware,
241 leave this option disabled.
243 config ACPI_PROCESSOR
245 depends on X86 || IA64 || ARM64
246 select ACPI_PROCESSOR_IDLE
247 select ACPI_CPU_FREQ_PSS if X86 || IA64
250 This driver adds support for the ACPI Processor package. It is required
251 by several flavors of cpufreq performance-state, thermal, throttling and
254 To compile this driver as a module, choose M here:
255 the module will be called processor.
259 depends on IPMI_HANDLER
262 This driver enables the ACPI to access the BMC controller. And it
263 uses the IPMI request/response message to communicate with BMC
264 controller, which can be found on on the server.
266 To compile this driver as a module, choose M here:
267 the module will be called as acpi_ipmi.
269 config ACPI_HOTPLUG_CPU
271 depends on ACPI_PROCESSOR && HOTPLUG_CPU
272 select ACPI_CONTAINER
275 config ACPI_PROCESSOR_AGGREGATOR
276 tristate "Processor Aggregator"
277 depends on ACPI_PROCESSOR
280 ACPI 4.0 defines processor Aggregator, which enables OS to perform
281 specific processor configuration and control that applies to all
282 processors in the platform. Currently only logical processor idling
283 is defined, which is to reduce power consumption. This driver
284 supports the new device.
287 tristate "Thermal Zone"
288 depends on ACPI_PROCESSOR
292 This driver supports ACPI thermal zones. Most mobile and
293 some desktop systems support ACPI thermal zones. It is HIGHLY
294 recommended that this option be enabled, as your processor(s)
295 may be damaged without it.
297 To compile this driver as a module, choose M here:
298 the module will be called thermal.
303 depends on (X86 || IA64 || ARM64)
304 default y if IA64_GENERIC || IA64_SGI_SN2 || ARM64
306 config ACPI_CUSTOM_DSDT_FILE
307 string "Custom DSDT Table file to include"
309 depends on !STANDALONE
311 This option supports a custom DSDT by linking it into the kernel.
312 See Documentation/acpi/dsdt-override.txt
314 Enter the full path name to the file which includes the AmlCode
317 If unsure, don't enter a file name.
319 config ACPI_CUSTOM_DSDT
321 default ACPI_CUSTOM_DSDT_FILE != ""
323 config ARCH_HAS_ACPI_TABLE_UPGRADE
326 config ACPI_TABLE_UPGRADE
327 bool "Allow upgrading ACPI tables via initrd"
328 depends on BLK_DEV_INITRD && ARCH_HAS_ACPI_TABLE_UPGRADE
331 This option provides functionality to upgrade arbitrary ACPI tables
332 via initrd. No functional change if no ACPI tables are passed via
333 initrd, therefore it's safe to say Y.
334 See Documentation/acpi/initrd_table_override.txt for details
337 bool "Debug Statements"
340 The ACPI subsystem can produce debug output. Saying Y enables this
341 output and increases the kernel size by around 50K.
343 Use the acpi.debug_layer and acpi.debug_level kernel command-line
344 parameters documented in Documentation/acpi/debug.txt and
345 Documentation/admin-guide/kernel-parameters.rst to control the type and
346 amount of debug output.
349 bool "PCI slot detection driver"
353 This driver creates entries in /sys/bus/pci/slots/ for all PCI
354 slots in the system. This can help correlate PCI bus addresses,
355 i.e., segment/bus/device/function tuples, with physical slots in
356 the system. If you are unsure, say N.
359 bool "Power Management Timer Support" if EXPERT
363 The Power Management Timer is available on all ACPI-capable,
364 in most cases even if ACPI is unusable or blacklisted.
366 This timing source is not affected by power management features
367 like aggressive processor idling, throttling, frequency and/or
368 voltage scaling, unlike the commonly used Time Stamp Counter
371 You should nearly always say Y here because many modern
372 systems require this timer.
374 config ACPI_CONTAINER
375 bool "Container and Module Devices"
376 default (ACPI_HOTPLUG_MEMORY || ACPI_HOTPLUG_CPU)
378 This driver supports ACPI Container and Module devices (IDs
379 ACPI0004, PNP0A05, and PNP0A06).
381 This helps support hotplug of nodes, CPUs, and memory.
383 To compile this driver as a module, choose M here:
384 the module will be called container.
386 config ACPI_HOTPLUG_MEMORY
387 bool "Memory Hotplug"
388 depends on MEMORY_HOTPLUG
390 This driver supports ACPI memory hotplug. The driver
391 fields notifications on ACPI memory devices (PNP0C80),
392 which represent memory ranges that may be onlined or
393 offlined during runtime.
395 If your hardware and firmware do not support adding or
396 removing memory devices at runtime, you need not enable
399 To compile this driver as a module, choose M here:
400 the module will be called acpi_memhotplug.
402 config ACPI_HOTPLUG_IOAPIC
405 depends on X86_IO_APIC
409 tristate "Smart Battery System"
413 This driver supports the Smart Battery System, another
414 type of access to battery information, found on some laptops.
416 To compile this driver as a module, choose M here:
417 the modules will be called sbs and sbshc.
420 tristate "Hardware Error Device"
422 This driver supports the Hardware Error Device (PNP0C33),
423 which is used to report some hardware errors notified via
424 SCI, mainly the corrected errors.
426 config ACPI_CUSTOM_METHOD
427 tristate "Allow ACPI methods to be inserted/replaced at run time"
431 This debug facility allows ACPI AML methods to be inserted and/or
432 replaced without rebooting the system. For details refer to:
433 Documentation/acpi/method-customizing.txt.
435 NOTE: This option is security sensitive, because it allows arbitrary
436 kernel memory to be written to by root (uid=0) users, allowing them
437 to bypass certain security measures (e.g. if root is not allowed to
438 load additional kernel modules after boot, this feature may be used
439 to override that restriction).
442 bool "Boottime Graphics Resource Table support"
443 depends on EFI && (X86 || ARM64)
445 This driver adds support for exposing the ACPI Boottime Graphics
446 Resource Table, which allows the operating system to obtain
447 data from the firmware boot splash. It will appear under
448 /sys/firmware/acpi/bgrt/ .
450 config ACPI_REDUCED_HARDWARE_ONLY
451 bool "Hardware-reduced ACPI support only" if EXPERT
454 This config item changes the way the ACPI code is built. When this
455 option is selected, the kernel will use a specialized version of
456 ACPICA that ONLY supports the ACPI "reduced hardware" mode. The
457 resulting kernel will be smaller but it will also be restricted to
458 running in ACPI reduced hardware mode ONLY.
460 If you are unsure what to do, do not enable this option.
462 source "drivers/acpi/nfit/Kconfig"
464 source "drivers/acpi/apei/Kconfig"
465 source "drivers/acpi/dptf/Kconfig"
471 tristate "Extended Error Log support"
472 depends on X86_MCE && X86_LOCAL_APIC && EDAC
476 Certain usages such as Predictive Failure Analysis (PFA) require
477 more information about the error than what can be described in
478 processor machine check banks. Most server processors log
479 additional information about the error in processor uncore
480 registers. Since the addresses and layout of these registers vary
481 widely from one processor to another, system software cannot
482 readily make use of them. To complicate matters further, some of
483 the additional error information cannot be constructed without
484 detailed knowledge about platform topology.
486 Enhanced MCA Logging allows firmware to provide additional error
487 information to system software, synchronous with MCE or CMCI. This
488 driver adds support for that functionality with corresponding
489 tracepoint which carries that information to userspace.
491 menuconfig PMIC_OPREGION
492 bool "PMIC (Power Management Integrated Circuit) operation region support"
494 Select this option to enable support for ACPI operation
495 region of the PMIC chip. The operation region can be used
496 to control power rails and sensor reading/writing on the
500 config CRC_PMIC_OPREGION
501 bool "ACPI operation region support for CrystalCove PMIC"
502 depends on INTEL_SOC_PMIC
504 This config adds ACPI operation region support for CrystalCove PMIC.
506 config XPOWER_PMIC_OPREGION
507 bool "ACPI operation region support for XPower AXP288 PMIC"
508 depends on MFD_AXP20X_I2C
510 This config adds ACPI operation region support for XPower AXP288 PMIC.
512 config BXT_WC_PMIC_OPREGION
513 bool "ACPI operation region support for BXT WhiskeyCove PMIC"
514 depends on INTEL_SOC_PMIC_BXTWC
516 This config adds ACPI operation region support for BXT WhiskeyCove PMIC.
518 config CHT_WC_PMIC_OPREGION
519 bool "ACPI operation region support for CHT Whiskey Cove PMIC"
520 depends on INTEL_SOC_PMIC_CHTWC
522 This config adds ACPI operation region support for CHT Whiskey Cove PMIC.
527 tristate "ACPI configfs support"
530 Select this option to enable support for ACPI configuration from
531 userspace. The configurable ACPI groups will be visible under
532 /config/acpi, assuming configfs is mounted under /config.
535 source "drivers/acpi/arm64/Kconfig"