-Each channel or limit may have an associated alarm file, containing a
-boolean value. 1 means than an alarm condition exists, 0 means no alarm.
-
-Usually a given chip will either use channel-related alarms, or
-limit-related alarms, not both. The driver should just reflect the hardware
-implementation.
-
-in[0-*]_alarm
-fan[1-*]_alarm
-temp[1-*]_alarm
- Channel alarm
- 0: no alarm
- 1: alarm
- RO
-
-OR
-
-in[0-*]_min_alarm
-in[0-*]_max_alarm
-fan[1-*]_min_alarm
-temp[1-*]_min_alarm
-temp[1-*]_max_alarm
-temp[1-*]_crit_alarm
- Limit alarm
- 0: no alarm
- 1: alarm
- RO
-
-Each input channel may have an associated fault file. This can be used
-to notify open diodes, unconnected fans etc. where the hardware
-supports it. When this boolean has value 1, the measurement for that
-channel should not be trusted.
-
-in[0-*]_input_fault
-fan[1-*]_input_fault
-temp[1-*]_input_fault
- Input fault condition
- 0: no fault occured
- 1: fault condition
- RO
-
-Some chips also offer the possibility to get beeped when an alarm occurs:
-
-beep_enable Master beep enable
- 0: no beeps
- 1: beeps
- RW
-
-in[0-*]_beep
-fan[1-*]_beep
-temp[1-*]_beep
- Channel beep
- 0: disable
- 1: enable
- RW
-
-In theory, a chip could provide per-limit beep masking, but no such chip
-was seen so far.
-
-Old drivers provided a different, non-standard interface to alarms and
-beeps. These interface files are deprecated, but will be kept around
-for compatibility reasons: