1# SPDX-License-Identifier: GPL-2.0 2# 3# ACPI Configuration 4# 5 6config ARCH_SUPPORTS_ACPI 7 bool 8 9menuconfig ACPI 10 bool "ACPI (Advanced Configuration and Power Interface) Support" 11 depends on ARCH_SUPPORTS_ACPI 12 select PNP 13 select NLS 14 select CRC32 15 default y if X86 16 help 17 Advanced Configuration and Power Interface (ACPI) support for 18 Linux requires an ACPI-compliant platform (hardware/firmware), 19 and assumes the presence of OS-directed configuration and power 20 management (OSPM) software. This option will enlarge your 21 kernel by about 70K. 22 23 Linux ACPI provides a robust functional replacement for several 24 legacy configuration and power management interfaces, including 25 the Plug-and-Play BIOS specification (PnP BIOS), the 26 MultiProcessor Specification (MPS), and the Advanced Power 27 Management (APM) specification. If both ACPI and APM support 28 are configured, ACPI is used. 29 30 Linux support for ACPI is based on Intel Corporation's ACPI 31 Component Architecture (ACPI CA). For more information on the 32 ACPI CA, see: 33 <https://acpica.org/> 34 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 <https://uefi.org/specifications> 42 43if ACPI 44 45config ACPI_LEGACY_TABLES_LOOKUP 46 bool 47 48config ARCH_MIGHT_HAVE_ACPI_PDC 49 bool 50 51config ACPI_GENERIC_GSI 52 bool 53 54config ACPI_SYSTEM_POWER_STATES_SUPPORT 55 bool 56 57config ACPI_CCA_REQUIRED 58 bool 59 60config ACPI_TABLE_LIB 61 bool 62 63config ACPI_DEBUGGER 64 bool "AML debugger interface" 65 select ACPI_DEBUG 66 help 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. 71 72if ACPI_DEBUGGER 73 74config ACPI_DEBUGGER_USER 75 tristate "Userspace debugger accessibility" 76 depends on DEBUG_FS 77 help 78 Export /sys/kernel/debug/acpi/acpidbg for userspace utilities 79 to access the debugger functionalities. 80 81endif 82 83config ACPI_SPCR_TABLE 84 bool "ACPI Serial Port Console Redirection Support" 85 default y if X86 86 help 87 Enable support for Serial Port Console Redirection (SPCR) Table. 88 This table provides information about the configuration of the 89 earlycon console. 90 91config ACPI_FPDT 92 bool "ACPI Firmware Performance Data Table (FPDT) support" 93 depends on X86_64 94 help 95 Enable support for the Firmware Performance Data Table (FPDT). 96 This table provides information on the timing of the system 97 boot, S3 suspend and S3 resume firmware code paths. 98 99config ACPI_LPIT 100 bool 101 depends on X86_64 102 default y 103 104config ACPI_SLEEP 105 bool 106 depends on SUSPEND || HIBERNATION 107 depends on ACPI_SYSTEM_POWER_STATES_SUPPORT 108 default y 109 110config ACPI_REV_OVERRIDE_POSSIBLE 111 bool "Allow supported ACPI revision to be overridden" 112 depends on X86 113 default y 114 help 115 The platform firmware on some systems expects Linux to return "5" as 116 the supported ACPI revision which makes it expose system configuration 117 information in a special way. 118 119 For example, based on what ACPI exports as the supported revision, 120 Dell XPS 13 (2015) configures its audio device to either work in HDA 121 mode or in I2S mode, where the former is supposed to be used on Linux 122 until the latter is fully supported (in the kernel as well as in user 123 space). 124 125 This option enables a DMI-based quirk for the above Dell machine (so 126 that HDA audio is exposed by the platform firmware to the kernel) and 127 makes it possible to force the kernel to return "5" as the supported 128 ACPI revision via the "acpi_rev_override" command line switch. 129 130config ACPI_EC_DEBUGFS 131 tristate "EC read/write access through /sys/kernel/debug/ec" 132 help 133 Say N to disable Embedded Controller /sys/kernel/debug interface 134 135 Be aware that using this interface can confuse your Embedded 136 Controller in a way that a normal reboot is not enough. You then 137 have to power off your system, and remove the laptop battery for 138 some seconds. 139 An Embedded Controller typically is available on laptops and reads 140 sensor values like battery state and temperature. 141 The kernel accesses the EC through ACPI parsed code provided by BIOS 142 tables. This option allows to access the EC directly without ACPI 143 code being involved. 144 Thus this option is a debug option that helps to write ACPI drivers 145 and can be used to identify ACPI code or EC firmware bugs. 146 147config ACPI_AC 148 tristate "AC Adapter" 149 select POWER_SUPPLY 150 default y 151 help 152 This driver supports the AC Adapter object, which indicates 153 whether a system is on AC or not. If you have a system that can 154 switch between A/C and battery, say Y. 155 156 To compile this driver as a module, choose M here: 157 the module will be called ac. 158 159config ACPI_BATTERY 160 tristate "Battery" 161 select POWER_SUPPLY 162 default y 163 help 164 This driver adds support for battery information through 165 /proc/acpi/battery. If you have a mobile system with a battery, 166 say Y. 167 168 To compile this driver as a module, choose M here: 169 the module will be called battery. 170 171config ACPI_BUTTON 172 tristate "Button" 173 depends on INPUT 174 default y 175 help 176 This driver handles events on the power, sleep, and lid buttons. 177 A daemon reads events from input devices or via netlink and 178 performs user-defined actions such as shutting down the system. 179 This is necessary for software-controlled poweroff. 180 181 To compile this driver as a module, choose M here: 182 the module will be called button. 183 184config ACPI_TINY_POWER_BUTTON 185 tristate "Tiny Power Button Driver" 186 depends on !ACPI_BUTTON 187 help 188 This driver provides a tiny alternative to the ACPI Button driver. 189 The tiny power button driver only handles the power button. Rather 190 than notifying userspace via the input layer or a netlink event, this 191 driver directly signals the init process to shut down. 192 193 This driver is particularly suitable for cloud and VM environments, 194 which use a simulated power button to initiate a controlled poweroff, 195 but which may not want to run a separate userspace daemon to process 196 input events. 197 198config ACPI_TINY_POWER_BUTTON_SIGNAL 199 int "Tiny Power Button Signal" 200 depends on ACPI_TINY_POWER_BUTTON 201 default 38 202 help 203 Default signal to send to init in response to the power button. 204 205 Likely values here include 38 (SIGRTMIN+4) to power off, or 2 206 (SIGINT) to simulate Ctrl+Alt+Del. 207 208config ACPI_VIDEO 209 tristate "Video" 210 depends on BACKLIGHT_CLASS_DEVICE 211 depends on INPUT 212 select THERMAL 213 help 214 This driver implements the ACPI Extensions For Display Adapters 215 for integrated graphics devices on motherboard, as specified in 216 ACPI 2.0 Specification, Appendix B. This supports basic operations 217 such as defining the video POST device, retrieving EDID information, 218 and setting up a video output. 219 220 To compile this driver as a module, choose M here: 221 the module will be called video. 222 223config ACPI_FAN 224 tristate "Fan" 225 depends on THERMAL 226 default y 227 help 228 This driver supports ACPI fan devices, allowing user-mode 229 applications to perform basic fan control (on, off, status). 230 231 To compile this driver as a module, choose M here: 232 the module will be called fan. 233 234config ACPI_TAD 235 tristate "ACPI Time and Alarm (TAD) Device Support" 236 depends on SYSFS && PM_SLEEP 237 help 238 The ACPI Time and Alarm (TAD) device is an alternative to the Real 239 Time Clock (RTC). Its wake timers allow the system to transition from 240 the S3 (or optionally S4/S5) state to S0 state after a time period 241 elapses. In comparison with the RTC Alarm, the TAD provides a larger 242 scale of flexibility in the wake timers. The time capabilities of the 243 TAD maintain the time of day information across platform power 244 transitions, and keep track of time even when the platform is turned 245 off. 246 247config ACPI_DOCK 248 bool "Dock" 249 help 250 This driver supports ACPI-controlled docking stations and removable 251 drive bays such as the IBM Ultrabay and the Dell Module Bay. 252 253config ACPI_CPU_FREQ_PSS 254 bool 255 256config ACPI_PROCESSOR_CSTATE 257 def_bool y 258 depends on ACPI_PROCESSOR 259 depends on IA64 || X86 260 261config ACPI_PROCESSOR_IDLE 262 bool 263 select CPU_IDLE 264 265config ACPI_MCFG 266 bool 267 268config ACPI_CPPC_LIB 269 bool 270 depends on ACPI_PROCESSOR 271 select MAILBOX 272 select PCC 273 help 274 If this option is enabled, this file implements common functionality 275 to parse CPPC tables as described in the ACPI 5.1+ spec. The 276 routines implemented are meant to be used by other 277 drivers to control CPU performance using CPPC semantics. 278 If your platform does not support CPPC in firmware, 279 leave this option disabled. 280 281config ACPI_PROCESSOR 282 tristate "Processor" 283 depends on X86 || IA64 || ARM64 || LOONGARCH 284 select ACPI_PROCESSOR_IDLE 285 select ACPI_CPU_FREQ_PSS if X86 || IA64 || LOONGARCH 286 select THERMAL 287 default y 288 help 289 This driver adds support for the ACPI Processor package. It is required 290 by several flavors of cpufreq performance-state, thermal, throttling and 291 idle drivers. 292 293 To compile this driver as a module, choose M here: 294 the module will be called processor. 295 296config ACPI_IPMI 297 tristate "IPMI" 298 depends on IPMI_HANDLER 299 help 300 This driver enables the ACPI to access the BMC controller. And it 301 uses the IPMI request/response message to communicate with BMC 302 controller, which can be found on the server. 303 304 To compile this driver as a module, choose M here: 305 the module will be called as acpi_ipmi. 306 307config ACPI_HOTPLUG_CPU 308 bool 309 depends on ACPI_PROCESSOR && HOTPLUG_CPU 310 select ACPI_CONTAINER 311 default y 312 313config ACPI_PROCESSOR_AGGREGATOR 314 tristate "Processor Aggregator" 315 depends on ACPI_PROCESSOR 316 depends on X86 317 help 318 ACPI 4.0 defines processor Aggregator, which enables OS to perform 319 specific processor configuration and control that applies to all 320 processors in the platform. Currently only logical processor idling 321 is defined, which is to reduce power consumption. This driver 322 supports the new device. 323 324config ACPI_THERMAL 325 tristate "Thermal Zone" 326 depends on ACPI_PROCESSOR 327 select THERMAL 328 default y 329 help 330 This driver supports ACPI thermal zones. Most mobile and 331 some desktop systems support ACPI thermal zones. It is HIGHLY 332 recommended that this option be enabled, as your processor(s) 333 may be damaged without it. 334 335 To compile this driver as a module, choose M here: 336 the module will be called thermal. 337 338config ACPI_PLATFORM_PROFILE 339 tristate 340 341config ACPI_CUSTOM_DSDT_FILE 342 string "Custom DSDT Table file to include" 343 default "" 344 depends on !STANDALONE 345 help 346 This option supports a custom DSDT by linking it into the kernel. 347 348 Enter the full path name to the file which includes the AmlCode 349 or dsdt_aml_code declaration. 350 351 If unsure, don't enter a file name. 352 353config ACPI_CUSTOM_DSDT 354 bool 355 default ACPI_CUSTOM_DSDT_FILE != "" 356 357config ARCH_HAS_ACPI_TABLE_UPGRADE 358 def_bool n 359 360config ACPI_TABLE_UPGRADE 361 bool "Allow upgrading ACPI tables via initrd" 362 depends on BLK_DEV_INITRD && ARCH_HAS_ACPI_TABLE_UPGRADE 363 default y 364 help 365 This option provides functionality to upgrade arbitrary ACPI tables 366 via initrd. No functional change if no ACPI tables are passed via 367 initrd, therefore it's safe to say Y. 368 See Documentation/admin-guide/acpi/initrd_table_override.rst for details 369 370config ACPI_TABLE_OVERRIDE_VIA_BUILTIN_INITRD 371 bool "Override ACPI tables from built-in initrd" 372 depends on ACPI_TABLE_UPGRADE 373 depends on INITRAMFS_SOURCE!="" && INITRAMFS_COMPRESSION_NONE 374 help 375 This option provides functionality to override arbitrary ACPI tables 376 from built-in uncompressed initrd. 377 378 See Documentation/admin-guide/acpi/initrd_table_override.rst for details 379 380config ACPI_DEBUG 381 bool "Debug Statements" 382 help 383 The ACPI subsystem can produce debug output. Saying Y enables this 384 output and increases the kernel size by around 50K. 385 386 Use the acpi.debug_layer and acpi.debug_level kernel command-line 387 parameters documented in Documentation/firmware-guide/acpi/debug.rst and 388 Documentation/admin-guide/kernel-parameters.rst to control the type and 389 amount of debug output. 390 391config ACPI_PCI_SLOT 392 bool "PCI slot detection driver" 393 depends on SYSFS && PCI 394 help 395 This driver creates entries in /sys/bus/pci/slots/ for all PCI 396 slots in the system. This can help correlate PCI bus addresses, 397 i.e., segment/bus/device/function tuples, with physical slots in 398 the system. If you are unsure, say N. 399 400config ACPI_CONTAINER 401 bool "Container and Module Devices" 402 default (ACPI_HOTPLUG_MEMORY || ACPI_HOTPLUG_CPU) 403 help 404 This driver supports ACPI Container and Module devices (IDs 405 ACPI0004, PNP0A05, and PNP0A06). 406 407 This helps support hotplug of nodes, CPUs, and memory. 408 409config ACPI_HOTPLUG_MEMORY 410 bool "Memory Hotplug" 411 depends on MEMORY_HOTPLUG 412 help 413 This driver supports ACPI memory hotplug. The driver 414 fields notifications on ACPI memory devices (PNP0C80), 415 which represent memory ranges that may be onlined or 416 offlined during runtime. 417 418 If your hardware and firmware do not support adding or 419 removing memory devices at runtime, you need not enable 420 this driver. 421 422config ACPI_HOTPLUG_IOAPIC 423 bool 424 depends on PCI 425 depends on X86_IO_APIC 426 default y 427 428config ACPI_SBS 429 tristate "Smart Battery System" 430 depends on X86 431 select POWER_SUPPLY 432 help 433 This driver supports the Smart Battery System, another 434 type of access to battery information, found on some laptops. 435 436 To compile this driver as a module, choose M here: 437 the modules will be called sbs and sbshc. 438 439config ACPI_HED 440 tristate "Hardware Error Device" 441 help 442 This driver supports the Hardware Error Device (PNP0C33), 443 which is used to report some hardware errors notified via 444 SCI, mainly the corrected errors. 445 446config ACPI_CUSTOM_METHOD 447 tristate "Allow ACPI methods to be inserted/replaced at run time" 448 depends on DEBUG_FS 449 help 450 This debug facility allows ACPI AML methods to be inserted and/or 451 replaced without rebooting the system. For details refer to: 452 Documentation/firmware-guide/acpi/method-customizing.rst. 453 454 NOTE: This option is security sensitive, because it allows arbitrary 455 kernel memory to be written to by root (uid=0) users, allowing them 456 to bypass certain security measures (e.g. if root is not allowed to 457 load additional kernel modules after boot, this feature may be used 458 to override that restriction). 459 460config ACPI_BGRT 461 bool "Boottime Graphics Resource Table support" 462 depends on EFI && (X86 || ARM64) 463 help 464 This driver adds support for exposing the ACPI Boottime Graphics 465 Resource Table, which allows the operating system to obtain 466 data from the firmware boot splash. It will appear under 467 /sys/firmware/acpi/bgrt/ . 468 469config ACPI_REDUCED_HARDWARE_ONLY 470 bool "Hardware-reduced ACPI support only" if EXPERT 471 def_bool n 472 help 473 This config item changes the way the ACPI code is built. When this 474 option is selected, the kernel will use a specialized version of 475 ACPICA that ONLY supports the ACPI "reduced hardware" mode. The 476 resulting kernel will be smaller but it will also be restricted to 477 running in ACPI reduced hardware mode ONLY. 478 479 If you are unsure what to do, do not enable this option. 480 481source "drivers/acpi/nfit/Kconfig" 482source "drivers/acpi/numa/Kconfig" 483source "drivers/acpi/apei/Kconfig" 484source "drivers/acpi/dptf/Kconfig" 485 486config ACPI_WATCHDOG 487 bool 488 489config ACPI_EXTLOG 490 tristate "Extended Error Log support" 491 depends on X86_MCE && X86_LOCAL_APIC && EDAC 492 select UEFI_CPER 493 help 494 Certain usages such as Predictive Failure Analysis (PFA) require 495 more information about the error than what can be described in 496 processor machine check banks. Most server processors log 497 additional information about the error in processor uncore 498 registers. Since the addresses and layout of these registers vary 499 widely from one processor to another, system software cannot 500 readily make use of them. To complicate matters further, some of 501 the additional error information cannot be constructed without 502 detailed knowledge about platform topology. 503 504 Enhanced MCA Logging allows firmware to provide additional error 505 information to system software, synchronous with MCE or CMCI. This 506 driver adds support for that functionality with corresponding 507 tracepoint which carries that information to userspace. 508 509config ACPI_ADXL 510 bool 511 512config ACPI_CONFIGFS 513 tristate "ACPI configfs support" 514 select CONFIGFS_FS 515 help 516 Select this option to enable support for ACPI configuration from 517 userspace. The configurable ACPI groups will be visible under 518 /config/acpi, assuming configfs is mounted under /config. 519 520config ACPI_PFRUT 521 tristate "ACPI Platform Firmware Runtime Update and Telemetry" 522 depends on 64BIT 523 help 524 This mechanism allows certain pieces of the platform firmware 525 to be updated on the fly while the system is running (runtime) 526 without the need to restart it, which is key in the cases when 527 the system needs to be available 100% of the time and it cannot 528 afford the downtime related to restarting it, or when the work 529 carried out by the system is particularly important, so it cannot 530 be interrupted, and it is not practical to wait until it is complete. 531 532 The existing firmware code can be modified (driver update) or 533 extended by adding new code to the firmware (code injection). 534 535 Besides, the telemetry driver allows user space to fetch telemetry 536 data from the firmware with the help of the Platform Firmware Runtime 537 Telemetry interface. 538 539 To compile the drivers as modules, choose M here: 540 the modules will be called pfr_update and pfr_telemetry. 541 542if ARM64 543source "drivers/acpi/arm64/Kconfig" 544 545config ACPI_PPTT 546 bool 547endif 548 549config ACPI_PCC 550 bool "ACPI PCC Address Space" 551 depends on PCC 552 default y 553 help 554 The PCC Address Space also referred as PCC Operation Region pertains 555 to the region of PCC subspace that succeeds the PCC signature. 556 557 The PCC Operation Region works in conjunction with the PCC Table 558 (Platform Communications Channel Table). PCC subspaces that are 559 marked for use as PCC Operation Regions must not be used as PCC 560 subspaces for the standard ACPI features such as CPPC, RASF, PDTT and 561 MPST. These standard features must always use the PCC Table instead. 562 563 Enable this feature if you want to set up and install the PCC Address 564 Space handler to handle PCC OpRegion in the firmware. 565 566source "drivers/acpi/pmic/Kconfig" 567 568config ACPI_VIOT 569 bool 570 571config ACPI_PRMT 572 bool "Platform Runtime Mechanism Support" 573 depends on EFI && (X86_64 || ARM64) 574 default y 575 help 576 Platform Runtime Mechanism (PRM) is a firmware interface exposing a 577 set of binary executables that can be called from the AML interpreter 578 or directly from device drivers. 579 580 Say Y to enable the AML interpreter to execute the PRM code. 581 582 While this feature is optional in principle, leaving it out may 583 substantially increase computational overhead related to the 584 initialization of some server systems. 585 586endif # ACPI 587 588config X86_PM_TIMER 589 bool "Power Management Timer Support" if EXPERT 590 depends on X86 && (ACPI || JAILHOUSE_GUEST) 591 default y 592 help 593 The Power Management Timer is available on all ACPI-capable, 594 in most cases even if ACPI is unusable or blacklisted. 595 596 This timing source is not affected by power management features 597 like aggressive processor idling, throttling, frequency and/or 598 voltage scaling, unlike the commonly used Time Stamp Counter 599 (TSC) timing source. 600 601 You should nearly always say Y here because many modern 602 systems require this timer. 603