From: Hans de Goede <hdegoede@redhat.com>
To: Armin Wolf <W_Armin@gmx.de>, pali@kernel.org
Cc: markgross@kernel.org, ilpo.jarvinen@linux.intel.com,
jdelvare@suse.com, linux@roeck-us.net,
platform-driver-x86@vger.kernel.org, linux-hwmon@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/9] hwmon: (dell-smm) Add support for WMI SMM interface
Date: Mon, 13 Nov 2023 21:17:48 +0100 [thread overview]
Message-ID: <8c25dfec-b0ca-4e2f-964a-5ae62452e141@redhat.com> (raw)
In-Reply-To: <3ec0496d-3b89-46f5-9faf-9fcce78f6b38@gmx.de>
Hi Armin,
On 11/13/23 20:55, Armin Wolf wrote:
> Am 06.11.23 um 07:43 schrieb Armin Wolf:
>
>> This patch series adds support for an alternative SMM calling
>> backend to the dell-smm-hwmon driver. The reason for this is
>> that on some modern machines, the legacy SMM calling interface
>> does not work anymore and the SMM handler can be called over
>> ACPI WMI instead.
>>
>> The first four patches prepare the driver by allowing to
>> specify different SMM calling backends, and by moving most of
>> the DMI handling into i8k_init() so that the DMI tables can
>> keep their __initconst attributes (the WMI SMM backend driver
>> does not probe at module init time). The fifth patch does some
>> minor cleanup, while the next three patches implement the new
>> WMI SMM calling backend. The last patch adds the machine of
>> the user who requested and tested the changes to the fan control
>> whitelist.
>>
>> If the driver does not detect the legacy SMM interface, either
>> because the machine is not whitelisted or because the SMM handler
>> does not react, it registers an WMI driver which will then bound
>> to the WMI SMM interface and do the remaining initialization.
>>
>> The deprecated procfs interface is not supported when using the
>> WMI SMM calling backend for the following reason: the WMI driver
>> can potentially be instantiated multiple times while the deprectated
>> procfs interface cannot. This should not cause any regressions
>> because on machines supporting only the WMI SMM interface, the
>> driver would, until now, not load anyway.
>>
>> All patches where tested on a Dell Inspiron 3505 and a Dell
>> OptiPlex 7000.
>
> Any thoughts on this?
I was waiting for the merge window to close before
reviewing / merging patches for the next cycle.
I plan to review and hopefully merge this and your
other series sometime this week.
Regards,
Hans
next prev parent reply other threads:[~2023-11-13 20:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 6:43 [PATCH v3 0/9] hwmon: (dell-smm) Add support for WMI SMM interface Armin Wolf
2023-11-06 6:43 ` [PATCH v3 1/9] hwmon: (dell-smm) Prepare for multiple SMM calling backends Armin Wolf
2023-11-06 6:43 ` [PATCH v3 2/9] hwmon: (dell-smm) Move blacklist handling to module init Armin Wolf
2023-11-06 6:43 ` [PATCH v3 3/9] hwmon: (dell-smm) Move whitelist " Armin Wolf
2023-11-06 6:43 ` [PATCH v3 4/9] hwmon: (dell-smm) Move DMI config " Armin Wolf
2023-11-06 6:43 ` [PATCH v3 5/9] hwmon: (dell-smm) Move config entries out of i8k_dmi_table Armin Wolf
2023-11-06 6:43 ` [PATCH v3 6/9] hwmon: (dell-smm) Introduce helper function for data init Armin Wolf
2023-11-06 6:43 ` [PATCH v3 7/9] hwmon: (dell-smm) Add support for WMI SMM interface Armin Wolf
[not found] ` <20231114141259.culmdxsoa3hduudm@pali>
2023-11-17 22:31 ` Armin Wolf
2023-11-06 6:43 ` [PATCH v3 8/9] hwmon: (dell-smm) Document the " Armin Wolf
2023-11-06 6:43 ` [PATCH v3 9/9] hwmon: (dell-smm) Add Optiplex 7000 to fan control whitelist Armin Wolf
2023-11-13 19:55 ` [PATCH v3 0/9] hwmon: (dell-smm) Add support for WMI SMM interface Armin Wolf
2023-11-13 20:17 ` Hans de Goede [this message]
2023-11-14 13:57 ` Guenter Roeck
2023-11-14 14:08 ` Hans de Goede
2023-11-20 13:03 ` Hans de Goede
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=8c25dfec-b0ca-4e2f-964a-5ae62452e141@redhat.com \
--to=hdegoede@redhat.com \
--cc=W_Armin@gmx.de \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=markgross@kernel.org \
--cc=pali@kernel.org \
--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