Commit 20b45147 authored by Carlos Corbacho's avatar Carlos Corbacho Committed by Len Brown
Browse files

ACPI: WMI: Improve Kconfig description 



As Pavel Machek has pointed out, the Kconfig entry for WMI is pretty
non-descriptive.

Rewrite it so that it explains what ACPI-WMI is, and why anyone
would want to enable it.

Many thanks to Ray Lee for ideas on this.

Signed-off-by: default avatarCarlos Corbacho <carlos@strangeworlds.co.uk>
CC: Pavel Machek <pavel@ucw.cz>
CC: Ray Lee <ray-lk@madrabbit.org>
Signed-off-by: default avatarLen Brown <len.brown@intel.com>
parent 543a9561

drivers/acpi/Kconfig

+15 −4
Original line number Diff line number Diff line
@@ -207,11 +207,22 @@ config ACPI_WMI 
	depends on X86

	depends on EXPERIMENTAL

	help

	  This driver adds support for the ACPI-WMI mapper device (PNP0C14)

	  found on some systems.

	  This driver adds support for the ACPI-WMI (Windows Management

	  Instrumentation) mapper device (PNP0C14) found on some systems.



	  NOTE: You will need another driver or userspace application on top of

	  this to actually use anything defined in the ACPI-WMI mapper.

	  ACPI-WMI is a proprietary extension to ACPI to expose parts of the

	  ACPI firmware to userspace - this is done through various vendor

	  defined methods and data blocks in a PNP0C14 device, which are then

	  made available for userspace to call.



	  The implementation of this in Linux currently only exposes this to

	  other kernel space drivers.



	  This driver is a required dependency to build the firmware specific

	  drivers needed on many machines, including Acer and HP laptops.



	  It is safe to enable this driver even if your DSDT doesn't define

	  any ACPI-WMI devices.



config ACPI_ASUS

        tristate "ASUS/Medion Laptop Extras"

CRA Git | Maintained and supported by SUSTech CRA and CCSE