6 * National Semiconductor LM90
10 Addresses scanned: I2C 0x4c
12 Datasheet: Publicly available at the National Semiconductor website
14 http://www.national.com/pf/LM/LM90.html
16 * National Semiconductor LM89
18 Prefix: 'lm89' (no auto-detection)
20 Addresses scanned: I2C 0x4c and 0x4d
22 Datasheet: Publicly available at the National Semiconductor website
24 http://www.national.com/mpf/LM/LM89.html
26 * National Semiconductor LM99
30 Addresses scanned: I2C 0x4c and 0x4d
32 Datasheet: Publicly available at the National Semiconductor website
34 http://www.national.com/pf/LM/LM99.html
36 * National Semiconductor LM86
40 Addresses scanned: I2C 0x4c
42 Datasheet: Publicly available at the National Semiconductor website
44 http://www.national.com/mpf/LM/LM86.html
46 * Analog Devices ADM1032
50 Addresses scanned: I2C 0x4c and 0x4d
52 Datasheet: Publicly available at the ON Semiconductor website
54 https://www.onsemi.com/PowerSolutions/product.do?id=ADM1032
56 * Analog Devices ADT7461
60 Addresses scanned: I2C 0x4c and 0x4d
62 Datasheet: Publicly available at the ON Semiconductor website
64 https://www.onsemi.com/PowerSolutions/product.do?id=ADT7461
66 * Analog Devices ADT7461A
70 Addresses scanned: I2C 0x4c and 0x4d
72 Datasheet: Publicly available at the ON Semiconductor website
74 https://www.onsemi.com/PowerSolutions/product.do?id=ADT7461A
76 * ON Semiconductor NCT1008
80 Addresses scanned: I2C 0x4c and 0x4d
82 Datasheet: Publicly available at the ON Semiconductor website
84 https://www.onsemi.com/PowerSolutions/product.do?id=NCT1008
90 Addresses scanned: I2C 0x4d
92 Datasheet: Publicly available at the Maxim website
94 http://www.maxim-ic.com/quick_view2.cfm/qv_pk/3497
100 Addresses scanned: I2C 0x4e
102 Datasheet: Publicly available at the Maxim website
104 http://www.maxim-ic.com/quick_view2.cfm/qv_pk/3497
110 Addresses scanned: I2C 0x4c
112 Datasheet: Publicly available at the Maxim website
114 http://www.maxim-ic.com/quick_view2.cfm/qv_pk/3500
120 Addresses scanned: I2C 0x4c
122 Datasheet: Publicly available at the Maxim website
124 http://www.maxim-ic.com/quick_view2.cfm/qv_pk/3497
130 Addresses scanned: I2C 0x18, 0x19, 0x1a, 0x29, 0x2a, 0x2b,
134 Datasheet: Publicly available at the Maxim website
136 https://www.maximintegrated.com/en/products/sensors/MAX6654.html
142 Addresses scanned: I2C 0x4c
144 Datasheet: Publicly available at the Maxim website
146 http://www.maxim-ic.com/quick_view2.cfm/qv_pk/2578
152 Addresses scanned: I2C 0x4c
154 Datasheet: Publicly available at the Maxim website
156 http://www.maxim-ic.com/quick_view2.cfm/qv_pk/2578
162 Addresses scanned: I2C 0x4c, 0x4d, 0x4e
164 Datasheet: Publicly available at the Maxim website
166 http://www.maxim-ic.com/quick_view2.cfm/qv_pk/2578
172 Addresses scanned: I2C 0x18, 0x19, 0x1a, 0x29, 0x2a, 0x2b,
176 Datasheet: Publicly available at the Maxim website
178 http://www.maxim-ic.com/quick_view2.cfm/qv_pk/3370
184 Addresses scanned: I2C 0x18, 0x19, 0x1a, 0x29, 0x2a, 0x2b,
188 Datasheet: Publicly available at the Maxim website
190 http://www.maxim-ic.com/quick_view2.cfm/qv_pk/3370
196 Addresses scanned: I2C 0x4c
198 Datasheet: Publicly available at the Maxim website
200 http://www.maxim-ic.com/quick_view2.cfm/qv_pk/3500
206 Addresses scanned: I2C 0x18
208 Datasheet: Publicly available at the Maxim website
210 http://www.maxim-ic.com/datasheet/index.mvp/id/4199
216 Addresses scanned: I2C 0x18, 0x19, 0x1a, 0x29, 0x2a, 0x2b,
220 Datasheet: Publicly available at the Maxim website
222 http://www.maxim-ic.com/datasheet/index.mvp/id/4199
224 * Winbond/Nuvoton W83L771W/G
228 Addresses scanned: I2C 0x4c
230 Datasheet: No longer available
232 * Winbond/Nuvoton W83L771AWG/ASG
236 Addresses scanned: I2C 0x4c
238 Datasheet: Not publicly available, can be requested from Nuvoton
240 * Philips/NXP SA56004X
244 Addresses scanned: I2C 0x48 through 0x4F
246 Datasheet: Publicly available at NXP website
248 http://ics.nxp.com/products/interface/datasheet/sa56004x.pdf
254 Addresses scanned: I2C 0x4c, 0x4d
256 Datasheet: Not publicly available from GMT
258 * Texas Instruments TMP451
262 Addresses scanned: I2C 0x4c
264 Datasheet: Publicly available at TI website
266 https://www.ti.com/litv/pdf/sbos686
268 Author: Jean Delvare <jdelvare@suse.de>
274 The LM90 is a digital temperature sensor. It senses its own temperature as
275 well as the temperature of up to one external diode. It is compatible
276 with many other devices, many of which are supported by this driver.
278 Note that there is no easy way to differentiate between the MAX6657,
279 MAX6658 and MAX6659 variants. The extra features of the MAX6659 are only
280 supported by this driver if the chip is located at address 0x4d or 0x4e,
281 or if the chip type is explicitly selected as max6659.
282 The MAX6680 and MAX6681 only differ in their pinout, therefore they obviously
283 can't (and don't need to) be distinguished.
285 The specificity of this family of chipsets over the ADM1021/LM84
286 family is that it features critical limits with hysteresis, and an
287 increased resolution of the remote temperature measurement.
289 The different chipsets of the family are not strictly identical, although
290 very similar. For reference, here comes a non-exhaustive list of specific
294 * Filter and alert configuration register at 0xBF.
295 * ALERT is triggered by temperatures over critical limits.
299 * Better external channel accuracy
303 * External temperature shifted by 16 degrees down
306 * Consecutive alert register at 0x22.
307 * Conversion averaging.
308 * Up to 64 conversions/s.
309 * ALERT is triggered by open remote sensor.
310 * SMBus PEC support for Write Byte and Receive Byte transactions.
312 ADT7461, ADT7461A, NCT1008:
313 * Extended temperature range (breaks compatibility)
314 * Lower resolution for remote temperature
317 * Better local resolution
319 * Remote sensor type selection
320 * Extended temperature range
321 * Extended resolution only available when conversion rate <= 1 Hz
324 * Better local resolution
325 * Remote sensor type selection
328 * Better local resolution
330 * Second critical temperature limit
331 * Remote sensor type selection
335 * Remote sensor type selection
338 * Better local resolution
339 * Selectable address (max6696)
340 * Second critical temperature limit
344 * The G variant is lead-free, otherwise similar to the W.
345 * Filter and alert configuration register at 0xBF
346 * Moving average (depending on conversion rate)
349 * Successor of the W83L771W/G, same features.
350 * The AWG and ASG variants only differ in package format.
351 * Diode ideality factor configuration (remote sensor) at 0xE3
354 * Better local resolution
356 All temperature values are given in degrees Celsius. Resolution
357 is 1.0 degree for the local temperature, 0.125 degree for the remote
358 temperature, except for the MAX6654, MAX6657, MAX6658 and MAX6659 which have
359 a resolution of 0.125 degree for both temperatures.
361 Each sensor has its own high and low limits, plus a critical limit.
362 Additionally, there is a relative hysteresis value common to both critical
363 values. To make life easier to user-space applications, two absolute values
364 are exported, one for each channel, but these values are of course linked.
365 Only the local hysteresis can be set from user-space, and the same delta
366 applies to the remote hysteresis.
368 The lm90 driver will not update its values more frequently than configured with
369 the update_interval attribute; reading them more often will do no harm, but will
375 This driver has basic support for SMBus alert. When an alert is received,
376 the status register is read and the faulty temperature channel is logged.
378 The Analog Devices chips (ADM1032, ADT7461 and ADT7461A) and ON
379 Semiconductor chips (NCT1008) do not implement the SMBus alert protocol
380 properly so additional care is needed: the ALERT output is disabled when
381 an alert is received, and is re-enabled only when the alarm is gone.
382 Otherwise the chip would block alerts from other chips in the bus as long
383 as the alarm is active.
388 The ADM1032 is the only chip of the family which supports PEC. It does
389 not support PEC on all transactions though, so some care must be taken.
391 When reading a register value, the PEC byte is computed and sent by the
392 ADM1032 chip. However, in the case of a combined transaction (SMBus Read
393 Byte), the ADM1032 computes the CRC value over only the second half of
394 the message rather than its entirety, because it thinks the first half
395 of the message belongs to a different transaction. As a result, the CRC
396 value differs from what the SMBus master expects, and all reads fail.
398 For this reason, the lm90 driver will enable PEC for the ADM1032 only if
399 the bus supports the SMBus Send Byte and Receive Byte transaction types.
400 These transactions will be used to read register values, instead of
401 SMBus Read Byte, and PEC will work properly.
403 Additionally, the ADM1032 doesn't support SMBus Send Byte with PEC.
404 Instead, it will try to write the PEC value to the register (because the
405 SMBus Send Byte transaction with PEC is similar to a Write Byte transaction
406 without PEC), which is not what we want. Thus, PEC is explicitly disabled
407 on SMBus Send Byte transactions in the lm90 driver.
409 PEC on byte data transactions represents a significant increase in bandwidth
410 usage (+33% for writes, +25% for reads) in normal conditions. With the need
411 to use two SMBus transaction for reads, this overhead jumps to +50%. Worse,
412 two transactions will typically mean twice as much delay waiting for
413 transaction completion, effectively doubling the register cache refresh time.
414 I guess reliability comes at a price, but it's quite expensive this time.
416 So, as not everyone might enjoy the slowdown, PEC can be disabled through
417 sysfs. Just write 0 to the "pec" file and PEC will be disabled. Write 1
418 to that file to enable PEC again.