From: Armin Wolf <W_Armin@gmx.de>
To: james@equiv.tech, markpearson@lenovo.com, jorge.lopez2@hp.com
Cc: jdelvare@suse.com, linux@roeck-us.net,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
hdegoede@redhat.com, ilpo.jarvinen@linux.intel.com,
platform-driver-x86@vger.kernel.org, corbet@lwn.net,
linux-doc@vger.kernel.org
Subject: [PATCH 0/7] platform/x86: wmi: Rework WMI device enabling
Date: Mon, 3 Feb 2025 19:23:15 +0100 [thread overview]
Message-ID: <20250203182322.384883-1-W_Armin@gmx.de> (raw)
This patch series reworks how WMI devices are enabled and disabled
to improve the compatibility with various firmware implementations.
The first three patches make sure that no WMI driver using the WMI bus
infrastructure is using the deprecated GUID-based API to access the
underlying WMI device.
The fourth patch is a unrelated cleanup patch.
The last three patches finally rework the WMI device enabling inside
the WMI core and update the documentation.
The WMI core patches have been tested on a Dell Inspiron 3505, but
the remaining patches are compile-tested only.
Armin Wolf (7):
hwmon: (hp-wmi-sensors) Use the WMI bus API when accessing sensors
platform/x86: think-lmi: Use ACPI object when extracting strings
platform/x86: think-lmi: Use WMI bus API when accessing BIOS settings
platform/x86: hp-bioscfg: Use wmi_instance_count()
platform/x86: wmi: Rework WCxx/WExx ACPI method handling
platform/x86: wmi: Call WCxx methods when setting data blocks
platform/x86: wmi: Update documentation regarding the GUID-based API
Documentation/wmi/acpi-interface.rst | 3 +
.../wmi/driver-development-guide.rst | 4 +
drivers/hwmon/hp-wmi-sensors.c | 4 +-
drivers/platform/x86/hp/hp-bioscfg/bioscfg.c | 13 +-
drivers/platform/x86/think-lmi.c | 51 ++++----
drivers/platform/x86/think-lmi.h | 2 +
drivers/platform/x86/wmi.c | 114 +++++++++---------
7 files changed, 96 insertions(+), 95 deletions(-)
--
2.39.5
next reply other threads:[~2025-02-03 18:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 18:23 Armin Wolf [this message]
2025-02-03 18:23 ` [PATCH 1/7] hwmon: (hp-wmi-sensors) Use the WMI bus API when accessing sensors Armin Wolf
2025-02-04 0:41 ` James Seo
2025-02-04 1:18 ` Guenter Roeck
2025-02-04 9:41 ` Armin Wolf
2025-02-03 18:23 ` [PATCH 2/7] platform/x86: think-lmi: Use ACPI object when extracting strings Armin Wolf
2025-02-10 0:31 ` Armin Wolf
2025-02-11 16:46 ` Mark Pearson
2025-02-03 18:23 ` [PATCH 3/7] platform/x86: think-lmi: Use WMI bus API when accessing BIOS settings Armin Wolf
2025-02-13 13:17 ` Ilpo Järvinen
2025-02-14 3:07 ` Armin Wolf
2025-02-03 18:23 ` [PATCH 4/7] platform/x86: hp-bioscfg: Use wmi_instance_count() Armin Wolf
2025-02-04 10:37 ` Ilpo Järvinen
2025-02-04 13:06 ` Armin Wolf
2025-02-04 14:27 ` Ilpo Järvinen
2025-02-03 18:23 ` [PATCH 5/7] platform/x86: wmi: Rework WCxx/WExx ACPI method handling Armin Wolf
2025-02-03 18:23 ` [PATCH 6/7] platform/x86: wmi: Call WCxx methods when setting data blocks Armin Wolf
2025-02-03 18:23 ` [PATCH 7/7] platform/x86: wmi: Update documentation regarding the GUID-based API Armin Wolf
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=20250203182322.384883-1-W_Armin@gmx.de \
--to=w_armin@gmx.de \
--cc=corbet@lwn.net \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=james@equiv.tech \
--cc=jdelvare@suse.com \
--cc=jorge.lopez2@hp.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=markpearson@lenovo.com \
--cc=platform-driver-x86@vger.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