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 default y if X86 15 help 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 20 kernel by about 70K. 21 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. 28 29 The project home page for the Linux ACPI subsystem is here: 30 <https://01.org/linux-acpi> 31 32 Linux support for ACPI is based on Intel Corporation's ACPI 33 Component Architecture (ACPI CA). For more information on the 34 ACPI CA, see: 35 <http://acpica.org/> 36 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> 45 46if ACPI 47 48config ACPI_LEGACY_TABLES_LOOKUP 49 bool 50 51config ARCH_MIGHT_HAVE_ACPI_PDC 52 bool 53 54config ACPI_GENERIC_GSI 55 bool 56 57config ACPI_SYSTEM_POWER_STATES_SUPPORT 58 bool 59 60config ACPI_CCA_REQUIRED 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 accessiblity" 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_LPIT 92 bool 93 depends on X86_64 94 default y 95 96config ACPI_SLEEP 97 bool 98 depends on SUSPEND || HIBERNATION 99 depends on ACPI_SYSTEM_POWER_STATES_SUPPORT 100 default y 101 102config ACPI_PROCFS_POWER 103 bool "Deprecated power /proc/acpi directories" 104 depends on X86 && PROC_FS 105 help 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. 116 117 Say N to delete power /proc/acpi/ directories that have moved to /sys. 118 119config ACPI_REV_OVERRIDE_POSSIBLE 120 bool "Allow supported ACPI revision to be overridden" 121 depends on X86 122 default y 123 help 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. 127 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 132 space). 133 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. 138 139config ACPI_EC_DEBUGFS 140 tristate "EC read/write access through /sys/kernel/debug/ec" 141 help 142 Say N to disable Embedded Controller /sys/kernel/debug interface 143 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 147 some seconds. 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 152 code being involved. 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. 155 156config ACPI_AC 157 tristate "AC Adapter" 158 select POWER_SUPPLY 159 default y 160 help 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. 164 165 To compile this driver as a module, choose M here: 166 the module will be called ac. 167 168config ACPI_BATTERY 169 tristate "Battery" 170 select POWER_SUPPLY 171 default y 172 help 173 This driver adds support for battery information through 174 /proc/acpi/battery. If you have a mobile system with a battery, 175 say Y. 176 177 To compile this driver as a module, choose M here: 178 the module will be called battery. 179 180config ACPI_BUTTON 181 tristate "Button" 182 depends on INPUT 183 default y 184 help 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. 189 190 To compile this driver as a module, choose M here: 191 the module will be called button. 192 193config ACPI_VIDEO 194 tristate "Video" 195 depends on X86 && BACKLIGHT_CLASS_DEVICE 196 depends on INPUT 197 select THERMAL 198 help 199 This driver implements the ACPI Extensions For Display Adapters 200 for integrated graphics devices on motherboard, as specified in 201 ACPI 2.0 Specification, Appendix B. This supports basic operations 202 such as defining the video POST device, retrieving EDID information, 203 and setting up a video output. 204 205 To compile this driver as a module, choose M here: 206 the module will be called video. 207 208config ACPI_FAN 209 tristate "Fan" 210 depends on THERMAL 211 default y 212 help 213 This driver supports ACPI fan devices, allowing user-mode 214 applications to perform basic fan control (on, off, status). 215 216 To compile this driver as a module, choose M here: 217 the module will be called fan. 218 219config ACPI_TAD 220 tristate "ACPI Time and Alarm (TAD) Device Support" 221 depends on SYSFS && PM_SLEEP 222 help 223 The ACPI Time and Alarm (TAD) device is an alternative to the Real 224 Time Clock (RTC). Its wake timers allow the system to transition from 225 the S3 (or optionally S4/S5) state to S0 state after a time period 226 elapses. In comparison with the RTC Alarm, the TAD provides a larger 227 scale of flexibility in the wake timers. The time capabilities of the 228 TAD maintain the time of day information across platform power 229 transitions, and keep track of time even when the platform is turned 230 off. 231 232config ACPI_DOCK 233 bool "Dock" 234 help 235 This driver supports ACPI-controlled docking stations and removable 236 drive bays such as the IBM Ultrabay and the Dell Module Bay. 237 238config ACPI_CPU_FREQ_PSS 239 bool 240 select THERMAL 241 242config ACPI_PROCESSOR_CSTATE 243 def_bool y 244 depends on IA64 || X86 245 246config ACPI_PROCESSOR_IDLE 247 bool 248 select CPU_IDLE 249 250config ACPI_MCFG 251 bool 252 253config ACPI_CPPC_LIB 254 bool 255 depends on ACPI_PROCESSOR 256 select MAILBOX 257 select PCC 258 help 259 If this option is enabled, this file implements common functionality 260 to parse CPPC tables as described in the ACPI 5.1+ spec. The 261 routines implemented are meant to be used by other 262 drivers to control CPU performance using CPPC semantics. 263 If your platform does not support CPPC in firmware, 264 leave this option disabled. 265 266config ACPI_PROCESSOR 267 tristate "Processor" 268 depends on X86 || IA64 || ARM64 269 select ACPI_PROCESSOR_IDLE 270 select ACPI_CPU_FREQ_PSS if X86 || IA64 271 default y 272 help 273 This driver adds support for the ACPI Processor package. It is required 274 by several flavors of cpufreq performance-state, thermal, throttling and 275 idle drivers. 276 277 To compile this driver as a module, choose M here: 278 the module will be called processor. 279 280config ACPI_IPMI 281 tristate "IPMI" 282 depends on IPMI_HANDLER 283 help 284 This driver enables the ACPI to access the BMC controller. And it 285 uses the IPMI request/response message to communicate with BMC 286 controller, which can be found on on the server. 287 288 To compile this driver as a module, choose M here: 289 the module will be called as acpi_ipmi. 290 291config ACPI_HOTPLUG_CPU 292 bool 293 depends on ACPI_PROCESSOR && HOTPLUG_CPU 294 select ACPI_CONTAINER 295 default y 296 297config ACPI_PROCESSOR_AGGREGATOR 298 tristate "Processor Aggregator" 299 depends on ACPI_PROCESSOR 300 depends on X86 301 help 302 ACPI 4.0 defines processor Aggregator, which enables OS to perform 303 specific processor configuration and control that applies to all 304 processors in the platform. Currently only logical processor idling 305 is defined, which is to reduce power consumption. This driver 306 supports the new device. 307 308config ACPI_THERMAL 309 tristate "Thermal Zone" 310 depends on ACPI_PROCESSOR 311 select THERMAL 312 default y 313 help 314 This driver supports ACPI thermal zones. Most mobile and 315 some desktop systems support ACPI thermal zones. It is HIGHLY 316 recommended that this option be enabled, as your processor(s) 317 may be damaged without it. 318 319 To compile this driver as a module, choose M here: 320 the module will be called thermal. 321 322config ACPI_NUMA 323 bool "NUMA support" 324 depends on NUMA 325 depends on (X86 || IA64 || ARM64) 326 default y if IA64 || ARM64 327 328config ACPI_CUSTOM_DSDT_FILE 329 string "Custom DSDT Table file to include" 330 default "" 331 depends on !STANDALONE 332 help 333 This option supports a custom DSDT by linking it into the kernel. 334 See Documentation/admin-guide/acpi/dsdt-override.rst 335 336 Enter the full path name to the file which includes the AmlCode 337 or dsdt_aml_code declaration. 338 339 If unsure, don't enter a file name. 340 341config ACPI_CUSTOM_DSDT 342 bool 343 default ACPI_CUSTOM_DSDT_FILE != "" 344 345config ARCH_HAS_ACPI_TABLE_UPGRADE 346 def_bool n 347 348config ACPI_TABLE_UPGRADE 349 bool "Allow upgrading ACPI tables via initrd" 350 depends on BLK_DEV_INITRD && ARCH_HAS_ACPI_TABLE_UPGRADE 351 default y 352 help 353 This option provides functionality to upgrade arbitrary ACPI tables 354 via initrd. No functional change if no ACPI tables are passed via 355 initrd, therefore it's safe to say Y. 356 See Documentation/admin-guide/acpi/initrd_table_override.rst for details 357 358config ACPI_TABLE_OVERRIDE_VIA_BUILTIN_INITRD 359 bool "Override ACPI tables from built-in initrd" 360 depends on ACPI_TABLE_UPGRADE 361 depends on INITRAMFS_SOURCE!="" && INITRAMFS_COMPRESSION="" 362 help 363 This option provides functionality to override arbitrary ACPI tables 364 from built-in uncompressed initrd. 365 366 See Documentation/admin-guide/acpi/initrd_table_override.rst for details 367 368config ACPI_DEBUG 369 bool "Debug Statements" 370 help 371 The ACPI subsystem can produce debug output. Saying Y enables this 372 output and increases the kernel size by around 50K. 373 374 Use the acpi.debug_layer and acpi.debug_level kernel command-line 375 parameters documented in Documentation/firmware-guide/acpi/debug.rst and 376 Documentation/admin-guide/kernel-parameters.rst to control the type and 377 amount of debug output. 378 379config ACPI_PCI_SLOT 380 bool "PCI slot detection driver" 381 depends on SYSFS && PCI 382 help 383 This driver creates entries in /sys/bus/pci/slots/ for all PCI 384 slots in the system. This can help correlate PCI bus addresses, 385 i.e., segment/bus/device/function tuples, with physical slots in 386 the system. If you are unsure, say N. 387 388config ACPI_CONTAINER 389 bool "Container and Module Devices" 390 default (ACPI_HOTPLUG_MEMORY || ACPI_HOTPLUG_CPU) 391 help 392 This driver supports ACPI Container and Module devices (IDs 393 ACPI0004, PNP0A05, and PNP0A06). 394 395 This helps support hotplug of nodes, CPUs, and memory. 396 397 To compile this driver as a module, choose M here: 398 the module will be called container. 399 400config ACPI_HOTPLUG_MEMORY 401 bool "Memory Hotplug" 402 depends on MEMORY_HOTPLUG 403 help 404 This driver supports ACPI memory hotplug. The driver 405 fields notifications on ACPI memory devices (PNP0C80), 406 which represent memory ranges that may be onlined or 407 offlined during runtime. 408 409 If your hardware and firmware do not support adding or 410 removing memory devices at runtime, you need not enable 411 this driver. 412 413 To compile this driver as a module, choose M here: 414 the module will be called acpi_memhotplug. 415 416config ACPI_HOTPLUG_IOAPIC 417 bool 418 depends on PCI 419 depends on X86_IO_APIC 420 default y 421 422config ACPI_SBS 423 tristate "Smart Battery System" 424 depends on X86 425 select POWER_SUPPLY 426 help 427 This driver supports the Smart Battery System, another 428 type of access to battery information, found on some laptops. 429 430 To compile this driver as a module, choose M here: 431 the modules will be called sbs and sbshc. 432 433config ACPI_HED 434 tristate "Hardware Error Device" 435 help 436 This driver supports the Hardware Error Device (PNP0C33), 437 which is used to report some hardware errors notified via 438 SCI, mainly the corrected errors. 439 440config ACPI_CUSTOM_METHOD 441 tristate "Allow ACPI methods to be inserted/replaced at run time" 442 depends on DEBUG_FS 443 help 444 This debug facility allows ACPI AML methods to be inserted and/or 445 replaced without rebooting the system. For details refer to: 446 Documentation/firmware-guide/acpi/method-customizing.rst. 447 448 NOTE: This option is security sensitive, because it allows arbitrary 449 kernel memory to be written to by root (uid=0) users, allowing them 450 to bypass certain security measures (e.g. if root is not allowed to 451 load additional kernel modules after boot, this feature may be used 452 to override that restriction). 453 454config ACPI_BGRT 455 bool "Boottime Graphics Resource Table support" 456 depends on EFI && (X86 || ARM64) 457 help 458 This driver adds support for exposing the ACPI Boottime Graphics 459 Resource Table, which allows the operating system to obtain 460 data from the firmware boot splash. It will appear under 461 /sys/firmware/acpi/bgrt/ . 462 463config ACPI_REDUCED_HARDWARE_ONLY 464 bool "Hardware-reduced ACPI support only" if EXPERT 465 def_bool n 466 help 467 This config item changes the way the ACPI code is built. When this 468 option is selected, the kernel will use a specialized version of 469 ACPICA that ONLY supports the ACPI "reduced hardware" mode. The 470 resulting kernel will be smaller but it will also be restricted to 471 running in ACPI reduced hardware mode ONLY. 472 473 If you are unsure what to do, do not enable this option. 474 475source "drivers/acpi/nfit/Kconfig" 476source "drivers/acpi/hmat/Kconfig" 477 478source "drivers/acpi/apei/Kconfig" 479source "drivers/acpi/dptf/Kconfig" 480 481config ACPI_WATCHDOG 482 bool 483 484config ACPI_EXTLOG 485 tristate "Extended Error Log support" 486 depends on X86_MCE && X86_LOCAL_APIC && EDAC 487 select UEFI_CPER 488 help 489 Certain usages such as Predictive Failure Analysis (PFA) require 490 more information about the error than what can be described in 491 processor machine check banks. Most server processors log 492 additional information about the error in processor uncore 493 registers. Since the addresses and layout of these registers vary 494 widely from one processor to another, system software cannot 495 readily make use of them. To complicate matters further, some of 496 the additional error information cannot be constructed without 497 detailed knowledge about platform topology. 498 499 Enhanced MCA Logging allows firmware to provide additional error 500 information to system software, synchronous with MCE or CMCI. This 501 driver adds support for that functionality with corresponding 502 tracepoint which carries that information to userspace. 503 504config ACPI_ADXL 505 bool 506 507menuconfig PMIC_OPREGION 508 bool "PMIC (Power Management Integrated Circuit) operation region support" 509 help 510 Select this option to enable support for ACPI operation 511 region of the PMIC chip. The operation region can be used 512 to control power rails and sensor reading/writing on the 513 PMIC chip. 514 515if PMIC_OPREGION 516config CRC_PMIC_OPREGION 517 bool "ACPI operation region support for CrystalCove PMIC" 518 depends on INTEL_SOC_PMIC 519 help 520 This config adds ACPI operation region support for CrystalCove PMIC. 521 522config XPOWER_PMIC_OPREGION 523 bool "ACPI operation region support for XPower AXP288 PMIC" 524 depends on MFD_AXP20X_I2C && IOSF_MBI=y 525 help 526 This config adds ACPI operation region support for XPower AXP288 PMIC. 527 528config BXT_WC_PMIC_OPREGION 529 bool "ACPI operation region support for BXT WhiskeyCove PMIC" 530 depends on INTEL_SOC_PMIC_BXTWC 531 help 532 This config adds ACPI operation region support for BXT WhiskeyCove PMIC. 533 534config CHT_WC_PMIC_OPREGION 535 bool "ACPI operation region support for CHT Whiskey Cove PMIC" 536 depends on INTEL_SOC_PMIC_CHTWC 537 help 538 This config adds ACPI operation region support for CHT Whiskey Cove PMIC. 539 540config CHT_DC_TI_PMIC_OPREGION 541 bool "ACPI operation region support for Dollar Cove TI PMIC" 542 depends on INTEL_SOC_PMIC_CHTDC_TI 543 help 544 This config adds ACPI operation region support for Dollar Cove TI PMIC. 545 546endif 547 548config ACPI_CONFIGFS 549 tristate "ACPI configfs support" 550 select CONFIGFS_FS 551 help 552 Select this option to enable support for ACPI configuration from 553 userspace. The configurable ACPI groups will be visible under 554 /config/acpi, assuming configfs is mounted under /config. 555 556if ARM64 557source "drivers/acpi/arm64/Kconfig" 558 559config ACPI_PPTT 560 bool 561endif 562 563config TPS68470_PMIC_OPREGION 564 bool "ACPI operation region support for TPS68470 PMIC" 565 depends on MFD_TPS68470 566 help 567 This config adds ACPI operation region support for TI TPS68470 PMIC. 568 TPS68470 device is an advanced power management unit that powers 569 a Compact Camera Module (CCM), generates clocks for image sensors, 570 drives a dual LED for flash and incorporates two LED drivers for 571 general purpose indicators. 572 This driver enables ACPI operation region support control voltage 573 regulators and clocks. 574 575 This option is a bool as it provides an ACPI operation 576 region, which must be available before any of the devices 577 using this, are probed. 578 579endif # ACPI 580 581config X86_PM_TIMER 582 bool "Power Management Timer Support" if EXPERT 583 depends on X86 && (ACPI || JAILHOUSE_GUEST) 584 default y 585 help 586 The Power Management Timer is available on all ACPI-capable, 587 in most cases even if ACPI is unusable or blacklisted. 588 589 This timing source is not affected by power management features 590 like aggressive processor idling, throttling, frequency and/or 591 voltage scaling, unlike the commonly used Time Stamp Counter 592 (TSC) timing source. 593 594 You should nearly always say Y here because many modern 595 systems require this timer. 596