From: r.marek@sh.cvut.cz (Rudolf Marek)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] [PATCH] Add fan control support to W83627EHF
Date: Sat, 04 Mar 2006 21:47:20 +0000 [thread overview]
Message-ID: <440A0AE8.5050604@sh.cvut.cz> (raw)
In-Reply-To: <4409FFA1.7050109@sh.cvut.cz>
Hi,
> Thanks for posting your work! I'm testing it right now. I have a question:
>
>
>>pwm[1-4]_enable - this file controls mode of fan/temperature control:
>> * 0 Disabled. In fact the pwm is set to 255
>> * 1 Manual Mode, write to pwm file any value 0-255 (fullspeed)
>> * 2 Thermal Cruise
>> * 3 Smart FAN III
>
>
> There is another mode, RPM Cruise, in the datasheet. Smart Fan 3 is
> only supported by CPUFANOUT0 and CPUFANOUT1. Tell me what you think,
> maybe mode 3 should be RPM cruise and mode 4 is either not allowed
> (-EINVAL) or for the two fans that allow Smart Fan 3, it turns it on.
I removed the support for RPM cruise because I cannot see the use of such mode.
The mode can be supported in the driver and in fact it was there.
see the
+static const u8 W83627EHF_PWM_MODE_USER_MAP[] = { 0, 0, 1, 3 };
+static const u8 W83627EHF_PWM_MODE_CHIP_MAP[] = { 1, 2, 4, 3 };
This translates between the former modes:
* 0 Manual mode
* 1 Thermal Cruise
* 2 Fan Speed Cruise
* 3 Smart FAN III
And yes the we must not allow the smartfan III on the fan1 and 3...
TODO:
not allow the SF3 mode on fans without support
check if fan4 is really enabled
You can meet me on IRC freenode.net #linux-sensors
Regards
Rudolf
> That's all until I get through testing,
> David
next prev parent reply other threads:[~2006-03-04 21:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-04 20:59 [lm-sensors] [PATCH] Add fan control support to W83627EHF Rudolf Marek
2006-03-04 21:17 ` David Hubbard
2006-03-04 21:47 ` Rudolf Marek [this message]
2006-03-05 9:52 ` Rudolf Marek
2006-03-05 16:42 ` David Hubbard
2006-03-05 20:05 ` Rudolf Marek
2006-03-05 21:10 ` David Hubbard
2006-03-05 21:14 ` Rudolf Marek
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=440A0AE8.5050604@sh.cvut.cz \
--to=r.marek@sh.cvut.cz \
--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.