From: Frank Myhr <fmyhr@fhmtech.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] lm-sensors Digest, Vol 41, Issue 2
Date: Tue, 02 Sep 2008 14:29:22 +0000 [thread overview]
Message-ID: <48BD4DC2.8000705@fhmtech.com> (raw)
Hector Lahoz Grañena wrote:
> Are there any plans to implement Smartguardian (i.e. fan speed control) for
> the it87 family? Should I write a daemon to control the fans or is the driver
> who has to do the work?
>
> Another possibility is using the smartguardian automatic mode which has the
> advantage, I think; that it's easy to implement and causes no CPU overload.
> By the way, the programming interface thar appears in the datasheet does not
> correspond to my chip (it8705 version 2). I almost go crazy.
Hi Hector,
I've been working to add automatic fan mode to the it87 driver. It works on the
it8718, but I'm still changing the sysfs interface, and adding auto mode support
for the other it87 chips. I'll post the code to this list when ready. It would
be great if you could help test it on your it8705_v2, I don't have one here.
Auto mode varies a bit from chip to chip, and for the 8705, for different
versions of the chip*. For your it8705_v2, auto mode allows 5 discrete fan
speeds: off, low, medium, high, and all fans full speed. You could get smoother
control by using the software pwm mode you already have working along with the
lm_sensors fancontrol script.
* Note that the datasheet version does not always correspond to the version
that the chip reports in Global Configuration Register 0x22:[3-0]. For
example:
datasheet chip-reported version
8705 0.3 0x02
8712 0.7 0x06
8712 0.81 0x07
8712 0.9.3 0x08
-Frank
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
reply other threads:[~2008-09-02 14:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=48BD4DC2.8000705@fhmtech.com \
--to=fmyhr@fhmtech.com \
--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.