The pc87360 driver now support the PC87365 and PC87366 as well,

and can write to registers. Untested.


git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@2427 7894878c-1315-0410-8ee3-d5d059ff63e0
This commit is contained in:
Jean Delvare committed 2004-04-09 18:41:30 +00:00
1 parent 4c32b1a881
commit 2cdac4e54a
5 files changed
+69 -36

No files matched your search

+2
View File
@@ -149,6 +149,8 @@ pc87360
pc87360 - - 2 2 pwm no yes (LPC)
pc87363 - - 2 2 pwm no yes (LPC)
pc87364 - - 3 3 pwm no yes (LPC)
pc87365 - - 3 3 pwm no yes (LPC)
pc87366 - - 3 3 pwm no yes (LPC)
sis5595
sis5595 0-1 4-5 2 - no yes
+6 -5
View File
@@ -40,7 +40,7 @@ is triggered if the rotation speed has dropped below a programmable limit.
Fan readings can be divided by a programmable divider (1, 2, 4 or 8) to give
the readings more range or accuracy. Not all RPM values can accurately be
represented, so some rounding is done. With a divider of 2, the lowest
representable value is around 2600 RPM.
representable value is around 1900 RPM. See doc/fan-divisors for details.
A different alarm is also triggered if the fan speed is too low to be
measured. It is suggested to increase the fan divisor in this case.
@@ -58,7 +58,8 @@ miss once-only alarms.
Limitations
-----------
This driver is read-only at the moment, and only supports fans. Since I
don't own a supported chip for testing, and the datasheet suggests that
you shouldn't change values once the monitoring has started (this is
normally done by the BIOS at boot time), I decided to play it safe.
This driver only supports fans at the moment.
The datasheets suggests that some values (fan mins, fan divisors)
shouldn't be changed once the monitoring has started, but we ignore that
recommendation. We'll reconsider if it actually causes trouble.