diff options
author | Matt Spinler <spinler@us.ibm.com> | 2019-08-07 18:36:20 +0300 |
---|---|---|
committer | Brad Bishop <bradleyb@fuzziesquirrel.com> | 2019-08-14 15:45:15 +0300 |
commit | d8cbfa5498e7fcc1646272c3c37febbdcd326c7b (patch) | |
tree | 1df6d10924bfc3eb9595a8a19f7fea0fe0aa45e8 /meta-phosphor | |
parent | 5c11c13abd3d75fde9cf171fd835143a0e0006a5 (diff) | |
download | openbmc-d8cbfa5498e7fcc1646272c3c37febbdcd326c7b.tar.xz |
wspoon: hwmon: Use labels for finding VRM I/V/P
A recent kernel update added a second input current/voltage/power
reading to the hwmon sysfs attributes for the ir35221 VRMs, and it threw
off the labels in the config files since they were hardcoded for the
specific previous numbers. For example, curr2_input previously
represented an output current but now represents an input current.
Fix this by using the LABEL mode in hwmon to find which sysfs file to
use for a particular sensor by the contents of its corresponding label
file. For example, the p0_vdd_current sensor should look at the sysfs
file that has a corresponding 'iout1' value in the currX_label file.
Tested: Test that the voltages are back within thresholds again and not
showing values around 12V.
(From meta-ibm rev: bca7ed0127f9e82895fb60b66b325347970f0860)
Change-Id: I9f28c9445daf9ce6206ff9e38e271ac805768fae
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Diffstat (limited to 'meta-phosphor')
0 files changed, 0 insertions, 0 deletions