All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Zintakis <michael.zintakis@googlemail.com>
To: Guenter Roeck <linux@roeck-us.net>
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: Thu, 28 Jun 2012 12:31:30 +0100	[thread overview]
Message-ID: <4FEC4092.7090104@googlemail.com> (raw)
In-Reply-To: <20120628052032.GA16364@roeck-us.net>


> Do you mean sysfs ?
>   
Yeah, sorry. Everything under /sys/class/hwmon/...

> 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.
>   
That won't be enough! I did a bit of experimenting and discovered the 
following:

The minimum value for pwm on all fans necessary to keep them going is 75 
(decimal) - below that value the fan just stops. The minimum value to 
kick-start the fan and make it spin from standstill is 190 (also 
decimal) - nothing below this value is sufficient to move the fan from 
its standstill position (in my script I use the maximum value - 255 - to 
be on the safe side).

So, even if I set the pwmX_auto_point5_pwm to 75 that won't be enough to 
kick-start the fan initially. On the other hand, if I set it to 190 that 
would be enough, but the fan will continue to spin at this rate which is 
very high (I may as well abandon fan/temperature management then).

> 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.
>   
It is indeed set to 2.

>> 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 ?
>   
It is and it is why I am keeping this automatic BIOS fan management in 
place and my script only intervenes to kick-start the fans when they are 
still, otherwise this automatic control is doing a good job. The problem 
is the actual kick-start (and the fact that there is no way I could 
force ACPI to abandon the region of memory used by the driver).


WARNING: multiple messages have this Message-ID (diff)
From: Michael Zintakis <michael.zintakis@googlemail.com>
To: Guenter Roeck <linux@roeck-us.net>
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: Thu, 28 Jun 2012 11:31:30 +0000	[thread overview]
Message-ID: <4FEC4092.7090104@googlemail.com> (raw)
In-Reply-To: <20120628052032.GA16364@roeck-us.net>


> Do you mean sysfs ?
>   
Yeah, sorry. Everything under /sys/class/hwmon/...

> 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.
>   
That won't be enough! I did a bit of experimenting and discovered the 
following:

The minimum value for pwm on all fans necessary to keep them going is 75 
(decimal) - below that value the fan just stops. The minimum value to 
kick-start the fan and make it spin from standstill is 190 (also 
decimal) - nothing below this value is sufficient to move the fan from 
its standstill position (in my script I use the maximum value - 255 - to 
be on the safe side).

So, even if I set the pwmX_auto_point5_pwm to 75 that won't be enough to 
kick-start the fan initially. On the other hand, if I set it to 190 that 
would be enough, but the fan will continue to spin at this rate which is 
very high (I may as well abandon fan/temperature management then).

> 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.
>   
It is indeed set to 2.

>> 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 ?
>   
It is and it is why I am keeping this automatic BIOS fan management in 
place and my script only intervenes to kick-start the fans when they are 
still, otherwise this automatic control is doing a good job. The problem 
is the actual kick-start (and the fact that there is no way I could 
force ACPI to abandon the region of memory used by the driver).


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  reply	other threads:[~2012-06-28 11:31 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-26 23:56 [lm-sensors] Fintek f71882fg ACPI conflict Michael Zintakis
2012-06-27 17:15 ` Guenter Roeck
2012-06-27 17:15   ` [lm-sensors] " Guenter Roeck
2012-06-27 23:00   ` Michael Zintakis
2012-06-27 23:00     ` Michael Zintakis
2012-06-28  1:45     ` Matthew Garrett
2012-06-28  1:45       ` Matthew Garrett
2012-06-28 11:15       ` Michael Zintakis
2012-06-28 11:15         ` Michael Zintakis
2012-06-28 12:40         ` Jean Delvare
2012-06-28 12:40           ` Jean Delvare
2012-06-28 12:53           ` Michael Zintakis
2012-06-28 12:53             ` Michael Zintakis
2012-06-28 13:27             ` Jean Delvare
2012-06-28 13:27               ` Jean Delvare
2012-06-29  5:35               ` Robert Hancock
2012-06-29  5:35                 ` Robert Hancock
2012-06-29 12:11                 ` Michael Zintakis
2012-06-29 12:11                   ` Michael Zintakis
2012-06-29 16:34                   ` Guenter Roeck
2012-06-29 16:34                     ` Guenter Roeck
2012-06-28  5:20     ` Guenter Roeck
2012-06-28  5:20       ` Guenter Roeck
2012-06-28 11:31       ` Michael Zintakis [this message]
2012-06-28 11:31         ` Michael Zintakis
2012-06-28 17:12         ` Guenter Roeck
2012-06-28 17:12           ` Guenter Roeck
2012-06-28 17:39           ` Michael Zintakis
2012-06-28 17:39             ` Michael Zintakis
2012-06-28 18:57             ` Guenter Roeck
2012-06-28 18:57               ` Guenter Roeck
2012-06-28  3:15 ` Andrey Repin
2012-06-28 11:36 ` Michael Zintakis

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=4FEC4092.7090104@googlemail.com \
    --to=michael.zintakis@googlemail.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lm-sensors@lm-sensors.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.