| # SPDX-License-Identifier: GPL-2.0-or-later | |
| # | |
| # ACPI WMI Core | |
| # | |
| menuconfig ACPI_WMI | |
| tristate "ACPI-WMI support" | |
| depends on ACPI | |
| 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" | |
| config WMI_BMOF | |
| tristate "WMI embedded Binary MOF driver" | |
| default ACPI_WMI | |
| help | |
| Say Y here if you want to be able to read the firmware-embedded | |
| WMI Binary MOF (Managed Object Format) data. Using this requires | |
| userspace tools, see Documentation/wmi/devices/wmi-bmof.rst for | |
| details. | |
| To compile this driver as a module, choose M here: the module will | |
| be called wmi-bmof. | |
| endif # ACPI_WMI |