Commit 2de83b67 authored by Javier Carrasco's avatar Javier Carrasco Committed by Guenter Roeck

ABI: sysfs-class-hwmon: fix tempY_crit_alarm access rights

This attribute is defined as read-only by all drivers that support it.

It seems that the access rights and description for this attribute were
copied from the intrusionY_alarm, which has indeed RW rights and must be
cleared by the user.

These are the modules that currently use this attribute:
- adt7x10
- i5500_temp
- jc42
- lm83
- lm90
- lm95245
- max31760
- max6621
- mc34vr500
- tmp401
- tmp464
- tmp513

Fix the attribute description and make it read-only.

Fixes: 365b5d63 ("ABI: sysfs-class-hwmon: add a description for tempY_crit_alarm")
Signed-off-by: default avatarJavier Carrasco <javier.carrasco.cruz@gmail.com>
Link: https://lore.kernel.org/r/20231116-hwmon_abi-v1-3-8bfb7f51145a@gmail.comSigned-off-by: default avatarGuenter Roeck <linux@roeck-us.net>
parent d0d71055
...@@ -434,12 +434,7 @@ Description: ...@@ -434,12 +434,7 @@ Description:
- 0: OK - 0: OK
- 1: temperature has reached tempY_crit - 1: temperature has reached tempY_crit
RW RO
Contrary to regular alarm flags which clear themselves
automatically when read, this one sticks until cleared by
the user. This is done by writing 0 to the file. Writing
other values is unsupported.
What: /sys/class/hwmon/hwmonX/tempY_crit_hyst What: /sys/class/hwmon/hwmonX/tempY_crit_hyst
Description: Description:
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment