platform/x86: wmi: Update documentation of WCxx/WExx ACPI methods

Inform potential firmware developers that WExx ACPI methods are
always called by the WMI driver core even if the associated WMI event
is not marked as being expensive.

Signed-off-by: Armin Wolf <W_Armin@gmx.de>
Link: https://lore.kernel.org/r/20250619221440.6737-2-W_Armin@gmx.de
Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
This commit is contained in:
Armin Wolf 2025-06-20 00:14:40 +02:00 committed by Ilpo Järvinen
parent cf0b812500
commit 50b6914fc5
No known key found for this signature in database
GPG Key ID: 59AC4F6153E5CE31

View File

@ -36,7 +36,7 @@ Offset Size (in bytes) Content
The WMI object flags control whether the method or notification ID is used: The WMI object flags control whether the method or notification ID is used:
- 0x1: Data block usage is expensive and must be explicitly enabled/disabled. - 0x1: Data block is expensive to collect.
- 0x2: Data block contains WMI methods. - 0x2: Data block contains WMI methods.
- 0x4: Data block contains ASCIZ string. - 0x4: Data block contains ASCIZ string.
- 0x8: Data block describes a WMI event, use notification ID instead - 0x8: Data block describes a WMI event, use notification ID instead
@ -83,14 +83,18 @@ event as hexadecimal value. Their first parameter is an integer with a value
of 0 if the WMI event should be disabled, other values will enable of 0 if the WMI event should be disabled, other values will enable
the WMI event. the WMI event.
Those ACPI methods are always called even for WMI events not registered as
being expensive to collect to match the behavior of the Windows driver.
WCxx ACPI methods WCxx ACPI methods
----------------- -----------------
Similar to the ``WExx`` ACPI methods, except that it controls data collection Similar to the ``WExx`` ACPI methods, except that instead of WMI events it controls
instead of events and thus the last two characters of the ACPI method name are data collection of data blocks registered as being expensive to collect. Thus the
the method ID of the data block to enable/disable. last two characters of the ACPI method name are the method ID of the data block
to enable/disable.
Those ACPI methods are also called before setting data blocks to match the Those ACPI methods are also called before setting data blocks to match the
behaviour of the Windows driver. behavior of the Windows driver.
_WED ACPI method _WED ACPI method
---------------- ----------------