2005-05-26 12:42:19 +00:00
|
|
|
Kernel driver smsc47m1
|
|
|
|
======================
|
|
|
|
|
|
|
|
Supported chips:
|
2019-04-17 09:46:28 +00:00
|
|
|
|
2006-10-08 20:00:44 +00:00
|
|
|
* SMSC LPC47B27x, LPC47M112, LPC47M10x, LPC47M13x, LPC47M14x,
|
2019-04-17 09:46:28 +00:00
|
|
|
|
2006-10-08 20:00:44 +00:00
|
|
|
LPC47M15x and LPC47M192
|
2019-04-17 09:46:28 +00:00
|
|
|
|
2005-05-26 12:42:19 +00:00
|
|
|
Addresses scanned: none, address read from Super I/O config space
|
2019-04-17 09:46:28 +00:00
|
|
|
|
2005-05-26 12:42:19 +00:00
|
|
|
Prefix: 'smsc47m1'
|
2019-04-17 09:46:28 +00:00
|
|
|
|
2005-05-26 12:42:19 +00:00
|
|
|
Datasheets:
|
2019-04-17 09:46:28 +00:00
|
|
|
|
|
|
|
http://www.smsc.com/media/Downloads_Public/Data_Sheets/47b272.pdf
|
|
|
|
|
|
|
|
http://www.smsc.com/media/Downloads_Public/Data_Sheets/47m10x.pdf
|
|
|
|
|
|
|
|
http://www.smsc.com/media/Downloads_Public/Data_Sheets/47m112.pdf
|
|
|
|
|
|
|
|
http://www.smsc.com/
|
|
|
|
|
2007-05-08 15:21:59 +00:00
|
|
|
* SMSC LPC47M292
|
2019-04-17 09:46:28 +00:00
|
|
|
|
2007-05-08 15:21:59 +00:00
|
|
|
Addresses scanned: none, address read from Super I/O config space
|
2019-04-17 09:46:28 +00:00
|
|
|
|
2007-05-08 15:21:59 +00:00
|
|
|
Prefix: 'smsc47m2'
|
2019-04-17 09:46:28 +00:00
|
|
|
|
2007-05-08 15:21:59 +00:00
|
|
|
Datasheet: Not public
|
2019-04-17 09:46:28 +00:00
|
|
|
|
2005-10-26 20:21:24 +00:00
|
|
|
* SMSC LPC47M997
|
2019-04-17 09:46:28 +00:00
|
|
|
|
2005-10-26 20:21:24 +00:00
|
|
|
Addresses scanned: none, address read from Super I/O config space
|
2019-04-17 09:46:28 +00:00
|
|
|
|
2005-10-26 20:21:24 +00:00
|
|
|
Prefix: 'smsc47m1'
|
2019-04-17 09:46:28 +00:00
|
|
|
|
2005-10-26 20:21:24 +00:00
|
|
|
Datasheet: none
|
2005-05-26 12:42:19 +00:00
|
|
|
|
2019-04-17 09:46:28 +00:00
|
|
|
|
|
|
|
|
2005-05-26 12:42:19 +00:00
|
|
|
Authors:
|
2019-04-17 09:46:28 +00:00
|
|
|
|
|
|
|
- Mark D. Studebaker <mdsxyz123@yahoo.com>,
|
|
|
|
- With assistance from Bruce Allen <ballen@uwm.edu>, and his
|
|
|
|
fan.c program:
|
|
|
|
|
|
|
|
- http://www.lsc-group.phys.uwm.edu/%7Eballen/driver/
|
|
|
|
|
|
|
|
- Gabriele Gorla <gorlik@yahoo.com>,
|
|
|
|
- Jean Delvare <jdelvare@suse.de>
|
2005-05-26 12:42:19 +00:00
|
|
|
|
|
|
|
Description
|
|
|
|
-----------
|
|
|
|
|
|
|
|
The Standard Microsystems Corporation (SMSC) 47M1xx Super I/O chips
|
|
|
|
contain monitoring and PWM control circuitry for two fans.
|
|
|
|
|
2007-05-08 15:21:59 +00:00
|
|
|
The LPC47M15x, LPC47M192 and LPC47M292 chips contain a full 'hardware
|
|
|
|
monitoring block' in addition to the fan monitoring and control. The
|
|
|
|
hardware monitoring block is not supported by this driver, use the
|
|
|
|
smsc47m192 driver for that.
|
2005-05-26 12:42:19 +00:00
|
|
|
|
2005-10-26 20:21:24 +00:00
|
|
|
No documentation is available for the 47M997, but it has the same device
|
|
|
|
ID as the 47M15x and 47M192 chips and seems to be compatible.
|
|
|
|
|
2005-05-26 12:42:19 +00:00
|
|
|
Fan rotation speeds are reported in RPM (rotations per minute). An alarm 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.
|
|
|
|
|
|
|
|
PWM values are from 0 to 255.
|
|
|
|
|
|
|
|
If an alarm triggers, it will remain triggered until the hardware register
|
|
|
|
is read at least once. This means that the cause for the alarm may
|
|
|
|
already have disappeared! Note that in the current implementation, all
|
|
|
|
hardware registers are read whenever any data is read (unless it is less
|
|
|
|
than 1.5 seconds since the last update). This means that you can easily
|
|
|
|
miss once-only alarms.
|
|
|
|
|
2019-04-17 09:46:28 +00:00
|
|
|
------------------------------------------------------------------
|
2005-05-26 12:42:19 +00:00
|
|
|
|
|
|
|
The lm_sensors project gratefully acknowledges the support of
|
|
|
|
Intel in the development of this driver.
|