diff options
| author | Alvaro G. M <alvaro.gamez@hazent.com> | 2018-03-21 16:04:52 +0100 |
|---|---|---|
| committer | Guenter Roeck <linux@roeck-us.net> | 2018-03-22 09:32:05 -0700 |
| commit | 05993e226ad997682929dec2c42477d5e3e6c274 (patch) | |
| tree | cf271dc92ae6b750b80c48618851d86a29cd94c0 /Documentation/hwmon | |
| parent | 72816cb06e7153c22aed8776949f558b635aa2c0 (diff) | |
hwmon: (lm92) Do not try to detect MAX6635
Maxim MAX663x family are mostly compatible with LM92, but they lack any
identification register. Weakening the detect function would make it prone
to false positives, and current one doesn't detect all chips. Therefore,
the detect function for max6635 devices is removed in favor of explicit
device instatiation.
Signed-off-by: Alvaro Gamez Machado <alvaro.gamez@hazent.com>
Reviewed-by: Jean Delvare <jdelvare@suse.de>
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
Diffstat (limited to 'Documentation/hwmon')
| -rw-r--r-- | Documentation/hwmon/lm92 | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/Documentation/hwmon/lm92 b/Documentation/hwmon/lm92 index 22f68ad032cf..f2a5adcf4ead 100644 --- a/Documentation/hwmon/lm92 +++ b/Documentation/hwmon/lm92 @@ -12,9 +12,7 @@ Supported chips: Datasheet: http://www.national.com/pf/LM/LM76.html * Maxim MAX6633/MAX6634/MAX6635 Prefix: 'lm92' - Addresses scanned: I2C 0x48 - 0x4b - MAX6633 with address in 0x40 - 0x47, 0x4c - 0x4f needs force parameter - and MAX6634 with address in 0x4c - 0x4f needs force parameter + Addresses scanned: none, force parameter needed Datasheet: http://www.maxim-ic.com/quick_view2.cfm/qv_pk/3074 Authors: |