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 * Texas Instruments TMP461
272 Addresses scanned: I2C 0x48 through 0x4F
274 Datasheet: Publicly available at TI website
276 https://www.ti.com/lit/gpn/tmp461
278 Author: Jean Delvare <jdelvare@suse.de>
284 The LM90 is a digital temperature sensor. It senses its own temperature as
285 well as the temperature of up to one external diode. It is compatible
286 with many other devices, many of which are supported by this driver.
288 Note that there is no easy way to differentiate between the MAX6657,
289 MAX6658 and MAX6659 variants. The extra features of the MAX6659 are only
290 supported by this driver if the chip is located at address 0x4d or 0x4e,
291 or if the chip type is explicitly selected as max6659.
292 The MAX6680 and MAX6681 only differ in their pinout, therefore they obviously
293 can't (and don't need to) be distinguished.
295 The specificity of this family of chipsets over the ADM1021/LM84
296 family is that it features critical limits with hysteresis, and an
297 increased resolution of the remote temperature measurement.
299 The different chipsets of the family are not strictly identical, although
300 very similar. For reference, here comes a non-exhaustive list of specific
304 * Filter and alert configuration register at 0xBF.
305 * ALERT is triggered by temperatures over critical limits.
309 * Better external channel accuracy
313 * External temperature shifted by 16 degrees down
316 * Consecutive alert register at 0x22.
317 * Conversion averaging.
318 * Up to 64 conversions/s.
319 * ALERT is triggered by open remote sensor.
320 * SMBus PEC support for Write Byte and Receive Byte transactions.
322 ADT7461, ADT7461A, NCT1008:
323 * Extended temperature range (breaks compatibility)
324 * Lower resolution for remote temperature
327 * Better local resolution
329 * Remote sensor type selection
330 * Extended temperature range
331 * Extended resolution only available when conversion rate <= 1 Hz
334 * Better local resolution
335 * Remote sensor type selection
338 * Better local resolution
340 * Second critical temperature limit
341 * Remote sensor type selection
345 * Remote sensor type selection
348 * Better local resolution
349 * Selectable address (max6696)
350 * Second critical temperature limit
354 * The G variant is lead-free, otherwise similar to the W.
355 * Filter and alert configuration register at 0xBF
356 * Moving average (depending on conversion rate)
359 * Successor of the W83L771W/G, same features.
360 * The AWG and ASG variants only differ in package format.
361 * Diode ideality factor configuration (remote sensor) at 0xE3
364 * Better local resolution
366 All temperature values are given in degrees Celsius. Resolution
367 is 1.0 degree for the local temperature, 0.125 degree for the remote
368 temperature, except for the MAX6654, MAX6657, MAX6658 and MAX6659 which have
369 a resolution of 0.125 degree for both temperatures.
371 Each sensor has its own high and low limits, plus a critical limit.
372 Additionally, there is a relative hysteresis value common to both critical
373 values. To make life easier to user-space applications, two absolute values
374 are exported, one for each channel, but these values are of course linked.
375 Only the local hysteresis can be set from user-space, and the same delta
376 applies to the remote hysteresis.
378 The lm90 driver will not update its values more frequently than configured with
379 the update_interval attribute; reading them more often will do no harm, but will
385 This driver has basic support for SMBus alert. When an alert is received,
386 the status register is read and the faulty temperature channel is logged.
388 The Analog Devices chips (ADM1032, ADT7461 and ADT7461A) and ON
389 Semiconductor chips (NCT1008) do not implement the SMBus alert protocol
390 properly so additional care is needed: the ALERT output is disabled when
391 an alert is received, and is re-enabled only when the alarm is gone.
392 Otherwise the chip would block alerts from other chips in the bus as long
393 as the alarm is active.
398 The ADM1032 is the only chip of the family which supports PEC. It does
399 not support PEC on all transactions though, so some care must be taken.
401 When reading a register value, the PEC byte is computed and sent by the
402 ADM1032 chip. However, in the case of a combined transaction (SMBus Read
403 Byte), the ADM1032 computes the CRC value over only the second half of
404 the message rather than its entirety, because it thinks the first half
405 of the message belongs to a different transaction. As a result, the CRC
406 value differs from what the SMBus master expects, and all reads fail.
408 For this reason, the lm90 driver will enable PEC for the ADM1032 only if
409 the bus supports the SMBus Send Byte and Receive Byte transaction types.
410 These transactions will be used to read register values, instead of
411 SMBus Read Byte, and PEC will work properly.
413 Additionally, the ADM1032 doesn't support SMBus Send Byte with PEC.
414 Instead, it will try to write the PEC value to the register (because the
415 SMBus Send Byte transaction with PEC is similar to a Write Byte transaction
416 without PEC), which is not what we want. Thus, PEC is explicitly disabled
417 on SMBus Send Byte transactions in the lm90 driver.
419 PEC on byte data transactions represents a significant increase in bandwidth
420 usage (+33% for writes, +25% for reads) in normal conditions. With the need
421 to use two SMBus transaction for reads, this overhead jumps to +50%. Worse,
422 two transactions will typically mean twice as much delay waiting for
423 transaction completion, effectively doubling the register cache refresh time.
424 I guess reliability comes at a price, but it's quite expensive this time.
426 So, as not everyone might enjoy the slowdown, PEC can be disabled through
427 sysfs. Just write 0 to the "pec" file and PEC will be disabled. Write 1
428 to that file to enable PEC again.