1 # SPDX-License-Identifier: GPL-2.0
7 bool "ACPI (Advanced Configuration and Power Interface) Support"
8 depends on !IA64_HP_SIM
9 depends on IA64 || X86 || ARM64
12 default y if (IA64 || X86)
14 Advanced Configuration and Power Interface (ACPI) support for
15 Linux requires an ACPI-compliant platform (hardware/firmware),
16 and assumes the presence of OS-directed configuration and power
17 management (OSPM) software. This option will enlarge your
20 Linux ACPI provides a robust functional replacement for several
21 legacy configuration and power management interfaces, including
22 the Plug-and-Play BIOS specification (PnP BIOS), the
23 MultiProcessor Specification (MPS), and the Advanced Power
24 Management (APM) specification. If both ACPI and APM support
25 are configured, ACPI is used.
27 The project home page for the Linux ACPI subsystem is here:
28 <https://01.org/linux-acpi>
30 Linux support for ACPI is based on Intel Corporation's ACPI
31 Component Architecture (ACPI CA). For more information on the
35 ACPI is an open industry specification originally co-developed by
36 Hewlett-Packard, Intel, Microsoft, Phoenix, and Toshiba. Currently,
37 it is developed by the ACPI Specification Working Group (ASWG) under
38 the UEFI Forum and any UEFI member can join the ASWG and contribute
39 to the ACPI specification.
40 The specification is available at:
41 <http://www.acpi.info>
42 <http://www.uefi.org/acpi/specs>
46 config ACPI_LEGACY_TABLES_LOOKUP
49 config ARCH_MIGHT_HAVE_ACPI_PDC
52 config ACPI_GENERIC_GSI
55 config ACPI_SYSTEM_POWER_STATES_SUPPORT
58 config ACPI_CCA_REQUIRED
62 bool "AML debugger interface"
65 Enable in-kernel debugging of AML facilities: statistics,
66 internal object dump, single step control method execution.
67 This is still under development, currently enabling this only
68 results in the compilation of the ACPICA debugger files.
72 config ACPI_DEBUGGER_USER
73 tristate "Userspace debugger accessiblity"
76 Export /sys/kernel/debug/acpi/acpidbg for userspace utilities
77 to access the debugger functionalities.
81 config ACPI_SPCR_TABLE
91 depends on SUSPEND || HIBERNATION
92 depends on ACPI_SYSTEM_POWER_STATES_SUPPORT
95 config ACPI_PROCFS_POWER
96 bool "Deprecated power /proc/acpi directories"
97 depends on X86 && PROC_FS
99 For backwards compatibility, this option allows
100 deprecated power /proc/acpi/ directories to exist, even when
101 they have been replaced by functions in /sys.
102 The deprecated directories (and their replacements) include:
103 /proc/acpi/battery/* (/sys/class/power_supply/*)
104 /proc/acpi/ac_adapter/* (sys/class/power_supply/*)
105 This option has no effect on /proc/acpi/ directories
106 and functions, which do not yet exist in /sys
107 This option, together with the proc directories, will be
108 deleted in the future.
110 Say N to delete power /proc/acpi/ directories that have moved to /sys/
112 config ACPI_REV_OVERRIDE_POSSIBLE
113 bool "Allow supported ACPI revision to be overridden"
117 The platform firmware on some systems expects Linux to return "5" as
118 the supported ACPI revision which makes it expose system configuration
119 information in a special way.
121 For example, based on what ACPI exports as the supported revision,
122 Dell XPS 13 (2015) configures its audio device to either work in HDA
123 mode or in I2S mode, where the former is supposed to be used on Linux
124 until the latter is fully supported (in the kernel as well as in user
127 This option enables a DMI-based quirk for the above Dell machine (so
128 that HDA audio is exposed by the platform firmware to the kernel) and
129 makes it possible to force the kernel to return "5" as the supported
130 ACPI revision via the "acpi_rev_override" command line switch.
132 config ACPI_EC_DEBUGFS
133 tristate "EC read/write access through /sys/kernel/debug/ec"
136 Say N to disable Embedded Controller /sys/kernel/debug interface
138 Be aware that using this interface can confuse your Embedded
139 Controller in a way that a normal reboot is not enough. You then
140 have to power off your system, and remove the laptop battery for
142 An Embedded Controller typically is available on laptops and reads
143 sensor values like battery state and temperature.
144 The kernel accesses the EC through ACPI parsed code provided by BIOS
145 tables. This option allows to access the EC directly without ACPI
147 Thus this option is a debug option that helps to write ACPI drivers
148 and can be used to identify ACPI code or EC firmware bugs.
151 tristate "AC Adapter"
156 This driver supports the AC Adapter object, which indicates
157 whether a system is on AC or not. If you have a system that can
158 switch between A/C and battery, say Y.
160 To compile this driver as a module, choose M here:
161 the module will be called ac.
169 This driver adds support for battery information through
170 /proc/acpi/battery. If you have a mobile system with a battery,
173 To compile this driver as a module, choose M here:
174 the module will be called battery.
181 This driver handles events on the power, sleep, and lid buttons.
182 A daemon reads events from input devices or via netlink and
183 performs user-defined actions such as shutting down the system.
184 This is necessary for software-controlled poweroff.
186 To compile this driver as a module, choose M here:
187 the module will be called button.
191 depends on X86 && BACKLIGHT_CLASS_DEVICE
195 This driver implements the ACPI Extensions For Display Adapters
196 for integrated graphics devices on motherboard, as specified in
197 ACPI 2.0 Specification, Appendix B. This supports basic operations
198 such as defining the video POST device, retrieving EDID information,
199 and setting up a video output.
201 To compile this driver as a module, choose M here:
202 the module will be called video.
209 This driver supports ACPI fan devices, allowing user-mode
210 applications to perform basic fan control (on, off, status).
212 To compile this driver as a module, choose M here:
213 the module will be called fan.
218 This driver supports ACPI-controlled docking stations and removable
219 drive bays such as the IBM Ultrabay and the Dell Module Bay.
221 config ACPI_CPU_FREQ_PSS
225 config ACPI_PROCESSOR_CSTATE
227 depends on IA64 || X86
229 config ACPI_PROCESSOR_IDLE
238 depends on ACPI_PROCESSOR
242 If this option is enabled, this file implements common functionality
243 to parse CPPC tables as described in the ACPI 5.1+ spec. The
244 routines implemented are meant to be used by other
245 drivers to control CPU performance using CPPC semantics.
246 If your platform does not support CPPC in firmware,
247 leave this option disabled.
249 config ACPI_PROCESSOR
251 depends on X86 || IA64 || ARM64
252 select ACPI_PROCESSOR_IDLE
253 select ACPI_CPU_FREQ_PSS if X86 || IA64
256 This driver adds support for the ACPI Processor package. It is required
257 by several flavors of cpufreq performance-state, thermal, throttling and
260 To compile this driver as a module, choose M here:
261 the module will be called processor.
265 depends on IPMI_HANDLER
268 This driver enables the ACPI to access the BMC controller. And it
269 uses the IPMI request/response message to communicate with BMC
270 controller, which can be found on on the server.
272 To compile this driver as a module, choose M here:
273 the module will be called as acpi_ipmi.
275 config ACPI_HOTPLUG_CPU
277 depends on ACPI_PROCESSOR && HOTPLUG_CPU
278 select ACPI_CONTAINER
281 config ACPI_PROCESSOR_AGGREGATOR
282 tristate "Processor Aggregator"
283 depends on ACPI_PROCESSOR
286 ACPI 4.0 defines processor Aggregator, which enables OS to perform
287 specific processor configuration and control that applies to all
288 processors in the platform. Currently only logical processor idling
289 is defined, which is to reduce power consumption. This driver
290 supports the new device.
293 tristate "Thermal Zone"
294 depends on ACPI_PROCESSOR
298 This driver supports ACPI thermal zones. Most mobile and
299 some desktop systems support ACPI thermal zones. It is HIGHLY
300 recommended that this option be enabled, as your processor(s)
301 may be damaged without it.
303 To compile this driver as a module, choose M here:
304 the module will be called thermal.
309 depends on (X86 || IA64 || ARM64)
310 default y if IA64_GENERIC || IA64_SGI_SN2 || ARM64
312 config ACPI_CUSTOM_DSDT_FILE
313 string "Custom DSDT Table file to include"
315 depends on !STANDALONE
317 This option supports a custom DSDT by linking it into the kernel.
318 See Documentation/acpi/dsdt-override.txt
320 Enter the full path name to the file which includes the AmlCode
323 If unsure, don't enter a file name.
325 config ACPI_CUSTOM_DSDT
327 default ACPI_CUSTOM_DSDT_FILE != ""
329 config ARCH_HAS_ACPI_TABLE_UPGRADE
332 config ACPI_TABLE_UPGRADE
333 bool "Allow upgrading ACPI tables via initrd"
334 depends on BLK_DEV_INITRD && ARCH_HAS_ACPI_TABLE_UPGRADE
337 This option provides functionality to upgrade arbitrary ACPI tables
338 via initrd. No functional change if no ACPI tables are passed via
339 initrd, therefore it's safe to say Y.
340 See Documentation/acpi/initrd_table_override.txt for details
343 bool "Debug Statements"
346 The ACPI subsystem can produce debug output. Saying Y enables this
347 output and increases the kernel size by around 50K.
349 Use the acpi.debug_layer and acpi.debug_level kernel command-line
350 parameters documented in Documentation/acpi/debug.txt and
351 Documentation/admin-guide/kernel-parameters.rst to control the type and
352 amount of debug output.
355 bool "PCI slot detection driver"
359 This driver creates entries in /sys/bus/pci/slots/ for all PCI
360 slots in the system. This can help correlate PCI bus addresses,
361 i.e., segment/bus/device/function tuples, with physical slots in
362 the system. If you are unsure, say N.
364 config ACPI_CONTAINER
365 bool "Container and Module Devices"
366 default (ACPI_HOTPLUG_MEMORY || ACPI_HOTPLUG_CPU)
368 This driver supports ACPI Container and Module devices (IDs
369 ACPI0004, PNP0A05, and PNP0A06).
371 This helps support hotplug of nodes, CPUs, and memory.
373 To compile this driver as a module, choose M here:
374 the module will be called container.
376 config ACPI_HOTPLUG_MEMORY
377 bool "Memory Hotplug"
378 depends on MEMORY_HOTPLUG
380 This driver supports ACPI memory hotplug. The driver
381 fields notifications on ACPI memory devices (PNP0C80),
382 which represent memory ranges that may be onlined or
383 offlined during runtime.
385 If your hardware and firmware do not support adding or
386 removing memory devices at runtime, you need not enable
389 To compile this driver as a module, choose M here:
390 the module will be called acpi_memhotplug.
392 config ACPI_HOTPLUG_IOAPIC
395 depends on X86_IO_APIC
399 tristate "Smart Battery System"
403 This driver supports the Smart Battery System, another
404 type of access to battery information, found on some laptops.
406 To compile this driver as a module, choose M here:
407 the modules will be called sbs and sbshc.
410 tristate "Hardware Error Device"
412 This driver supports the Hardware Error Device (PNP0C33),
413 which is used to report some hardware errors notified via
414 SCI, mainly the corrected errors.
416 config ACPI_CUSTOM_METHOD
417 tristate "Allow ACPI methods to be inserted/replaced at run time"
421 This debug facility allows ACPI AML methods to be inserted and/or
422 replaced without rebooting the system. For details refer to:
423 Documentation/acpi/method-customizing.txt.
425 NOTE: This option is security sensitive, because it allows arbitrary
426 kernel memory to be written to by root (uid=0) users, allowing them
427 to bypass certain security measures (e.g. if root is not allowed to
428 load additional kernel modules after boot, this feature may be used
429 to override that restriction).
432 bool "Boottime Graphics Resource Table support"
433 depends on EFI && (X86 || ARM64)
435 This driver adds support for exposing the ACPI Boottime Graphics
436 Resource Table, which allows the operating system to obtain
437 data from the firmware boot splash. It will appear under
438 /sys/firmware/acpi/bgrt/ .
440 config ACPI_REDUCED_HARDWARE_ONLY
441 bool "Hardware-reduced ACPI support only" if EXPERT
444 This config item changes the way the ACPI code is built. When this
445 option is selected, the kernel will use a specialized version of
446 ACPICA that ONLY supports the ACPI "reduced hardware" mode. The
447 resulting kernel will be smaller but it will also be restricted to
448 running in ACPI reduced hardware mode ONLY.
450 If you are unsure what to do, do not enable this option.
452 source "drivers/acpi/nfit/Kconfig"
454 source "drivers/acpi/apei/Kconfig"
455 source "drivers/acpi/dptf/Kconfig"
461 tristate "Extended Error Log support"
462 depends on X86_MCE && X86_LOCAL_APIC && EDAC
466 Certain usages such as Predictive Failure Analysis (PFA) require
467 more information about the error than what can be described in
468 processor machine check banks. Most server processors log
469 additional information about the error in processor uncore
470 registers. Since the addresses and layout of these registers vary
471 widely from one processor to another, system software cannot
472 readily make use of them. To complicate matters further, some of
473 the additional error information cannot be constructed without
474 detailed knowledge about platform topology.
476 Enhanced MCA Logging allows firmware to provide additional error
477 information to system software, synchronous with MCE or CMCI. This
478 driver adds support for that functionality with corresponding
479 tracepoint which carries that information to userspace.
481 menuconfig PMIC_OPREGION
482 bool "PMIC (Power Management Integrated Circuit) operation region support"
484 Select this option to enable support for ACPI operation
485 region of the PMIC chip. The operation region can be used
486 to control power rails and sensor reading/writing on the
490 config CRC_PMIC_OPREGION
491 bool "ACPI operation region support for CrystalCove PMIC"
492 depends on INTEL_SOC_PMIC
494 This config adds ACPI operation region support for CrystalCove PMIC.
496 config XPOWER_PMIC_OPREGION
497 bool "ACPI operation region support for XPower AXP288 PMIC"
498 depends on MFD_AXP20X_I2C
500 This config adds ACPI operation region support for XPower AXP288 PMIC.
502 config BXT_WC_PMIC_OPREGION
503 bool "ACPI operation region support for BXT WhiskeyCove PMIC"
504 depends on INTEL_SOC_PMIC_BXTWC
506 This config adds ACPI operation region support for BXT WhiskeyCove PMIC.
508 config CHT_WC_PMIC_OPREGION
509 bool "ACPI operation region support for CHT Whiskey Cove PMIC"
510 depends on INTEL_SOC_PMIC_CHTWC
512 This config adds ACPI operation region support for CHT Whiskey Cove PMIC.
514 config CHT_DC_TI_PMIC_OPREGION
515 bool "ACPI operation region support for Dollar Cove TI PMIC"
516 depends on INTEL_SOC_PMIC_CHTDC_TI
518 This config adds ACPI operation region support for Dollar Cove TI PMIC.
523 tristate "ACPI configfs support"
526 Select this option to enable support for ACPI configuration from
527 userspace. The configurable ACPI groups will be visible under
528 /config/acpi, assuming configfs is mounted under /config.
531 source "drivers/acpi/arm64/Kconfig"
534 config TPS68470_PMIC_OPREGION
535 bool "ACPI operation region support for TPS68470 PMIC"
536 depends on MFD_TPS68470
538 This config adds ACPI operation region support for TI TPS68470 PMIC.
539 TPS68470 device is an advanced power management unit that powers
540 a Compact Camera Module (CCM), generates clocks for image sensors,
541 drives a dual LED for flash and incorporates two LED drivers for
542 general purpose indicators.
543 This driver enables ACPI operation region support control voltage
544 regulators and clocks.
546 This option is a bool as it provides an ACPI operation
547 region, which must be available before any of the devices
548 using this, are probed.
553 bool "Power Management Timer Support" if EXPERT
554 depends on X86 && (ACPI || JAILHOUSE_GUEST)
557 The Power Management Timer is available on all ACPI-capable,
558 in most cases even if ACPI is unusable or blacklisted.
560 This timing source is not affected by power management features
561 like aggressive processor idling, throttling, frequency and/or
562 voltage scaling, unlike the commonly used Time Stamp Counter
565 You should nearly always say Y here because many modern
566 systems require this timer.