From: Dario Messina <nanodario@gmail.com>
To: Stefan Assmann <sassmann@kpanic.de>
Cc: Alexander Kappner <agk@godking.net>,
ibm-acpi@hmh.eng.br, dvhart@infradead.org, andy@infradead.org,
ibm-acpi-devel@lists.sourceforge.net,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add Second Fan Support for Thinkpad P50
Date: Sat, 20 Jul 2019 17:22:00 +0200 [thread overview]
Message-ID: <5490267.oBufKZg01J@lenovodario> (raw)
In-Reply-To: <20180926143449.bnqliemloqw7fuyv@t530.fritz.box>
I have a Thinkpad P51 (BIOS version: N1UET74W, EC version: N1UHT26W).
This patch works on my computer and I can read both fan speeds through sysfs
interface.
On 2018-09-26 16:34:19 CEST, Stefan Assmann wrote:
> Is there a way to actually control the second fan? There's pwm1, but no
> pwm2. And pwm1 only affects fan1.
I have played with the driver code and I noticed that it is possible to
control both fans independently (unlike what the "Fan subdriver" comment in
the code says).
You can do that simply by calling fan_select_fan1 or fan_select_fan2, to
select a fan to be controlled, before calling fan_set_level. All control
parameters (disengaged, manual speeds, auto) are fully independent.
What is not smooth is reading back current control parameters from register
0x2f (like fan_pwm1_show or fan_pwm1_enable_show actually do), because the EC
ignores which fan is currently selected and it always returns the last written
value.
Distinti Saluti/Best Regards,
Dario Messina
prev parent reply other threads:[~2019-07-20 15:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-02 18:27 Alexander Kappner
2018-04-02 19:08 ` Henrique de Moraes Holschuh
2018-04-02 21:45 ` [ibm-acpi-devel] " Alexander Kappner
2018-04-02 20:22 ` Andy Shevchenko
2018-04-04 23:20 ` Alexander Kappner
2018-04-03 8:13 ` Andy Shevchenko
2018-09-26 14:34 ` Stefan Assmann
2019-07-20 15:22 ` Dario Messina [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=5490267.oBufKZg01J@lenovodario \
--to=nanodario@gmail.com \
--cc=agk@godking.net \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=ibm-acpi@hmh.eng.br \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sassmann@kpanic.de \
/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®