diff options
author | Chu Lin <linchuyuan@google.com> | 2020-06-23 22:13:08 +0000 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2020-07-09 09:35:56 +0200 |
commit | 25c99651712a17cd34da036498691cdf77c80a32 (patch) | |
tree | f62d3e08e84f7c596a3cc07fe4d485a05df26417 /net/sched | |
parent | 69d3042df6648ab5af973189edb380864b470d3c (diff) | |
download | linux-stable-25c99651712a17cd34da036498691cdf77c80a32.tar.gz linux-stable-25c99651712a17cd34da036498691cdf77c80a32.tar.bz2 linux-stable-25c99651712a17cd34da036498691cdf77c80a32.zip |
hwmon: (max6697) Make sure the OVERT mask is set correctly
[ Upstream commit 016983d138cbe99a5c0aaae0103ee88f5300beb3 ]
Per the datasheet for max6697, OVERT mask and ALERT mask are different.
For example, the 7th bit of OVERT is the local channel but for alert
mask, the 6th bit is the local channel. Therefore, we can't apply the
same mask for both registers. In addition to that, the max6697 driver
is supposed to be compatibale with different models. I manually went over
all the listed chips and made sure all chip types have the same layout.
Testing;
mask value of 0x9 should map to 0x44 for ALERT and 0x84 for OVERT.
I used iotool to read the reg value back to verify. I only tested this
change on max6581.
Reference:
https://datasheets.maximintegrated.com/en/ds/MAX6581.pdf
https://datasheets.maximintegrated.com/en/ds/MAX6697.pdf
https://datasheets.maximintegrated.com/en/ds/MAX6699.pdf
Signed-off-by: Chu Lin <linchuyuan@google.com>
Fixes: 5372d2d71c46e ("hwmon: Driver for Maxim MAX6697 and compatibles")
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'net/sched')
0 files changed, 0 insertions, 0 deletions