aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/early-userspace
diff options
context:
space:
mode:
authorJean Delvare <khali@linux-fr.org>2008-10-26 17:04:39 +0100
committerJean Delvare <khali@linux-fr.org>2008-10-26 17:04:39 +0100
commitec38fa2b35f13e7fa1d676a5bc997d0df1b02574 (patch)
treedf2ffd6eb0af65516cf0aae37c80c9fd1eee5dc6 /Documentation/early-userspace
parent1b871826b3dfcdcd78140d17c00e452eec6c12a4 (diff)
downloadkernel_samsung_tuna-ec38fa2b35f13e7fa1d676a5bc997d0df1b02574.zip
kernel_samsung_tuna-ec38fa2b35f13e7fa1d676a5bc997d0df1b02574.tar.gz
kernel_samsung_tuna-ec38fa2b35f13e7fa1d676a5bc997d0df1b02574.tar.bz2
hwmon: (lm90) Fix handling of hysteresis value
There are several problems in the way the hysteresis value is handled by the lm90 driver: * In show_temphyst(), specific handling of the MAX6646 is missing, so the hysteresis is reported incorrectly if the critical temperature is over 127 degrees C. * In set_temphyst(), the new hysteresis register value is written to the chip but data->temp_hyst isn't updated accordingly, so there is a short period of time (up to 2 seconds) where the old hystereris value will be returned while the new one is already active. * In set_temphyst(), the critical temperature which is used as a base to compute the value of the hysteresis register lacks device-specific handling. As a result, the value of the hysteresis register might be incorrect for the ADT7461 and MAX6646 chips. Fix these 3 bugs. Signed-off-by: Jean Delvare <khali@linux-fr.org> Cc: Ben Hutchings <bhutchings@solarflare.com> Cc: Nate Case <ncase@xes-inc.com>
Diffstat (limited to 'Documentation/early-userspace')
0 files changed, 0 insertions, 0 deletions