| commit | cf6b9ea661ef4f20b4a4cba1a232a732339aae2c | |
| author | Jean Delvare <khali@linux-fr.org> | |
| Mon, 15 Nov 2010 20:38:56 +0000 (15 21:38 +0100) | ||
| committer | Jean Delvare <khali@endymion.delvare> | |
| Mon, 15 Nov 2010 20:38:56 +0000 (15 21:38 +0100) | ||
| tree | d12db9d301146d533120686d7da1bf84a3068c0a | treesnapshot (tar.gz zip) |
| parent | 2a2d27da00250c9f117e35653ed5a6a3212e5d77 | commitdiff |
hwmon: (w83795) Read the intrusion state properly
We can't read the intrusion state from the real-time alarm registers
as we do for all other alarm flags, because real-time alarm bits don't
stick (by definition) and the intrusion state has to stick until
explicitly cleared (otherwise it has little value.)
So we have to use the interrupt status register instead, which is read
from the same address but with a configuration bit flipped in another
register.
Signed-off-by: Jean Delvare <khali@linux-fr.org>
Acked-by: Guenter Roeck <guenter.roeck@ericsson.com>
We can't read the intrusion state from the real-time alarm registers
as we do for all other alarm flags, because real-time alarm bits don't
stick (by definition) and the intrusion state has to stick until
explicitly cleared (otherwise it has little value.)
So we have to use the interrupt status register instead, which is read
from the same address but with a configuration bit flipped in another
register.
Signed-off-by: Jean Delvare <khali@linux-fr.org>
Acked-by: Guenter Roeck <guenter.roeck@ericsson.com>
| drivers/hwmon/w83795.c | diffblobblamehistory |