Re: [PATCH 2/2] hwmon: (max16065) Fix alarm attributes

[Guenter Roeck <linux@roeck-us.net>]

On 7/21/24 22:47, Tzung-Bi Shih wrote:
> On Sun, Jul 21, 2024 at 08:48:51PM -0700, Guenter Roeck wrote:
>> On 7/21/24 20:30, Tzung-Bi Shih wrote:
>>> On Sun, Jul 21, 2024 at 12:35:06PM -0700, Guenter Roeck wrote:
>>>> Chips reporting overcurrent alarms report it in the second alarm register.
>>>
>>> I can't understand the sentence.  Not sure whether it needs to be rephrased or
>>> not.  s/overcurrent/overvoltage/.
>>>
>>
>> No, it is over-current. Not all chips support current measurements.
>> Those who do support it also support reporting over-current alarms.
>> Over-current alarms are reported in the second alarm register.
> 
> Table 16 in [1] and Table 11 in [2] use "overvoltage".  Please ignore the
> comments if I'm misunderstanding.
> 
> [1]: https://www.analog.com/media/en/technical-documentation/data-sheets/max16067.pdf
> [2]: https://www.analog.com/media/en/technical-documentation/data-sheets/max16068.pdf
> 
Yes, those two chips don't support current or over-current reporting.
Only 160{65,66,70,71} support it.

Thanks,
Guenter