All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mildred Ki'Lya" <mildred593@online.fr>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] fancontrol EeePC,
Date: Sun, 25 Apr 2010 14:55:09 +0000	[thread overview]
Message-ID: <4BD457CD.6070907@online.fr> (raw)
In-Reply-To: <p2r64d6c631004250035lca8a4234o4787745b623460bb@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1920 bytes --]

On 04/25/2010 01:21 PM, Jean Delvare wrote:
> Hi Mildred,
>
> On Sun, 25 Apr 2010 09:35:58 +0200, Mildred Ki'Lya wrote:
>   
>> Hi,
>>
>> I am using fancontrol for my new EeePC, and when fancontrol exit (when I
>> reboot for example) the fans are set to manual mode at full speed.
>>
>> Aparently, the source code of fancontrol first tries to set the fan to safe
>> mode, and if it doesn't work, set it to manual at full speed. Apparently,
>> the EeePC safe mode is the same as automatic mode. So when we write "0" to
>> pwm1_enable, if we read it again, we'll see "2".
>>     
> This is a bug in the eeepc driver. If it doesn't support mode 0, it
> should return -EINVAL when one tries to set it.
>   

Well, I didn't think this was a bug, from what I read, mode 0
corresponds to safe mode which is the automatic mode on the EeePC, and
of course since this is the same as the mode 2 (automatic), when we read
the file back we get 2.

But you certainly know better about this, so I'm not pressing the issue
further.

If I understand how fancontrol works, when the mode 0 doesn't work, it
set the pwm to mnual mode (1) and maximum speed. Do you think that is a
good choice given that for some laptops where the default mode is the
automatic mode (2) ? That would be a perfectly acceptable fallback when
fancontrol isn't in charge.

Do you think there is possibility in the future that fancontrol reset
the fan state to automatic when it quits (when specified in the
configuration) ? I'd be willing to work on a patch if that were the case.


Mildred

-- 
Mildred Ki'Lya
╭───────── mildred593@online.fr ──────────
│ Jabber, GoogleTalk: <mildred@jabber.fr>
│ Website: <http://ki.lya.online.fr>           GPG ID: 9A7D 2E2B
│ Fingerprint: 197C A7E6 645B 4299 6D37 684B 6F9D A8D6 9A7D 2E2B



[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

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

  parent reply	other threads:[~2010-04-25 14:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-25  7:35 [lm-sensors] fancontrol EeePC, Mildred Ki'Lya
2010-04-25 11:21 ` Jean Delvare
2010-04-25 14:55 ` Mildred Ki'Lya [this message]
2010-04-25 17:02 ` Jean Delvare

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=4BD457CD.6070907@online.fr \
    --to=mildred593@online.fr \
    --cc=lm-sensors@vger.kernel.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.