Bug 197167
Summary: | tmp102: Initial read is invalid | ||
---|---|---|---|
Product: | Drivers | Reporter: | ralf.goebel |
Component: | Hardware Monitoring | Assignee: | Guenter Roeck (linux) |
Status: | RESOLVED CODE_FIX | ||
Severity: | normal | CC: | eduardo.valentin, linux, nm, rui.zhang |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 4.9.28 | Subsystem: | |
Regression: | Yes | Bisected commit-id: |
Description
ralf.goebel
2017-10-09 07:08:52 UTC
Commit 3d8f7a89a197 ("hwmon: (tmp102) Improve handling of initial read delay") would be my prime suspect. Guenter? My workaround using bit 0 of the temperature register doesn't seem to work. Bit 0 turns to 1 as soon as the 13-bit mode is activated, even if the contents are still 12 bits. Yes, I guess it is 3d8f7a89a197. That commit sets the wait period only if the chip was shut down, but it appears that it is also needed if the resolution changes. I'll check the datasheet tonight to confirm and submit a patch. Fixed by commit d0725439354a58f2b13b9f5234420641b662b9c4 Author: Guenter Roeck Date: Mon Oct 23 17:36:03 2017 -0700 hwmon: (tmp102) Fix first temperature reading |