| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
The metadata common to all IBM systems is confusingly split between
meta-ibm and meta-witherspoon. Move everything to meta-ibm.
The meta-ibm README is re-written to more accurately reflect the scope
of the layer.
Allow the configuration samples (bblayers.conf.sample,
local.conf.sample) to be sourced from either meta-ibm or
meta-witherspoon until such a time that any workflows and tooling have
had the opportunity to move to meta-ibm.
(From meta-ibm rev: 6e05ef2e90b214eaf4e43ee7027bbbb1d8d09442)
Change-Id: I3ec890d5300f9649c974ea6b9dca93a2e8a889ab
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The 5.3 kernel adds an 'fsi-master' directory in front of the fsi0 and
fsi1 directories in the OCC device tree paths. Update the OCC hwmon
file paths accordingly as those are based on that path.
(From meta-ibm rev: 696d1d3438499f974390c2c9c77fe4879509d9d1)
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I62b00664f2ebc18ed291d23faaf310fd15ce3e90
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
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>
|
|
Hard-coded values for fan tach sensor thresholds don't work because
these values vary. For accurate reporting, Redfish sensor output looks
at the functional status on the fan inventory.
Tested:
Same config files changed under /etc and change verified in the webUI
(From meta-ibm rev: 13ed7b8ed73d71206f6992a4c71294280c451446)
Signed-off-by: Aatir Manzur <aatrapps@gmail.com>
Change-Id: I80df620662d16cb677acbfe311bd2e709ae5976f
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Yocto automatically adds files/<MACHINE>/ to the file path, take
advantage of this feature to simplify the recipe and directory
structure.
Tested: Built witherspoon, witherspoon-128, and swift, and verified
they had the right conf file:
$ diff tmp/work/witherspoon_128-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/rootfs/etc/default/obmc/hwmon/ahb/apb/bus@1e78a000/i2c-bus@100/max31785@52_air.conf \
tmp/work/witherspoon-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/rootfs/etc/default/obmc/hwmon/ahb/apb/bus@1e78a000/i2c-bus@100/max31785@52_air.conf
$
$ diff tmp/work/witherspoon-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/rootfs/etc/default/obmc/hwmon/ahb/apb/bus@1e78a000/i2c-bus@100/max31785@52_air.conf \
tmp/work/swift-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/rootfs/etc/default/obmc/hwmon/ahb/apb/bus@1e78a000/i2c-bus@100/max31785@52_air.conf
2,3c2,3
< CRITLO_fan1 = "2974"
< CRITHI_fan1 = "12076"
---
...
(From meta-ibm rev: afdfaba229df3376f17ca063b53c9c8df0d84d0f)
Change-Id: Id24796c17c24aad29770fbd591e885534eeee2f7
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
