607 lines · plain
1# SPDX-License-Identifier: GPL-2.02#3# ACPI Configuration4#5 6config ARCH_SUPPORTS_ACPI7 bool8 9menuconfig ACPI10 bool "ACPI (Advanced Configuration and Power Interface) Support"11 depends on ARCH_SUPPORTS_ACPI12 select PNP13 select NLS14 select CRC3215 select FIRMWARE_TABLE16 default y if X8617 help18 Advanced Configuration and Power Interface (ACPI) support for 19 Linux requires an ACPI-compliant platform (hardware/firmware),20 and assumes the presence of OS-directed configuration and power21 management (OSPM) software. This option will enlarge your 22 kernel by about 70K.23 24 Linux ACPI provides a robust functional replacement for several 25 legacy configuration and power management interfaces, including26 the Plug-and-Play BIOS specification (PnP BIOS), the 27 MultiProcessor Specification (MPS), and the Advanced Power 28 Management (APM) specification. If both ACPI and APM support 29 are configured, ACPI is used.30 31 Linux support for ACPI is based on Intel Corporation's ACPI32 Component Architecture (ACPI CA). For more information on the33 ACPI CA, see:34 <https://acpica.org/>35 36 ACPI is an open industry specification originally co-developed by37 Hewlett-Packard, Intel, Microsoft, Phoenix, and Toshiba. Currently,38 it is developed by the ACPI Specification Working Group (ASWG) under39 the UEFI Forum and any UEFI member can join the ASWG and contribute40 to the ACPI specification.41 The specification is available at:42 <https://uefi.org/specifications>43 44if ACPI45 46config ACPI_LEGACY_TABLES_LOOKUP47 bool48 49config ARCH_MIGHT_HAVE_ACPI_PDC50 bool51 52config ACPI_GENERIC_GSI53 bool54 55config ACPI_SYSTEM_POWER_STATES_SUPPORT56 bool57 58config ACPI_CCA_REQUIRED59 bool60 61config ACPI_TABLE_LIB62 bool63 64config ACPI_THERMAL_LIB65 depends on THERMAL66 bool67 68config ACPI_DEBUGGER69 bool "AML debugger interface"70 select ACPI_DEBUG71 help72 Enable in-kernel debugging of AML facilities: statistics,73 internal object dump, single step control method execution.74 This is still under development, currently enabling this only75 results in the compilation of the ACPICA debugger files.76 77if ACPI_DEBUGGER78 79config ACPI_DEBUGGER_USER80 tristate "Userspace debugger accessibility"81 depends on DEBUG_FS82 help83 Export /sys/kernel/debug/acpi/acpidbg for userspace utilities84 to access the debugger functionalities.85 86endif87 88config ACPI_SPCR_TABLE89 bool "ACPI Serial Port Console Redirection Support"90 default y if X8691 help92 Enable support for Serial Port Console Redirection (SPCR) Table.93 This table provides information about the configuration of the94 earlycon console.95 96config ACPI_FPDT97 bool "ACPI Firmware Performance Data Table (FPDT) support"98 depends on X86_64 || ARM6499 help100 Enable support for the Firmware Performance Data Table (FPDT).101 This table provides information on the timing of the system102 boot, S3 suspend and S3 resume firmware code paths.103 104config ACPI_LPIT105 bool106 depends on X86_64107 default y108 109config ACPI_SLEEP110 bool111 depends on SUSPEND || HIBERNATION112 depends on ACPI_SYSTEM_POWER_STATES_SUPPORT113 default y114 115config ACPI_REV_OVERRIDE_POSSIBLE116 bool "Allow supported ACPI revision to be overridden"117 depends on X86118 default y119 help120 The platform firmware on some systems expects Linux to return "5" as121 the supported ACPI revision which makes it expose system configuration122 information in a special way.123 124 For example, based on what ACPI exports as the supported revision,125 Dell XPS 13 (2015) configures its audio device to either work in HDA126 mode or in I2S mode, where the former is supposed to be used on Linux127 until the latter is fully supported (in the kernel as well as in user128 space).129 130 This option enables a DMI-based quirk for the above Dell machine (so131 that HDA audio is exposed by the platform firmware to the kernel) and132 makes it possible to force the kernel to return "5" as the supported133 ACPI revision via the "acpi_rev_override" command line switch.134 135config ACPI_EC_DEBUGFS136 tristate "EC read/write access through /sys/kernel/debug/ec"137 help138 Say N to disable Embedded Controller /sys/kernel/debug interface139 140 Be aware that using this interface can confuse your Embedded141 Controller in a way that a normal reboot is not enough. You then142 have to power off your system, and remove the laptop battery for143 some seconds.144 An Embedded Controller typically is available on laptops and reads145 sensor values like battery state and temperature.146 The kernel accesses the EC through ACPI parsed code provided by BIOS147 tables. This option allows to access the EC directly without ACPI148 code being involved.149 Thus this option is a debug option that helps to write ACPI drivers150 and can be used to identify ACPI code or EC firmware bugs.151 152config ACPI_AC153 tristate "AC Adapter"154 select POWER_SUPPLY155 default y156 help157 This driver supports the AC Adapter object, which indicates158 whether a system is on AC or not. If you have a system that can159 switch between A/C and battery, say Y.160 161 To compile this driver as a module, choose M here:162 the module will be called ac.163 164config ACPI_BATTERY165 tristate "Battery"166 select POWER_SUPPLY167 default y168 help169 This driver adds support for battery information through170 /proc/acpi/battery. If you have a mobile system with a battery, 171 say Y.172 173 To compile this driver as a module, choose M here:174 the module will be called battery.175 176config ACPI_BUTTON177 tristate "Button"178 depends on INPUT179 default y180 help181 This driver handles events on the power, sleep, and lid buttons.182 A daemon reads events from input devices or via netlink and183 performs user-defined actions such as shutting down the system.184 This is necessary for software-controlled poweroff.185 186 To compile this driver as a module, choose M here:187 the module will be called button.188 189config ACPI_TINY_POWER_BUTTON190 tristate "Tiny Power Button Driver"191 depends on !ACPI_BUTTON192 help193 This driver provides a tiny alternative to the ACPI Button driver.194 The tiny power button driver only handles the power button. Rather195 than notifying userspace via the input layer or a netlink event, this196 driver directly signals the init process to shut down.197 198 This driver is particularly suitable for cloud and VM environments,199 which use a simulated power button to initiate a controlled poweroff,200 but which may not want to run a separate userspace daemon to process201 input events.202 203config ACPI_TINY_POWER_BUTTON_SIGNAL204 int "Tiny Power Button Signal"205 depends on ACPI_TINY_POWER_BUTTON206 default 38207 help208 Default signal to send to init in response to the power button.209 210 Likely values here include 38 (SIGRTMIN+4) to power off, or 2211 (SIGINT) to simulate Ctrl+Alt+Del.212 213config ACPI_VIDEO214 tristate "Video"215 depends on BACKLIGHT_CLASS_DEVICE216 depends on INPUT217 depends on ACPI_WMI || !X86218 select THERMAL219 help220 This driver implements the ACPI Extensions For Display Adapters221 for integrated graphics devices on motherboard, as specified in222 ACPI 2.0 Specification, Appendix B. This supports basic operations223 such as defining the video POST device, retrieving EDID information,224 and setting up a video output.225 226 To compile this driver as a module, choose M here:227 the module will be called video.228 229config ACPI_FAN230 tristate "Fan"231 depends on THERMAL232 default y233 help234 This driver supports ACPI fan devices, allowing user-mode235 applications to perform basic fan control (on, off, status).236 237 To compile this driver as a module, choose M here:238 the module will be called fan.239 240config ACPI_TAD241 tristate "ACPI Time and Alarm (TAD) Device Support"242 depends on SYSFS && PM_SLEEP243 help244 The ACPI Time and Alarm (TAD) device is an alternative to the Real245 Time Clock (RTC). Its wake timers allow the system to transition from246 the S3 (or optionally S4/S5) state to S0 state after a time period247 elapses. In comparison with the RTC Alarm, the TAD provides a larger248 scale of flexibility in the wake timers. The time capabilities of the249 TAD maintain the time of day information across platform power250 transitions, and keep track of time even when the platform is turned251 off.252 253config ACPI_DOCK254 bool "Dock"255 help256 This driver supports ACPI-controlled docking stations and removable257 drive bays such as the IBM Ultrabay and the Dell Module Bay.258 259config ACPI_CPU_FREQ_PSS260 bool261 262config ACPI_PROCESSOR_CSTATE263 def_bool y264 depends on ACPI_PROCESSOR265 depends on X86266 267config ACPI_PROCESSOR_IDLE268 bool269 select CPU_IDLE270 271config ACPI_MCFG272 bool273 274config ACPI_CPPC_LIB275 bool276 depends on ACPI_PROCESSOR277 select MAILBOX278 select PCC279 help280 If this option is enabled, this file implements common functionality281 to parse CPPC tables as described in the ACPI 5.1+ spec. The282 routines implemented are meant to be used by other283 drivers to control CPU performance using CPPC semantics.284 If your platform does not support CPPC in firmware,285 leave this option disabled.286 287config ACPI_PROCESSOR288 tristate "Processor"289 depends on X86 || ARM64 || LOONGARCH || RISCV290 select ACPI_PROCESSOR_IDLE291 select ACPI_CPU_FREQ_PSS if X86 || LOONGARCH292 select THERMAL293 default y294 help295 This driver adds support for the ACPI Processor package. It is required296 by several flavors of cpufreq performance-state, thermal, throttling and297 idle drivers.298 299 To compile this driver as a module, choose M here:300 the module will be called processor.301 302config ACPI_IPMI303 tristate "IPMI"304 depends on IPMI_HANDLER305 help306 This driver enables the ACPI to access the BMC controller. And it307 uses the IPMI request/response message to communicate with BMC308 controller, which can be found on the server.309 310 To compile this driver as a module, choose M here:311 the module will be called as acpi_ipmi.312 313config ACPI_HOTPLUG_CPU314 bool315 depends on ACPI_PROCESSOR && HOTPLUG_CPU316 select ACPI_CONTAINER317 318config ACPI_PROCESSOR_AGGREGATOR319 tristate "Processor Aggregator"320 depends on ACPI_PROCESSOR321 depends on X86322 help323 ACPI 4.0 defines processor Aggregator, which enables OS to perform324 specific processor configuration and control that applies to all325 processors in the platform. Currently only logical processor idling326 is defined, which is to reduce power consumption. This driver327 supports the new device.328 329config ACPI_THERMAL330 tristate "Thermal Zone"331 depends on ACPI_PROCESSOR332 select THERMAL333 select ACPI_THERMAL_LIB334 default y335 help336 This driver supports ACPI thermal zones. Most mobile and337 some desktop systems support ACPI thermal zones. It is HIGHLY338 recommended that this option be enabled, as your processor(s)339 may be damaged without it.340 341 To compile this driver as a module, choose M here:342 the module will be called thermal.343 344config ACPI_PLATFORM_PROFILE345 tristate346 347config ACPI_CUSTOM_DSDT_FILE348 string "Custom DSDT Table file to include"349 default ""350 depends on !STANDALONE351 help352 This option supports a custom DSDT by linking it into the kernel.353 354 Enter the full path name to the file which includes the AmlCode355 or dsdt_aml_code declaration.356 357 If unsure, don't enter a file name.358 359config ACPI_CUSTOM_DSDT360 bool361 default ACPI_CUSTOM_DSDT_FILE != ""362 363config ARCH_HAS_ACPI_TABLE_UPGRADE364 def_bool n365 366config ACPI_TABLE_UPGRADE367 bool "Allow upgrading ACPI tables via initrd"368 depends on BLK_DEV_INITRD && ARCH_HAS_ACPI_TABLE_UPGRADE369 default y370 help371 This option provides functionality to upgrade arbitrary ACPI tables372 via initrd. No functional change if no ACPI tables are passed via373 initrd, therefore it's safe to say Y.374 See Documentation/admin-guide/acpi/initrd_table_override.rst for details375 376config ACPI_TABLE_OVERRIDE_VIA_BUILTIN_INITRD377 bool "Override ACPI tables from built-in initrd"378 depends on ACPI_TABLE_UPGRADE379 depends on INITRAMFS_SOURCE!="" && INITRAMFS_COMPRESSION_NONE380 help381 This option provides functionality to override arbitrary ACPI tables382 from built-in uncompressed initrd.383 384 See Documentation/admin-guide/acpi/initrd_table_override.rst for details385 386config ACPI_DEBUG387 bool "Debug Statements"388 help389 The ACPI subsystem can produce debug output. Saying Y enables this390 output and increases the kernel size by around 50K.391 392 Use the acpi.debug_layer and acpi.debug_level kernel command-line393 parameters documented in Documentation/firmware-guide/acpi/debug.rst and394 Documentation/admin-guide/kernel-parameters.rst to control the type and395 amount of debug output.396 397config ACPI_PCI_SLOT398 bool "PCI slot detection driver"399 depends on SYSFS && PCI400 help401 This driver creates entries in /sys/bus/pci/slots/ for all PCI402 slots in the system. This can help correlate PCI bus addresses,403 i.e., segment/bus/device/function tuples, with physical slots in404 the system. If you are unsure, say N.405 406config ACPI_CONTAINER407 bool "Container and Module Devices"408 default (ACPI_HOTPLUG_MEMORY || ACPI_HOTPLUG_CPU)409 help410 This driver supports ACPI Container and Module devices (IDs411 ACPI0004, PNP0A05, and PNP0A06).412 413 This helps support hotplug of nodes, CPUs, and memory.414 415config ACPI_HOTPLUG_MEMORY416 bool "Memory Hotplug"417 depends on MEMORY_HOTPLUG418 help419 This driver supports ACPI memory hotplug. The driver420 fields notifications on ACPI memory devices (PNP0C80),421 which represent memory ranges that may be onlined or422 offlined during runtime.423 424 If your hardware and firmware do not support adding or425 removing memory devices at runtime, you need not enable426 this driver.427 428config ACPI_HOTPLUG_IOAPIC429 bool430 depends on PCI431 depends on X86_IO_APIC432 default y433 434config ACPI_SBS435 tristate "Smart Battery System"436 depends on X86437 select POWER_SUPPLY438 help439 This driver supports the Smart Battery System, another440 type of access to battery information, found on some laptops.441 442 To compile this driver as a module, choose M here:443 the modules will be called sbs and sbshc.444 445config ACPI_HED446 tristate "Hardware Error Device"447 help448 This driver supports the Hardware Error Device (PNP0C33),449 which is used to report some hardware errors notified via450 SCI, mainly the corrected errors.451 452config ACPI_BGRT453 bool "Boottime Graphics Resource Table support"454 depends on EFI && (X86 || ARM64 || LOONGARCH)455 help456 This driver adds support for exposing the ACPI Boottime Graphics457 Resource Table, which allows the operating system to obtain458 data from the firmware boot splash. It will appear under459 /sys/firmware/acpi/bgrt/ .460 461config ACPI_REDUCED_HARDWARE_ONLY462 bool "Hardware-reduced ACPI support only" if EXPERT463 help464 This config item changes the way the ACPI code is built. When this465 option is selected, the kernel will use a specialized version of466 ACPICA that ONLY supports the ACPI "reduced hardware" mode. The467 resulting kernel will be smaller but it will also be restricted to468 running in ACPI reduced hardware mode ONLY.469 470 If you are unsure what to do, do not enable this option.471 472config ACPI_NHLT473 bool474 475source "drivers/acpi/nfit/Kconfig"476source "drivers/acpi/numa/Kconfig"477source "drivers/acpi/apei/Kconfig"478source "drivers/acpi/dptf/Kconfig"479 480config ACPI_WATCHDOG481 bool482 483config ACPI_EXTLOG484 tristate "Extended Error Log support"485 depends on X86_MCE && X86_LOCAL_APIC && EDAC486 select UEFI_CPER487 help488 Certain usages such as Predictive Failure Analysis (PFA) require489 more information about the error than what can be described in490 processor machine check banks. Most server processors log491 additional information about the error in processor uncore492 registers. Since the addresses and layout of these registers vary493 widely from one processor to another, system software cannot494 readily make use of them. To complicate matters further, some of495 the additional error information cannot be constructed without496 detailed knowledge about platform topology.497 498 Enhanced MCA Logging allows firmware to provide additional error499 information to system software, synchronous with MCE or CMCI. This500 driver adds support for that functionality with corresponding501 tracepoint which carries that information to userspace.502 503config ACPI_ADXL504 bool505 506config ACPI_CONFIGFS507 tristate "ACPI configfs support"508 select CONFIGFS_FS509 help510 Select this option to enable support for ACPI configuration from511 userspace. The configurable ACPI groups will be visible under512 /config/acpi, assuming configfs is mounted under /config.513 514config ACPI_PFRUT515 tristate "ACPI Platform Firmware Runtime Update and Telemetry"516 depends on 64BIT517 help518 This mechanism allows certain pieces of the platform firmware519 to be updated on the fly while the system is running (runtime)520 without the need to restart it, which is key in the cases when521 the system needs to be available 100% of the time and it cannot522 afford the downtime related to restarting it, or when the work523 carried out by the system is particularly important, so it cannot524 be interrupted, and it is not practical to wait until it is complete.525 526 The existing firmware code can be modified (driver update) or527 extended by adding new code to the firmware (code injection).528 529 Besides, the telemetry driver allows user space to fetch telemetry530 data from the firmware with the help of the Platform Firmware Runtime531 Telemetry interface.532 533 To compile the drivers as modules, choose M here:534 the modules will be called pfr_update and pfr_telemetry.535 536if ARM64537source "drivers/acpi/arm64/Kconfig"538endif539 540config ACPI_PPTT541 bool542 543config ACPI_PCC544 bool "ACPI PCC Address Space"545 depends on PCC546 default y547 help548 The PCC Address Space also referred as PCC Operation Region pertains549 to the region of PCC subspace that succeeds the PCC signature.550 551 The PCC Operation Region works in conjunction with the PCC Table552 (Platform Communications Channel Table). PCC subspaces that are553 marked for use as PCC Operation Regions must not be used as PCC554 subspaces for the standard ACPI features such as CPPC, RASF, PDTT and555 MPST. These standard features must always use the PCC Table instead.556 557 Enable this feature if you want to set up and install the PCC Address558 Space handler to handle PCC OpRegion in the firmware.559 560config ACPI_FFH561 bool "ACPI FFH Address Space"562 default n563 help564 The FFH(Fixed Function Hardware) Address Space also referred as FFH565 Operation Region allows to define platform specific opregion.566 567 Enable this feature if you want to set up and install the FFH Address568 Space handler to handle FFH OpRegion in the firmware.569 570source "drivers/acpi/pmic/Kconfig"571 572config ACPI_VIOT573 bool574 575config ACPI_PRMT576 bool "Platform Runtime Mechanism Support"577 depends on EFI_RUNTIME_WRAPPERS && (X86_64 || ARM64)578 default y579 help580 Platform Runtime Mechanism (PRM) is a firmware interface exposing a581 set of binary executables that can be called from the AML interpreter582 or directly from device drivers.583 584 Say Y to enable the AML interpreter to execute the PRM code.585 586 While this feature is optional in principle, leaving it out may587 substantially increase computational overhead related to the588 initialization of some server systems.589 590endif # ACPI591 592config X86_PM_TIMER593 bool "Power Management Timer Support" if EXPERT594 depends on X86 && (ACPI || JAILHOUSE_GUEST)595 default y596 help597 The Power Management Timer is available on all ACPI-capable,598 in most cases even if ACPI is unusable or blacklisted.599 600 This timing source is not affected by power management features601 like aggressive processor idling, throttling, frequency and/or602 voltage scaling, unlike the commonly used Time Stamp Counter603 (TSC) timing source.604 605 You should nearly always say Y here because many modern606 systems require this timer.607