drivers/platform/wmi/Kconfig
Source file repositories/reference/linux-study-clean/drivers/platform/wmi/Kconfig
File Facts
- System
- Linux kernel
- Corpus path
drivers/platform/wmi/Kconfig- Extension
[no extension]- Size
- 1271 bytes
- Lines
- 38
- Domain
- Driver Families
- Bucket
- drivers/platform
- Inferred role
- Driver Families: build/configuration rule
- Status
- atlas-only
Why This File Exists
Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
# SPDX-License-Identifier: GPL-2.0-or-later
#
# ACPI WMI Core
#
menuconfig ACPI_WMI
tristate "ACPI-WMI support"
depends on ACPI && X86
select NLS
help
This option enables support for the ACPI-WMI driver core.
The ACPI-WMI interface is a proprietary extension of ACPI allowing
the platform firmware to expose WMI (Windows Management Instrumentation)
objects used for managing various aspects of the underlying system.
Mapping between ACPI control methods and WMI objects happens through
special mapper devices (PNP0C14) defined inside the ACPI tables.
Enabling this option is necessary for building the vendor specific
ACPI-WMI client drivers for Acer, Dell an HP machines (among others).
It is safe to enable this option even for machines that do not contain
any ACPI-WMI mapper devices at all.
if ACPI_WMI
config ACPI_WMI_LEGACY_DEVICE_NAMES
bool "Use legacy WMI device naming scheme"
help
Say Y here to force the WMI driver core to use the old WMI device naming
scheme when creating WMI devices. Doing so might be necessary for some
userspace applications but will cause the registration of WMI devices with
the same GUID to fail in some corner cases.
source "drivers/platform/wmi/tests/Kconfig"
endif # ACPI_WMI
Annotation
- Atlas domain: Driver Families / drivers/platform.
- Implementation status: atlas-only.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.