diff options
| author | Armin Wolf <W_Armin@gmx.de> | 2025-02-16 20:32:50 +0100 |
|---|---|---|
| committer | Ilpo Järvinen <ilpo.jarvinen@linux.intel.com> | 2025-02-24 13:30:15 +0200 |
| commit | 08c9f4029007325e0bbd4fdda05650b03e43f071 (patch) | |
| tree | 8851b5bebb67a52710455ecaa63ba8dfe31071f5 /Documentation/wmi | |
| parent | 656f0961d126f5d1f0bcc62fa8bb7598d8f89207 (diff) | |
| download | linux-08c9f4029007325e0bbd4fdda05650b03e43f071.tar.gz linux-08c9f4029007325e0bbd4fdda05650b03e43f071.tar.bz2 linux-08c9f4029007325e0bbd4fdda05650b03e43f071.zip | |
platform/x86: wmi: Call WCxx methods when setting data blocks
After performing some tests with a custom SSDT table available at
https://github.com/Wer-Wolf/acpi-wmi-ssdt i found out that Windows
also enables data block collection even when the data block is
being set.
Emulate this behaviour to avoid confusing the ACPI firmware.
The bus-based API already implements this behaviour, so only the
legacy GUID-based API needs to be changed.
Signed-off-by: Armin Wolf <W_Armin@gmx.de>
Link: https://lore.kernel.org/r/20250216193251.866125-8-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>
Diffstat (limited to 'Documentation/wmi')
| -rw-r--r-- | Documentation/wmi/acpi-interface.rst | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/Documentation/wmi/acpi-interface.rst b/Documentation/wmi/acpi-interface.rst index 06fb7fcf4413..f1b28835d23c 100644 --- a/Documentation/wmi/acpi-interface.rst +++ b/Documentation/wmi/acpi-interface.rst @@ -89,6 +89,9 @@ Similar to the ``WExx`` ACPI methods, except that it controls data collection instead of events and thus the 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 +behaviour of the Windows driver. + _WED ACPI method ---------------- |