diff options
author | Armin Wolf <W_Armin@gmx.de> | 2024-02-19 12:59:17 +0100 |
---|---|---|
committer | Ilpo Järvinen <ilpo.jarvinen@linux.intel.com> | 2024-02-27 13:44:25 +0100 |
commit | 56230bd733f8cb122632c80bc49ae12b1a9365a6 (patch) | |
tree | 6ae156d778c101e7583b19a56d8cea59aca64bbe /.gitignore | |
parent | platform/x86: wmi: Check if event data is not NULL (diff) | |
download | linux-56230bd733f8cb122632c80bc49ae12b1a9365a6.tar.xz linux-56230bd733f8cb122632c80bc49ae12b1a9365a6.zip |
platform/x86: wmi: Always evaluate _WED when receiving an event
The ACPI WMI specification states:
"The _WED control method is evaluated by the mapper in
response to receiving a notification from a control
method."
This means that _WED should be evaluated unconditionally even
if no WMI event consumers are present.
Some firmware implementations actually depend on this behavior
by storing the event data inside a queue which will fill up if
the WMI core stops retrieving event data items due to no
consumers being present
Fix this by always evaluating _WED even if no WMI event consumers
are present.
Signed-off-by: Armin Wolf <W_Armin@gmx.de>
Link: https://lore.kernel.org/r/20240219115919.16526-4-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 '.gitignore')
0 files changed, 0 insertions, 0 deletions