summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorArmin Wolf <W_Armin@gmx.de>2026-08-02 14:45:30 +0200
committerIlpo Järvinen <ilpo.jarvinen@linux.intel.com>2026-09-18 19:42:03 +0300
commitd3b84e9c1a63c3ef6ea89276b7162ccb52b2ffd8 (patch)
tree3978a08b6d8a122660f9e9d4a01e47ff2e019359 /tools/perf/scripts/python
parentc3e23729224dbf177185e99b61b4ca39046e9b12 (diff)
downloadlinux-next-d3b84e9c1a63c3ef6ea89276b7162ccb52b2ffd8.tar.gz
linux-next-d3b84e9c1a63c3ef6ea89276b7162ccb52b2ffd8.zip
platform/x86: dell-wmi-aio: Convert to use the bus-based WMI API
It turns out that some devices like the Dell Inspiron One 2310 contain multiple WMI event devices with a matching GUID of 284A0E6B-380E-472A-921F-E52786257FB4, each handling a separate hotkey (volume up, volume down, ...). The dell-wmi-aio driver however still uses the legacy GUID-based WMI API and can thus only see the first of those WMI event devices, preventing the remaining buttons from working. Fix this by converting the driver to use the modern bus-based WMI API. This also includes replacing the usage of union acpi_object with struct wmi_buffer. Tested using the ACPI-WMI ASL code from the Dell Inspiron One 2310 together with some changes to allow injecting events. Link: https://linux-hardware.org/?probe=e86d77e44d Signed-off-by: Armin Wolf <W_Armin@gmx.de> Link: https://patch.msgid.link/20260802124530.7116-1-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 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions