From: Guenter Roeck <linux@roeck-us.net>
To: Tzung-Bi Shih <tzungbi@kernel.org>
Cc: linux-hwmon@vger.kernel.org
Subject: Re: [PATCH 1/2] hwmon: (max6697) Fix swapped temp{1,8} critical alarms
Date: Sun, 14 Jul 2024 11:47:59 -0700 [thread overview]
Message-ID: <4190de32-d0e1-4884-8823-e993bc4d054e@roeck-us.net> (raw)
In-Reply-To: <ZpN5A1SzNkw1xUDK@tzungbi-laptop>
On 7/14/24 00:06, Tzung-Bi Shih wrote:
> On Sat, Jul 13, 2024 at 02:34:01PM -0700, Guenter Roeck wrote:
>> The critical alarm bit for the local temperature sensor (temp1) is in
>> bit 7 of register 0x45 (not bit 6), and the critical alarm bit for remote
>> temperature sensor 7 (temp8) is in bit 6 (not bit 7).
>>
>> This only affects MAX6581 since all other chips supported by this driver
>> do not support those critical alarms.
>>
>> Fixes: 5372d2d71c46 ("hwmon: Driver for Maxim MAX6697 and compatibles")
>> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
>
> Double checked with the datasheet[1],
I checked this several times because I couldn't believe that I got it wrong
when I wrote the driver. Thanks a lot for the reviews and for cross-checking !
Guenter
> Reviewed-by: Tzung-Bi Shih <tzungbi@kernel.org>
>
> [1]: https://www.analog.com/media/en/technical-documentation/data-sheets/max6581.pdf
>
prev parent reply other threads:[~2024-07-14 18:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-13 21:34 [PATCH 1/2] hwmon: (max6697) Fix swapped temp{1,8} critical alarms Guenter Roeck
2024-07-13 21:34 ` [PATCH 2/2] hwmon: (max6697) Fix underflow when writing limit attributes Guenter Roeck
2024-07-14 7:07 ` Tzung-Bi Shih
2024-07-14 7:06 ` [PATCH 1/2] hwmon: (max6697) Fix swapped temp{1,8} critical alarms Tzung-Bi Shih
2024-07-14 18:47 ` Guenter Roeck [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4190de32-d0e1-4884-8823-e993bc4d054e@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-hwmon@vger.kernel.org \
--cc=tzungbi@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox