1 # SPDX-License-Identifier: GPL-2.0
6 config ARCH_SUPPORTS_ACPI
10 bool "ACPI (Advanced Configuration and Power Interface) Support"
11 depends on ARCH_SUPPORTS_ACPI
16 Advanced Configuration and Power Interface (ACPI) support for
17 Linux requires an ACPI-compliant platform (hardware/firmware),
18 and assumes the presence of OS-directed configuration and power
19 management (OSPM) software. This option will enlarge your
22 Linux ACPI provides a robust functional replacement for several
23 legacy configuration and power management interfaces, including
24 the Plug-and-Play BIOS specification (PnP BIOS), the
25 MultiProcessor Specification (MPS), and the Advanced Power
26 Management (APM) specification. If both ACPI and APM support
27 are configured, ACPI is used.
29 The project home page for the Linux ACPI subsystem is here:
30 <https://01.org/linux-acpi>
32 Linux support for ACPI is based on Intel Corporation's ACPI
33 Component Architecture (ACPI CA). For more information on the
37 ACPI is an open industry specification originally co-developed by
38 Hewlett-Packard, Intel, Microsoft, Phoenix, and Toshiba. Currently,
39 it is developed by the ACPI Specification Working Group (ASWG) under
40 the UEFI Forum and any UEFI member can join the ASWG and contribute
41 to the ACPI specification.
42 The specification is available at:
43 <http://www.acpi.info>
44 <http://www.uefi.org/acpi/specs>
48 config ACPI_LEGACY_TABLES_LOOKUP
51 config ARCH_MIGHT_HAVE_ACPI_PDC
54 config ACPI_GENERIC_GSI
57 config ACPI_SYSTEM_POWER_STATES_SUPPORT
60 config ACPI_CCA_REQUIRED
64 bool "AML debugger interface"
67 Enable in-kernel debugging of AML facilities: statistics,
68 internal object dump, single step control method execution.
69 This is still under development, currently enabling this only
70 results in the compilation of the ACPICA debugger files.
74 config ACPI_DEBUGGER_USER
75 tristate "Userspace debugger accessiblity"
78 Export /sys/kernel/debug/acpi/acpidbg for userspace utilities
79 to access the debugger functionalities.
83 config ACPI_SPCR_TABLE
84 bool "ACPI Serial Port Console Redirection Support"
87 Enable support for Serial Port Console Redirection (SPCR) Table.
88 This table provides information about the configuration of the
98 depends on SUSPEND || HIBERNATION
99 depends on ACPI_SYSTEM_POWER_STATES_SUPPORT
102 config ACPI_PROCFS_POWER
103 bool "Deprecated power /proc/acpi directories"
104 depends on X86 && PROC_FS
106 For backwards compatibility, this option allows
107 deprecated power /proc/acpi/ directories to exist, even when
108 they have been replaced by functions in /sys.
109 The deprecated directories (and their replacements) include:
110 /proc/acpi/battery/* (/sys/class/power_supply/*) and
111 /proc/acpi/ac_adapter/* (sys/class/power_supply/*).
112 This option has no effect on /proc/acpi/ directories
113 and functions which do not yet exist in /sys.
114 This option, together with the proc directories, will be
115 deleted in the future.
117 Say N to delete power /proc/acpi/ directories that have moved to /sys.
119 config ACPI_REV_OVERRIDE_POSSIBLE
120 bool "Allow supported ACPI revision to be overridden"
124 The platform firmware on some systems expects Linux to return "5" as
125 the supported ACPI revision which makes it expose system configuration
126 information in a special way.
128 For example, based on what ACPI exports as the supported revision,
129 Dell XPS 13 (2015) configures its audio device to either work in HDA
130 mode or in I2S mode, where the former is supposed to be used on Linux
131 until the latter is fully supported (in the kernel as well as in user
134 This option enables a DMI-based quirk for the above Dell machine (so
135 that HDA audio is exposed by the platform firmware to the kernel) and
136 makes it possible to force the kernel to return "5" as the supported
137 ACPI revision via the "acpi_rev_override" command line switch.
139 config ACPI_EC_DEBUGFS
140 tristate "EC read/write access through /sys/kernel/debug/ec"
142 Say N to disable Embedded Controller /sys/kernel/debug interface
144 Be aware that using this interface can confuse your Embedded
145 Controller in a way that a normal reboot is not enough. You then
146 have to power off your system, and remove the laptop battery for
148 An Embedded Controller typically is available on laptops and reads
149 sensor values like battery state and temperature.
150 The kernel accesses the EC through ACPI parsed code provided by BIOS
151 tables. This option allows to access the EC directly without ACPI
153 Thus this option is a debug option that helps to write ACPI drivers
154 and can be used to identify ACPI code or EC firmware bugs.
157 tristate "AC Adapter"
161 This driver supports the AC Adapter object, which indicates
162 whether a system is on AC or not. If you have a system that can
163 switch between A/C and battery, say Y.
165 To compile this driver as a module, choose M here:
166 the module will be called ac.
173 This driver adds support for battery information through
174 /proc/acpi/battery. If you have a mobile system with a battery,
177 To compile this driver as a module, choose M here:
178 the module will be called battery.
185 This driver handles events on the power, sleep, and lid buttons.
186 A daemon reads events from input devices or via netlink and
187 performs user-defined actions such as shutting down the system.
188 This is necessary for software-controlled poweroff.
190 To compile this driver as a module, choose M here:
191 the module will be called button.
193 config ACPI_TINY_POWER_BUTTON
194 tristate "Tiny Power Button Driver"
195 depends on !ACPI_BUTTON
197 This driver provides a tiny alternative to the ACPI Button driver.
198 The tiny power button driver only handles the power button. Rather
199 than notifying userspace via the input layer or a netlink event, this
200 driver directly signals the init process to shut down.
202 This driver is particularly suitable for cloud and VM environments,
203 which use a simulated power button to initiate a controlled poweroff,
204 but which may not want to run a separate userspace daemon to process
207 config ACPI_TINY_POWER_BUTTON_SIGNAL
208 int "Tiny Power Button Signal"
209 depends on ACPI_TINY_POWER_BUTTON
212 Default signal to send to init in response to the power button.
214 Likely values here include 38 (SIGRTMIN+4) to power off, or 2
215 (SIGINT) to simulate Ctrl+Alt+Del.
219 depends on X86 && BACKLIGHT_CLASS_DEVICE
223 This driver implements the ACPI Extensions For Display Adapters
224 for integrated graphics devices on motherboard, as specified in
225 ACPI 2.0 Specification, Appendix B. This supports basic operations
226 such as defining the video POST device, retrieving EDID information,
227 and setting up a video output.
229 To compile this driver as a module, choose M here:
230 the module will be called video.
237 This driver supports ACPI fan devices, allowing user-mode
238 applications to perform basic fan control (on, off, status).
240 To compile this driver as a module, choose M here:
241 the module will be called fan.
244 tristate "ACPI Time and Alarm (TAD) Device Support"
245 depends on SYSFS && PM_SLEEP
247 The ACPI Time and Alarm (TAD) device is an alternative to the Real
248 Time Clock (RTC). Its wake timers allow the system to transition from
249 the S3 (or optionally S4/S5) state to S0 state after a time period
250 elapses. In comparison with the RTC Alarm, the TAD provides a larger
251 scale of flexibility in the wake timers. The time capabilities of the
252 TAD maintain the time of day information across platform power
253 transitions, and keep track of time even when the platform is turned
259 This driver supports ACPI-controlled docking stations and removable
260 drive bays such as the IBM Ultrabay and the Dell Module Bay.
262 config ACPI_CPU_FREQ_PSS
266 config ACPI_PROCESSOR_CSTATE
268 depends on ACPI_PROCESSOR
269 depends on IA64 || X86
271 config ACPI_PROCESSOR_IDLE
280 depends on ACPI_PROCESSOR
284 If this option is enabled, this file implements common functionality
285 to parse CPPC tables as described in the ACPI 5.1+ spec. The
286 routines implemented are meant to be used by other
287 drivers to control CPU performance using CPPC semantics.
288 If your platform does not support CPPC in firmware,
289 leave this option disabled.
291 config ACPI_PROCESSOR
293 depends on X86 || IA64 || ARM64
294 select ACPI_PROCESSOR_IDLE
295 select ACPI_CPU_FREQ_PSS if X86 || IA64
298 This driver adds support for the ACPI Processor package. It is required
299 by several flavors of cpufreq performance-state, thermal, throttling and
302 To compile this driver as a module, choose M here:
303 the module will be called processor.
307 depends on IPMI_HANDLER
309 This driver enables the ACPI to access the BMC controller. And it
310 uses the IPMI request/response message to communicate with BMC
311 controller, which can be found on on the server.
313 To compile this driver as a module, choose M here:
314 the module will be called as acpi_ipmi.
316 config ACPI_HOTPLUG_CPU
318 depends on ACPI_PROCESSOR && HOTPLUG_CPU
319 select ACPI_CONTAINER
322 config ACPI_PROCESSOR_AGGREGATOR
323 tristate "Processor Aggregator"
324 depends on ACPI_PROCESSOR
327 ACPI 4.0 defines processor Aggregator, which enables OS to perform
328 specific processor configuration and control that applies to all
329 processors in the platform. Currently only logical processor idling
330 is defined, which is to reduce power consumption. This driver
331 supports the new device.
334 tristate "Thermal Zone"
335 depends on ACPI_PROCESSOR
339 This driver supports ACPI thermal zones. Most mobile and
340 some desktop systems support ACPI thermal zones. It is HIGHLY
341 recommended that this option be enabled, as your processor(s)
342 may be damaged without it.
344 To compile this driver as a module, choose M here:
345 the module will be called thermal.
347 config ACPI_CUSTOM_DSDT_FILE
348 string "Custom DSDT Table file to include"
350 depends on !STANDALONE
352 This option supports a custom DSDT by linking it into the kernel.
353 See Documentation/admin-guide/acpi/dsdt-override.rst
355 Enter the full path name to the file which includes the AmlCode
356 or dsdt_aml_code declaration.
358 If unsure, don't enter a file name.
360 config ACPI_CUSTOM_DSDT
362 default ACPI_CUSTOM_DSDT_FILE != ""
364 config ARCH_HAS_ACPI_TABLE_UPGRADE
367 config ACPI_TABLE_UPGRADE
368 bool "Allow upgrading ACPI tables via initrd"
369 depends on BLK_DEV_INITRD && ARCH_HAS_ACPI_TABLE_UPGRADE
372 This option provides functionality to upgrade arbitrary ACPI tables
373 via initrd. No functional change if no ACPI tables are passed via
374 initrd, therefore it's safe to say Y.
375 See Documentation/admin-guide/acpi/initrd_table_override.rst for details
377 config ACPI_TABLE_OVERRIDE_VIA_BUILTIN_INITRD
378 bool "Override ACPI tables from built-in initrd"
379 depends on ACPI_TABLE_UPGRADE
380 depends on INITRAMFS_SOURCE!="" && INITRAMFS_COMPRESSION=""
382 This option provides functionality to override arbitrary ACPI tables
383 from built-in uncompressed initrd.
385 See Documentation/admin-guide/acpi/initrd_table_override.rst for details
388 bool "Debug Statements"
390 The ACPI subsystem can produce debug output. Saying Y enables this
391 output and increases the kernel size by around 50K.
393 Use the acpi.debug_layer and acpi.debug_level kernel command-line
394 parameters documented in Documentation/firmware-guide/acpi/debug.rst and
395 Documentation/admin-guide/kernel-parameters.rst to control the type and
396 amount of debug output.
399 bool "PCI slot detection driver"
400 depends on SYSFS && PCI
402 This driver creates entries in /sys/bus/pci/slots/ for all PCI
403 slots in the system. This can help correlate PCI bus addresses,
404 i.e., segment/bus/device/function tuples, with physical slots in
405 the system. If you are unsure, say N.
407 config ACPI_CONTAINER
408 bool "Container and Module Devices"
409 default (ACPI_HOTPLUG_MEMORY || ACPI_HOTPLUG_CPU)
411 This driver supports ACPI Container and Module devices (IDs
412 ACPI0004, PNP0A05, and PNP0A06).
414 This helps support hotplug of nodes, CPUs, and memory.
416 To compile this driver as a module, choose M here:
417 the module will be called container.
419 config ACPI_HOTPLUG_MEMORY
420 bool "Memory Hotplug"
421 depends on MEMORY_HOTPLUG
423 This driver supports ACPI memory hotplug. The driver
424 fields notifications on ACPI memory devices (PNP0C80),
425 which represent memory ranges that may be onlined or
426 offlined during runtime.
428 If your hardware and firmware do not support adding or
429 removing memory devices at runtime, you need not enable
432 To compile this driver as a module, choose M here:
433 the module will be called acpi_memhotplug.
435 config ACPI_HOTPLUG_IOAPIC
438 depends on X86_IO_APIC
442 tristate "Smart Battery System"
446 This driver supports the Smart Battery System, another
447 type of access to battery information, found on some laptops.
449 To compile this driver as a module, choose M here:
450 the modules will be called sbs and sbshc.
453 tristate "Hardware Error Device"
455 This driver supports the Hardware Error Device (PNP0C33),
456 which is used to report some hardware errors notified via
457 SCI, mainly the corrected errors.
459 config ACPI_CUSTOM_METHOD
460 tristate "Allow ACPI methods to be inserted/replaced at run time"
463 This debug facility allows ACPI AML methods to be inserted and/or
464 replaced without rebooting the system. For details refer to:
465 Documentation/firmware-guide/acpi/method-customizing.rst.
467 NOTE: This option is security sensitive, because it allows arbitrary
468 kernel memory to be written to by root (uid=0) users, allowing them
469 to bypass certain security measures (e.g. if root is not allowed to
470 load additional kernel modules after boot, this feature may be used
471 to override that restriction).
474 bool "Boottime Graphics Resource Table support"
475 depends on EFI && (X86 || ARM64)
477 This driver adds support for exposing the ACPI Boottime Graphics
478 Resource Table, which allows the operating system to obtain
479 data from the firmware boot splash. It will appear under
480 /sys/firmware/acpi/bgrt/ .
482 config ACPI_REDUCED_HARDWARE_ONLY
483 bool "Hardware-reduced ACPI support only" if EXPERT
486 This config item changes the way the ACPI code is built. When this
487 option is selected, the kernel will use a specialized version of
488 ACPICA that ONLY supports the ACPI "reduced hardware" mode. The
489 resulting kernel will be smaller but it will also be restricted to
490 running in ACPI reduced hardware mode ONLY.
492 If you are unsure what to do, do not enable this option.
494 source "drivers/acpi/nfit/Kconfig"
495 source "drivers/acpi/numa/Kconfig"
496 source "drivers/acpi/apei/Kconfig"
497 source "drivers/acpi/dptf/Kconfig"
503 tristate "Extended Error Log support"
504 depends on X86_MCE && X86_LOCAL_APIC && EDAC
507 Certain usages such as Predictive Failure Analysis (PFA) require
508 more information about the error than what can be described in
509 processor machine check banks. Most server processors log
510 additional information about the error in processor uncore
511 registers. Since the addresses and layout of these registers vary
512 widely from one processor to another, system software cannot
513 readily make use of them. To complicate matters further, some of
514 the additional error information cannot be constructed without
515 detailed knowledge about platform topology.
517 Enhanced MCA Logging allows firmware to provide additional error
518 information to system software, synchronous with MCE or CMCI. This
519 driver adds support for that functionality with corresponding
520 tracepoint which carries that information to userspace.
525 menuconfig PMIC_OPREGION
526 bool "PMIC (Power Management Integrated Circuit) operation region support"
528 Select this option to enable support for ACPI operation
529 region of the PMIC chip. The operation region can be used
530 to control power rails and sensor reading/writing on the
534 config BYTCRC_PMIC_OPREGION
535 bool "ACPI operation region support for Bay Trail Crystal Cove PMIC"
536 depends on INTEL_SOC_PMIC
538 This config adds ACPI operation region support for the Bay Trail
539 version of the Crystal Cove PMIC.
541 config CHTCRC_PMIC_OPREGION
542 bool "ACPI operation region support for Cherry Trail Crystal Cove PMIC"
543 depends on INTEL_SOC_PMIC
545 This config adds ACPI operation region support for the Cherry Trail
546 version of the Crystal Cove PMIC.
548 config XPOWER_PMIC_OPREGION
549 bool "ACPI operation region support for XPower AXP288 PMIC"
550 depends on MFD_AXP20X_I2C && IOSF_MBI=y
552 This config adds ACPI operation region support for XPower AXP288 PMIC.
554 config BXT_WC_PMIC_OPREGION
555 bool "ACPI operation region support for BXT WhiskeyCove PMIC"
556 depends on INTEL_SOC_PMIC_BXTWC
558 This config adds ACPI operation region support for BXT WhiskeyCove PMIC.
560 config CHT_WC_PMIC_OPREGION
561 bool "ACPI operation region support for CHT Whiskey Cove PMIC"
562 depends on INTEL_SOC_PMIC_CHTWC
564 This config adds ACPI operation region support for CHT Whiskey Cove PMIC.
566 config CHT_DC_TI_PMIC_OPREGION
567 bool "ACPI operation region support for Dollar Cove TI PMIC"
568 depends on INTEL_SOC_PMIC_CHTDC_TI
570 This config adds ACPI operation region support for Dollar Cove TI PMIC.
575 tristate "ACPI configfs support"
578 Select this option to enable support for ACPI configuration from
579 userspace. The configurable ACPI groups will be visible under
580 /config/acpi, assuming configfs is mounted under /config.
583 source "drivers/acpi/arm64/Kconfig"
589 config TPS68470_PMIC_OPREGION
590 bool "ACPI operation region support for TPS68470 PMIC"
591 depends on MFD_TPS68470
593 This config adds ACPI operation region support for TI TPS68470 PMIC.
594 TPS68470 device is an advanced power management unit that powers
595 a Compact Camera Module (CCM), generates clocks for image sensors,
596 drives a dual LED for flash and incorporates two LED drivers for
597 general purpose indicators.
598 This driver enables ACPI operation region support control voltage
599 regulators and clocks.
601 This option is a bool as it provides an ACPI operation
602 region, which must be available before any of the devices
603 using this, are probed.
608 bool "Power Management Timer Support" if EXPERT
609 depends on X86 && (ACPI || JAILHOUSE_GUEST)
612 The Power Management Timer is available on all ACPI-capable,
613 in most cases even if ACPI is unusable or blacklisted.
615 This timing source is not affected by power management features
616 like aggressive processor idling, throttling, frequency and/or
617 voltage scaling, unlike the commonly used Time Stamp Counter
620 You should nearly always say Y here because many modern
621 systems require this timer.