tjh.dev / kernel
Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux
1
fork

Configure Feed

Select the types of activity you want to include in your feed.

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>

authored by

Armin Wolf and committed by
Ilpo Järvinen 50b6914f cf0b8125

+9 -5
+9 -5
Documentation/wmi/acpi-interface.rst
··· 36 36 37 37 The WMI object flags control whether the method or notification ID is used: 38 38 39 - - 0x1: Data block usage is expensive and must be explicitly enabled/disabled. 39 + - 0x1: Data block is expensive to collect. 40 40 - 0x2: Data block contains WMI methods. 41 41 - 0x4: Data block contains ASCIZ string. 42 42 - 0x8: Data block describes a WMI event, use notification ID instead ··· 83 83 of 0 if the WMI event should be disabled, other values will enable 84 84 the WMI event. 85 85 86 + Those ACPI methods are always called even for WMI events not registered as 87 + being expensive to collect to match the behavior of the Windows driver. 88 + 86 89 WCxx ACPI methods 87 90 ----------------- 88 - Similar to the ``WExx`` ACPI methods, except that it controls data collection 89 - instead of events and thus the last two characters of the ACPI method name are 90 - the method ID of the data block to enable/disable. 91 + Similar to the ``WExx`` ACPI methods, except that instead of WMI events it controls 92 + data collection of data blocks registered as being expensive to collect. Thus the 93 + last two characters of the ACPI method name are the method ID of the data block 94 + to enable/disable. 91 95 92 96 Those ACPI methods are also called before setting data blocks to match the 93 - behaviour of the Windows driver. 97 + behavior of the Windows driver. 94 98 95 99 _WED ACPI method 96 100 ----------------