[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240214070433.2677-1-W_Armin@gmx.de>
Date: Wed, 14 Feb 2024 08:04:28 +0100
From: Armin Wolf <W_Armin@....de>
To: corentin.chary@...il.com,
luke@...nes.dev
Cc: hdegoede@...hat.com,
ilpo.jarvinen@...ux.intel.com,
platform-driver-x86@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: [PATCH 0/5] platform/x86: wmi: Fixes for event data handling
This patch series contains fixes for the handling of WMI event data
when receiving WMI events.
The first patch aims to prevent WMI event drivers depending on WMI
event data support from binding to a WMI device which does not
support the retrieval of additional WMI event data.
The second patch makes sure that the WMI core not only checks that
evaluating the ACPI control method used for retrieving additional
event data (_WED) succeeded, but that it also returned any data.
The third patch fixes an compatibility issue with the ACPI firmware
of some ASUS notebooks. This issue was "fixed" inside asus-wmi by
manually retrieving event data items, sidestepping the WMI core.
The last patch reverts this hacky fixup, as the underlying issue is
now handled inside the WMI core itself.
All patches where tested on a Dell Inspiron 3505 and a ASUS Prime
B650-Plus motherboard. However the last patch should be tested on an
actual ASUS notebook which is affected by the workaround.
Armin Wolf (5):
platform/x86: wmi: Prevent incompatible event driver from probing
platform/x86: wmi: Check if event data is not NULL
platform/x86: wmi: Always evaluate _WED when receiving an event
platform/x86: wmi: Update documentation regarding _WED
Revert "platform/x86: asus-wmi: Support WMI event queue"
Documentation/wmi/acpi-interface.rst | 5 +-
drivers/platform/x86/asus-wmi.c | 71 ++------------------------
drivers/platform/x86/wmi.c | 74 +++++++++++++++++++++++-----
include/linux/wmi.h | 2 +-
4 files changed, 71 insertions(+), 81 deletions(-)
--
2.39.2
Powered by blists - more mailing lists