From: "Pali Rohár" <pali.rohar@gmail.com>
To: Giovanni Mascellani <gio@debian.org>
Cc: Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hwmon: (dell-smm-hwmon) Disable BIOS fan control on SET_FAN
Date: Sat, 16 Nov 2019 16:03:10 +0100 [thread overview]
Message-ID: <20191116150310.dlhjrr3kyh7fsykf@pali> (raw)
In-Reply-To: <20191114211408.22123-1-gio@debian.org>
[-- Attachment #1: Type: text/plain, Size: 706 bytes --]
On Thursday 14 November 2019 22:14:08 Giovanni Mascellani wrote:
> +#define I8K_SMM_DISABLE_BIOS 0x30a3
> +#define I8K_SMM_ENABLE_BIOS 0x31a3
In my old notes I have written these two comments:
0x30a3 disable the Fn- key combinations (except the volume functions) key and disable BIOS auto fan control (no args)
0x31a3 enable the Fn- key combinations (except the volume functions) key and enable BIOS auto fan control (no args)
So seems that these two commands have some side effect on some
machines.
For 0x34a3/0x35a3 I have only these comments:
0x34a3 disable BIOS auto fan control (no args)
0x35a3 enable BIOS auto fan control (no args)
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2019-11-16 15:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 21:14 Giovanni Mascellani
2019-11-14 21:39 ` Guenter Roeck
2019-11-14 21:51 ` Pali Rohár
2019-11-15 9:51 ` Giovanni Mascellani
2019-11-15 11:29 ` Pali Rohár
2019-11-15 13:44 ` Giovanni Mascellani
2019-11-15 14:36 ` Pali Rohár
2019-11-15 14:46 ` Guenter Roeck
2019-11-15 19:10 ` Giovanni Mascellani
2019-11-15 7:12 ` kbuild test robot
2019-11-15 8:19 ` kbuild test robot
2019-11-16 15:03 ` Pali Rohár [this message]
2019-11-16 17:14 ` Giovanni Mascellani
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=20191116150310.dlhjrr3kyh7fsykf@pali \
--to=pali.rohar@gmail.com \
--cc=gio@debian.org \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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
all inboxes | Powered by JetHome®