Update the docs accordingly.
Rename PWM registers so that it is clearer which chip uses them.
Remove outdated comments.
Fix the name in the w83627hf_driver structure.
Fix reserved register and PWM bits being written to on the W83627THF.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@2290 7894878c-1315-0410-8ee3-d5d059ff63e0
chip, but we'll guess that GPIO5 are used for this purpose. It's
correct for (at least) Asus P4C800-E, and if it's wrong for any
others then we're no worse off. Also, switch to using common LM75
conversion functions.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@2151 7894878c-1315-0410-8ee3-d5d059ff63e0
Michael Hufer <michael.hufer@freenet.de>
------------------------
> First, I added a new mod parameter "reset_it87" which controls whether
> or not the chip is reset on module load (modprobe it87 reset_it=1,
> default) or not(modprobe it87 reset_it87=0).
> Since this worked out quiet nicely I decided to go one step further
> and also add the chips manual and automatic temperature controlled fan
> speed features (PWM etc.).
>
> Finally I also updated the doc to document the new features.
>
> Attached is a diff against the current cvs version.
------------------------
Subject:
Re: fan speed for it87?? chips added
Date:
Fri, 26 Sep 2003 23:28:35 +0200
From:
Michael Hufer <michael.hufer@freenet.de>
To:
sensors@Stimpy.netroedge.com, Jean Delvare <khali@linux-fr.org>
On Friday 26 September 2003 22:40, Jean Delvare wrote:
> > I found and fixed the little problem I had with the original chip
> > initialization. I can now load the module with reset_it87=0 and
> > init=1 without messing up the settings of the power supply fan
> > from the BIOS. It was quite simple after all.
>
> I'm interested in details, can you tell us what it was?
Sure, it actually was something I introduced myself :-(. I initialized the
fan_ctl register with (read_value & 0x8f | 0x77) to enable the smart
guardian feature for all 3 fans. But the power supply fan does not support
pwm. It can only be operated in on/off mode, i.e. bit 0 must be clear. I
switched it back to the original (rv & 0x8f | 0x70 ) and everything is back
to working.
> > Do you want me to send the latest diff?
>
> Sure I want.
Here it comes.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@2033 7894878c-1315-0410-8ee3-d5d059ff63e0
Mainly targetted (and tested) with the 6651, but should work with
the MAX6550.
See doc/chips/max6650 for notes, bugs, assumptions, etc.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@1987 7894878c-1315-0410-8ee3-d5d059ff63e0
Add half a dozen new features.
Add checksum parameter (same as for the eeprom module)
Fix monitor limits
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@1934 7894878c-1315-0410-8ee3-d5d059ff63e0
This patch fixes a race condition in the lm85 driver and adds support for the
SMC EMC6D100 and EMC6D101. The EMC6D100 and 101 chips have some additional
features that *are not* currently implemented in the driver, but the chip is
detected (by sensors-detect and the lm85 driver).
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@1740 7894878c-1315-0410-8ee3-d5d059ff63e0
Jean Delvare