diff options
| author | Jean Delvare <khali@linux-fr.org> | 2007-06-09 10:11:16 -0400 |
|---|---|---|
| committer | Mark M. Hoffman <mhoffman@lightlink.com> | 2007-07-19 14:22:12 -0400 |
| commit | 7817a39e65f04abe136d94a65fa26b7fe3334a1f (patch) | |
| tree | 4c7170fe690a8e66e1db341e32e28e7108e46435 /README | |
| parent | 32c82a934759b2c9939c9e25865c2d7d1204b9e8 (diff) | |
| download | linux-3.10-7817a39e65f04abe136d94a65fa26b7fe3334a1f.tar.gz linux-3.10-7817a39e65f04abe136d94a65fa26b7fe3334a1f.tar.bz2 linux-3.10-7817a39e65f04abe136d94a65fa26b7fe3334a1f.zip | |
hwmon: Fault files naming convention
We have the following naming convention documented in
Documentation/hwmon/sysfs-interface for fault files:
in[0-*]_input_fault
fan[1-*]_input_fault
temp[1-*]_input_fault
Some drivers follow this convention (lm63, lm83, lm90, smsc47m192).
However some drivers omit the "input" part and create files named
fan1_fault (pc87427) or temp1_fault (dme1737). And the new "generic"
libsensors follows this second (non-standard) convention, so it fails
to report fault conditions for drivers which follow the standard.
We want a single naming scheme, and everyone seems to prefer the
shorter variant, so let's go for it.
Signed-off-by: Jean Delvare <khali@linux-fr.org>
Diffstat (limited to 'README')
0 files changed, 0 insertions, 0 deletions