From: Hans de Goede <hdegoede@redhat.com>
To: Armin Wolf <W_Armin@gmx.de>,
james@equiv.tech, jlee@suse.com, corentin.chary@gmail.com,
luke@ljones.dev, matan@svgalib.org, coproscefalo@gmail.com
Cc: ilpo.jarvinen@linux.intel.com, linux@roeck-us.net,
jdelvare@suse.com, rafael@kernel.org, lenb@kernel.org,
platform-driver-x86@vger.kernel.org, linux-hwmon@vger.kernel.org,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/5] platform/x86: wmi: Pass event data directly to legacy notify handlers
Date: Thu, 5 Sep 2024 17:31:22 +0200 [thread overview]
Message-ID: <ea736e0a-a92e-4a2f-a06c-04f8c20aaf22@redhat.com> (raw)
In-Reply-To: <20240901031055.3030-1-W_Armin@gmx.de>
Hi,
On 9/1/24 5:10 AM, Armin Wolf wrote:
> The current legacy WMI handlers are susceptible to picking up wrong
> WMI event data on systems where different WMI devices share some
> notification IDs.
>
> Prevent this by letting the WMI driver core taking care of retrieving
> the event data. This also simplifies the legacy WMI handlers and their
> implementation inside the WMI driver core.
>
> The fisr patch fixes a minor issue discovered inside the hp-wmi-sensors
> driver.
> The second patch converts all legacy WMI notify handlers to stop using
> wmi_get_event_data() and instead use the new event data provided by
> the WMI driver core.
> The remaining patches finally perform some cleanups.
>
> The patch series was tested on a Dell Inspiron 3505 and a Acer Aspire
> E1-731 and appears to work.
>
> Changes since v1:
> - Rework the hp-wmi-sensors patch
> - add Reviewed-by tags
>
> Armin Wolf (5):
> hwmon: (hp-wmi-sensors) Check if WMI event data exists
> platform/x86: wmi: Pass event data directly to legacy notify handlers
> platform/x86: wmi: Remove wmi_get_event_data()
> platform/x86: wmi: Merge get_event_data() with wmi_get_notify_data()
> platform/x86: wmi: Call both legacy and WMI driver notify handlers
Thank you for your patch-series, I've applied the series to my
review-hans branch:
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/log/?h=review-hans
Once I've run some tests on this branch the patches there will be
added to the platform-drivers-x86/for-next branch and eventually
will be included in the pdx86 pull-request to Linus for the next
merge-window.
Regards,
Hans
>
> drivers/hwmon/hp-wmi-sensors.c | 20 +---
> drivers/platform/x86/acer-wmi.c | 16 +--
> drivers/platform/x86/asus-wmi.c | 19 +--
> drivers/platform/x86/dell/dell-wmi-aio.c | 13 +--
> drivers/platform/x86/hp/hp-wmi.c | 16 +--
> drivers/platform/x86/huawei-wmi.c | 14 +--
> drivers/platform/x86/lg-laptop.c | 13 +--
> drivers/platform/x86/msi-wmi.c | 20 +---
> drivers/platform/x86/toshiba-wmi.c | 15 +--
> drivers/platform/x86/wmi.c | 143 ++++++-----------------
> include/linux/acpi.h | 3 +-
> 11 files changed, 53 insertions(+), 239 deletions(-)
>
> --
> 2.39.2
>
prev parent reply other threads:[~2024-09-05 15:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-01 3:10 [PATCH v2 0/5] platform/x86: wmi: Pass event data directly to legacy notify handlers Armin Wolf
2024-09-01 3:10 ` [PATCH v2 1/5] hwmon: (hp-wmi-sensors) Check if WMI event data exists Armin Wolf
2024-09-02 14:09 ` Ilpo Järvinen
2024-09-02 14:28 ` Guenter Roeck
2024-09-04 17:55 ` Hans de Goede
2024-09-04 18:38 ` Guenter Roeck
2024-09-04 18:42 ` Hans de Goede
2024-09-04 19:40 ` Guenter Roeck
2024-09-01 3:10 ` [PATCH v2 2/5] platform/x86: wmi: Pass event data directly to legacy notify handlers Armin Wolf
2024-09-01 3:10 ` [PATCH v2 3/5] platform/x86: wmi: Remove wmi_get_event_data() Armin Wolf
2024-09-01 3:10 ` [PATCH v2 4/5] platform/x86: wmi: Merge get_event_data() with wmi_get_notify_data() Armin Wolf
2024-09-01 3:10 ` [PATCH v2 5/5] platform/x86: wmi: Call both legacy and WMI driver notify handlers Armin Wolf
2024-09-05 15:31 ` Hans de Goede [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ea736e0a-a92e-4a2f-a06c-04f8c20aaf22@redhat.com \
--to=hdegoede@redhat.com \
--cc=W_Armin@gmx.de \
--cc=coproscefalo@gmail.com \
--cc=corentin.chary@gmail.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=james@equiv.tech \
--cc=jdelvare@suse.com \
--cc=jlee@suse.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=luke@ljones.dev \
--cc=matan@svgalib.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox