| 1 | # SPDX-License-Identifier: GPL-2.0-or-later |
| 2 | # |
| 3 | # ACPI WMI Core |
| 4 | # |
| 5 | |
| 6 | menuconfig ACPI_WMI |
| 7 | tristate "ACPI-WMI support" |
| 8 | depends on ACPI && X86 |
| 9 | select NLS |
| 10 | help |
| 11 | This option enables support for the ACPI-WMI driver core. |
| 12 | |
| 13 | The ACPI-WMI interface is a proprietary extension of ACPI allowing |
| 14 | the platform firmware to expose WMI (Windows Management Instrumentation) |
| 15 | objects used for managing various aspects of the underlying system. |
| 16 | Mapping between ACPI control methods and WMI objects happens through |
| 17 | special mapper devices (PNP0C14) defined inside the ACPI tables. |
| 18 | |
| 19 | Enabling this option is necessary for building the vendor specific |
| 20 | ACPI-WMI client drivers for Acer, Dell an HP machines (among others). |
| 21 | |
| 22 | It is safe to enable this option even for machines that do not contain |
| 23 | any ACPI-WMI mapper devices at all. |
| 24 | |
| 25 | if ACPI_WMI |
| 26 | |
| 27 | config ACPI_WMI_LEGACY_DEVICE_NAMES |
| 28 | bool "Use legacy WMI device naming scheme" |
| 29 | help |
| 30 | Say Y here to force the WMI driver core to use the old WMI device naming |
| 31 | scheme when creating WMI devices. Doing so might be necessary for some |
| 32 | userspace applications but will cause the registration of WMI devices with |
| 33 | the same GUID to fail in some corner cases. |
| 34 | |
| 35 | source "drivers/platform/wmi/tests/Kconfig" |
| 36 | |
| 37 | endif # ACPI_WMI |