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