apfs/linux-apfs
0
0
Fork 0
mirror of https://github.com/linux-apfs/linux-apfs.git synced 2026-05-01 15:00:59 -07:00
Code Issues Packages Projects Releases Wiki Activity

hwmon: (ds1621) Remove detect function

Browse Source 
Due to a lack of device and vendor identification registers, the
Dallas/Maxim DS16xx devices cannot be uniquely detected, sometimes
resulting in false positives. Therefore, the detect function is
being removed in favor of explicit device instantiation.

Signed-off-by: Robert Coulson <rob.coulson@gmail.com>
Acked-by: Jean Delvare <khali@linux-fr.org>
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
This commit is contained in:
Robert Coulson
2013-05-23 09:22:22 -07:00
committed by Guenter Roeck
parent 79c1cc1c90
commit ed7c34e89d
2 changed files with 12 additions and 61 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Documentation/hwmon/ds1621
+12 -13
View File
@@ -4,24 +4,22 @@ Kernel driver ds1621
Supported chips:
* Dallas Semiconductor / Maxim Integrated DS1621
Prefix: 'ds1621'
Addresses scanned: I2C 0x48 - 0x4f
Addresses scanned: none
Datasheet: Publicly available from www.maximintegrated.com
* Dallas Semiconductor DS1625
Prefix:
'ds1621' - if binding via _detect function
'ds1625' - explicit instantiation
Addresses scanned: I2C 0x48 - 0x4f
Prefix: 'ds1625'
Addresses scanned: none
Datasheet: Publicly available from www.datasheetarchive.com
* Maxim Integrated DS1631
Prefix: 'ds1631'
Addresses scanned: I2C 0x48 - 0x4f
Addresses scanned: none
Datasheet: Publicly available from www.maximintegrated.com
* Maxim Integrated DS1721
Prefix: 'ds1721'
Addresses scanned: I2C 0x48 - 0x4f
Addresses scanned: none
Datasheet: Publicly available from www.maximintegrated.com
Authors:
@@ -77,12 +75,13 @@ The DS1625 is pin compatible and functionally equivalent with the DS1621,
but the DS1621 is meant to replace it. The DS1631 and DS1721 are also
pin compatible with the DS1621, but provide multi-resolution support.
Since there is no version register, there is no unique identification
for these devices. In addition, the DS1631 and DS1721 will emulate a
DS1621 device, if not explicitly instantiated (why? because the detect
function compares the temperature register values bits and checks for a
9-bit resolution). Therefore, for correct device identification and
functionality, explicit device instantiation is required.
Since there is no version or vendor identification register, there is
no unique identification for these devices. Therefore, explicit device
instantiation is required for correct device identification and functionality.
And, for correct identification and operation, each device must be
explicitly instantiated, one device per address, in this address
range: 0x48..0x4f.
The DS1721 is pin compatible with the DS1621, has an accuracy of +/- 1.0
degree Celsius over a -10 to +85 degree range, a minimum/maximum alarm