From: Armin Wolf <W_Armin@gmx.de>
To: Povilas Kanapickas <povilas@radix.lt>, pali@kernel.org
Cc: jdelvare@suse.com, linux@roeck-us.net,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hwmon: (dell-smm) Add Dell XPS 9370 to fan control whitelist
Date: Sat, 7 Dec 2024 22:26:31 +0100 [thread overview]
Message-ID: <fa78f27a-a92c-452d-b710-c4b3c8c52629@gmx.de> (raw)
In-Reply-To: <e5d65c8a-4785-4635-ad77-d5155f517155@radix.lt>
Am 07.12.24 um 21:26 schrieb Povilas Kanapickas:
> Add the Dell XPS 9370 to the fan control whitelist to allow
> for manual fan control.
Can you check if using i8k_fan_control_data[I8K_FAN_30A3_31A3] also works?
The reason for this is that the official Dell software seems to use those SMM calls
to enable/disable automatic fan control. If this does not work then you can keep
the i8k_fan_control_data[I8K_FAN_34A3_35A3].
Thanks,
Armin Wolf
> Signed-off-by: Povilas Kanapickas <povilas@radix.lt>
> ---
> drivers/hwmon/dell-smm-hwmon.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/hwmon/dell-smm-hwmon.c b/drivers/hwmon/dell-smm-hwmon.c
> index f5bdf842040e..bcb295ea3319 100644
> --- a/drivers/hwmon/dell-smm-hwmon.c
> +++ b/drivers/hwmon/dell-smm-hwmon.c
> @@ -1544,6 +1544,14 @@ static const struct dmi_system_id i8k_whitelist_fan_control[] __initconst = {
> },
> .driver_data = (void *)&i8k_fan_control_data[I8K_FAN_34A3_35A3],
> },
> + {
> + .ident = "Dell XPS 13 9370",
> + .matches = {
> + DMI_MATCH(DMI_SYS_VENDOR, "Dell Inc."),
> + DMI_EXACT_MATCH(DMI_PRODUCT_NAME, "XPS 13 9370"),
> + },
> + .driver_data = (void *)&i8k_fan_control_data[I8K_FAN_34A3_35A3],
> + },
> {
> .ident = "Dell Optiplex 7000",
> .matches = {
next prev parent reply other threads:[~2024-12-07 21:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-07 20:26 [PATCH] hwmon: (dell-smm) Add Dell XPS 9370 to fan control whitelist Povilas Kanapickas
2024-12-07 21:26 ` Armin Wolf [this message]
2025-01-09 21:03 ` Povilas Kanapickas
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=fa78f27a-a92c-452d-b710-c4b3c8c52629@gmx.de \
--to=w_armin@gmx.de \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=pali@kernel.org \
--cc=povilas@radix.lt \
/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