blob: f478132b0408afd2671634c78e5b978179c73e53 [file] [log] [blame]
R.Marek@sh.cvut.cz7f15b662005-05-26 12:42:19 +00001Kernel driver lm63
2==================
3
4Supported chips:
Mauro Carvalho Chehabb04f2f72019-04-17 06:46:28 -03005
R.Marek@sh.cvut.cz7f15b662005-05-26 12:42:19 +00006 * National Semiconductor LM63
Mauro Carvalho Chehabb04f2f72019-04-17 06:46:28 -03007
R.Marek@sh.cvut.cz7f15b662005-05-26 12:42:19 +00008 Prefix: 'lm63'
Mauro Carvalho Chehabb04f2f72019-04-17 06:46:28 -03009
R.Marek@sh.cvut.cz7f15b662005-05-26 12:42:19 +000010 Addresses scanned: I2C 0x4c
Mauro Carvalho Chehabb04f2f72019-04-17 06:46:28 -030011
R.Marek@sh.cvut.cz7f15b662005-05-26 12:42:19 +000012 Datasheet: Publicly available at the National Semiconductor website
Mauro Carvalho Chehabb04f2f72019-04-17 06:46:28 -030013
14 http://www.national.com/pf/LM/LM63.html
15
Matthew Garrett10f2ed32010-05-27 19:58:38 +020016 * National Semiconductor LM64
Mauro Carvalho Chehabb04f2f72019-04-17 06:46:28 -030017
Matthew Garrett10f2ed32010-05-27 19:58:38 +020018 Prefix: 'lm64'
Mauro Carvalho Chehabb04f2f72019-04-17 06:46:28 -030019
Matthew Garrett10f2ed32010-05-27 19:58:38 +020020 Addresses scanned: I2C 0x18 and 0x4e
Mauro Carvalho Chehabb04f2f72019-04-17 06:46:28 -030021
Matthew Garrett10f2ed32010-05-27 19:58:38 +020022 Datasheet: Publicly available at the National Semiconductor website
Mauro Carvalho Chehabb04f2f72019-04-17 06:46:28 -030023
24 http://www.national.com/pf/LM/LM64.html
25
Guenter Roeck210961c2012-01-16 22:51:45 +010026 * National Semiconductor LM96163
Mauro Carvalho Chehabb04f2f72019-04-17 06:46:28 -030027
Guenter Roeck210961c2012-01-16 22:51:45 +010028 Prefix: 'lm96163'
Mauro Carvalho Chehabb04f2f72019-04-17 06:46:28 -030029
Guenter Roeck210961c2012-01-16 22:51:45 +010030 Addresses scanned: I2C 0x4c
Mauro Carvalho Chehabb04f2f72019-04-17 06:46:28 -030031
Guenter Roeck210961c2012-01-16 22:51:45 +010032 Datasheet: Publicly available at the National Semiconductor website
Mauro Carvalho Chehabb04f2f72019-04-17 06:46:28 -030033
34 http://www.national.com/pf/LM/LM96163.html
35
R.Marek@sh.cvut.cz7f15b662005-05-26 12:42:19 +000036
Jean Delvare7c81c60f2014-01-29 20:40:08 +010037Author: Jean Delvare <jdelvare@suse.de>
R.Marek@sh.cvut.cz7f15b662005-05-26 12:42:19 +000038
39Thanks go to Tyan and especially Alex Buckingham for setting up a remote
40access to their S4882 test platform for this driver.
Mauro Carvalho Chehabb04f2f72019-04-17 06:46:28 -030041
R.Marek@sh.cvut.cz7f15b662005-05-26 12:42:19 +000042 http://www.tyan.com/
43
44Description
45-----------
46
47The LM63 is a digital temperature sensor with integrated fan monitoring
48and control.
49
50The LM63 is basically an LM86 with fan speed monitoring and control
51capabilities added. It misses some of the LM86 features though:
Mauro Carvalho Chehabb04f2f72019-04-17 06:46:28 -030052
R.Marek@sh.cvut.cz7f15b662005-05-26 12:42:19 +000053 - No low limit for local temperature.
54 - No critical limit for local temperature.
55 - Critical limit for remote temperature can be changed only once. We
56 will consider that the critical limit is read-only.
57
58The datasheet isn't very clear about what the tachometer reading is.
59
60An explanation from National Semiconductor: The two lower bits of the read
61value have to be masked out. The value is still 16 bit in width.
62
63All temperature values are given in degrees Celsius. Resolution is 1.0
64degree for the local temperature, 0.125 degree for the remote temperature.
65
66The fan speed is measured using a tachometer. Contrary to most chips which
67store the value in an 8-bit register and have a selectable clock divider
68to make sure that the result will fit in the register, the LM63 uses 16-bit
69value for measuring the speed of the fan. It can measure fan speeds down to
7083 RPM, at least in theory.
71
72Note that the pin used for fan monitoring is shared with an alert out
73function. Depending on how the board designer wanted to use the chip, fan
74speed monitoring will or will not be possible. The proper chip configuration
Jean Delvare409c0b52012-01-16 22:51:46 +010075is left to the BIOS, and the driver will blindly trust it. Only the original
76LM63 suffers from this limitation, the LM64 and LM96163 have separate pins
77for fan monitoring and alert out. On the LM64, monitoring is always enabled;
78on the LM96163 it can be disabled.
R.Marek@sh.cvut.cz7f15b662005-05-26 12:42:19 +000079
80A PWM output can be used to control the speed of the fan. The LM63 has two
81PWM modes: manual and automatic. Automatic mode is not fully implemented yet
82(you cannot define your custom PWM/temperature curve), and mode change isn't
83supported either.
84
Guenter Roeck04738b22012-01-16 22:51:46 +010085The lm63 driver will not update its values more frequently than configured with
86the update_interval sysfs attribute; reading them more often will do no harm,
Jean Delvared216f682012-01-16 22:51:47 +010087but will return 'old' values. Values in the automatic fan control lookup table
88(attributes pwm1_auto_*) have their own independent lifetime of 5 seconds.
R.Marek@sh.cvut.cz7f15b662005-05-26 12:42:19 +000089
Matthew Garrett10f2ed32010-05-27 19:58:38 +020090The LM64 is effectively an LM63 with GPIO lines. The driver does not
91support these GPIO lines at present.
Guenter Roeck210961c2012-01-16 22:51:45 +010092
93The LM96163 is an enhanced version of LM63 with improved temperature accuracy
Guenter Roeckf496b2d2012-01-16 22:51:46 +010094and better PWM resolution. For LM96163, the external temperature sensor type is
95configurable as CPU embedded diode(1) or 3904 transistor(2).