[lm-sensors] Help wanted: individual alarm files
khali at linux-fr.org
Sun Jul 1 22:00:05 CEST 2007
The future libsensors assumes that all hardware monitoring drivers
follow the standard sysfs interface defined in
Documentation/hwmon/sysfs-interface. They all mostly do already, except
for one thing: alarms. Most drivers are still only exposing a single
file with all alarms in a bit-vector, in chip-dependent order. In order
to let the new libsenors display the alarms properly, we must add
individual alarm files to these drivers. For some drivers, fault and/or
beep files need to be added too.
Here's the current status, to the best of my knowledge.
Already have individual alarm files:
Don't have alarms at all:
Need to be converted:
As you can see, the list is quite long, so I need help. That's not a
difficult job, but you need chip ship in question to test.
How to add individual alarm files:
* Read Documentation/hwmon/sysfs-interface, so that you know what are
the valid names for individual alarm, fault and beep files.
* Take a look at this patch which adds individual alarm support to 4
* Do the same to your driver. To find out which alarm bit correspond to
what, you can look at the defines used in the current version of
Or you can look at the datasheet for your chip, but it's likely to take
* Test. You can test manually (change the limits and read the alarm
files from sysfs) or you can use the next version of libsensors, which
is in branch "lm-sensors-3.0.0" under SVN:
svn checkout http://lm-sensors.org/svn/lm-sensors/branch/lm-sensors-3.0.0 lm-sensors-3
* Submit your patch to the lm-sensors list, I'll review it.
More information about the lm-sensors