From: Guenter Roeck <linux@roeck-us.net>
To: Michael Zintakis <michael.zintakis@googlemail.com>
Cc: lm-sensors@lm-sensors.org, Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org
Subject: Re: [lm-sensors] Fintek f71882fg ACPI conflict
Date: Wed, 27 Jun 2012 22:20:32 -0700 [thread overview]
Message-ID: <20120628052032.GA16364@roeck-us.net> (raw)
In-Reply-To: <4FEB90A8.8050901@googlemail.com>
On Thu, Jun 28, 2012 at 12:00:56AM +0100, Michael Zintakis wrote:
> Hello Guenter and All,
>
[ .. ]
> One last question (though this is more specific to the f71882fg
> driver): I have a procfs file called "pwmX_auto_pointY" (Y being
Do you mean sysfs ?
> from 1-5), which indicates the various pwm current value which is to
> be applied for different points: 4 being when the controlling
> temperature is low (the value of pwmX_auto_point4_temp to be
> precise) and 1 being where the current is at its maximum - normally
> 255.
>
> Now, what is the purpose of pwmX_auto_point5 - does this hold the
> pwm value where the fan is in an idle state (i.e. the temperature is
> below pwmX_auto_point4_temp)? Because on all 3 fans, I have this set
> to 1, which, I am assuming is when the fans are stopped.
>
Correct. 1 is too low, though. Default value per datasheet is 0x80.
Whatever it is, it should be high enough for the fans to start spinning.
The F71882FG does not have a register to set a "start spinning" pwm value,
so your minimum must guarantee that the fans do start to spin.
What is your setting for pwmX_enable ? It should probably be set to
automatic(2) so the chip can automatically control the fan speed depending
on the temperature.
> Even if I bring this value to some "idle" current, that won't help
> much because when I first boot the system, the fans are *always*
> still, so even if the idle state is >1, that won't help me much, so
> there must be another - better - way than using a script to
> "kickstart" the fans initially, surely!
>
Maybe fan control is not set to automatic by the BIOS ?
Guenter
next prev parent reply other threads:[~2012-06-28 5:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4FEA4C10.2060904@googlemail.com>
2012-06-27 17:15 ` Fintek f71882fg ACPI conflict Guenter Roeck
2012-06-27 23:00 ` [lm-sensors] " Michael Zintakis
2012-06-28 1:45 ` Matthew Garrett
2012-06-28 11:15 ` Michael Zintakis
2012-06-28 12:40 ` Jean Delvare
2012-06-28 12:53 ` Michael Zintakis
2012-06-28 13:27 ` Jean Delvare
2012-06-29 5:35 ` Robert Hancock
2012-06-29 12:11 ` Michael Zintakis
2012-06-29 16:34 ` Guenter Roeck
2012-06-28 5:20 ` Guenter Roeck [this message]
2012-06-28 11:31 ` Michael Zintakis
2012-06-28 17:12 ` Guenter Roeck
2012-06-28 17:39 ` Michael Zintakis
2012-06-28 18:57 ` Guenter Roeck
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=20120628052032.GA16364@roeck-us.net \
--to=linux@roeck-us.net \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=michael.zintakis@googlemail.com \
/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;
as well as URLs for NNTP newsgroup(s).