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