Age | Commit message (Collapse) | Author | Files | Lines |
|
Modify ACBEL PSU configuration file to read output voltage from sysfs
in2_label and to read the output current from curr2_label.
Testing: Placed the modified config file in
/etc//default/obmc/hwmon/ahb/apb/bus@1e78a000/i2c-bus@200/power-supply@5a.conf
then verified the output voltage and current output shows up on the BMC
sensors web page and redfish.
Change-Id: Iacf1469295b99f6a7363d26983786f9c7ed8826a
Signed-off-by: Faisal Awada <faisal@us.ibm.com>
|
|
Would like to make a variant of the p10bmc machine that includes some of
the new etcd function. To do that, the search paths need to not include
the MACHINE variable. bitbake is smart enough to look under the
sub-directory and find the appropriate files.
Change-Id: I542b4568c18210870b3e621461585a4c7eee3121
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Add the power-supply configuration files for the acbel-fsg032 power
supplies used in the Bonnell systems in order to get telemetry data
added to D-Bus via phosphor-hwmon.
Bonnell power supplies on bus 3 at 0x5a and 0x5b
Change-Id: I97a1e1ba57ee1b2da6462b6921f121683498fe87
Signed-off-by: Lakshmi Yadlapati <lakshmiy@us.ibm.com>
|
|
While the max31785 is at the same I2C bus and address as on Rainier, it
only has two fans so it needs a unique hwmon conf file, which it has
because the name is different in the device tree.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Ia2c77e4149f02fe0a9d335cdd0551fb4ddd75108
|
|
Since the accuracy of power supply input power sensors is 1% on IBM's
p10bmc system, add `ACCURACY=1` to the power supply configuration of
p10bmc.
Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: If143a61e44936fbd758d556575c250bc6ea501b2
|
|
A fork of it is maintained but its upstream layer has largely been
unmaintained.
No future products are planned to be based on this layer.
Mihawk is similar to Witherspoon.
Signed-off-by: Myung Bae <myungbae@us.ibm.com>
Change-Id: I82f7d777b78cd126237d51e42f1e11abdf80ae68
|
|
New yocto has gotten more strict and requires the specific paths be set
for machines.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: If7fb3410c2c513b355260ed28869822741b9d344
|
|
Add the power supply temperature readings to the hwmon configuration and
the Rainier and Everest assocation files.
Signed-off-by: Brandon Wyman <bjwyman@gmail.com>
Change-Id: I00e7fde4a58da553b9374733b22b8608d0c9da41
|
|
As mentioned by I970e06ca6f9d0a9792af122eb25da1bb9a06f058, append and
remove directives with '+=' are no longer valid Yocto syntax and raise a
warning.
See https://git.yoctoproject.org/poky/tree/documentation/migration-guides/migration-3.5.rst#n40
One interesting caveat has to do with the difference between "append"
and "+=".
foo:append = "a"
foo:append = "b"
Results in `foo = "ab"`, but
foo += "a"
foo += "b"
Results in `foo = "a b"`. When `:append +=` is used it has behavior
like the `+=` operator. Therefore, in some cases we need to insert
additional whitespace after the `:append = "` to ensure concatenation
behaves as expected. I've manually reviewed the results to ensure there
is no ill side-effects from an additional space potentially being added.
Fix up the entire tree with the following one-liner (and similar for
`remove`):
git ls-files -- ':!:poky/**' ':!:meta-security/**' \
':!:meta-raspberrypi/**' ':!:meta-openembedded/**' \
| grep "\.bb" | xargs grep -l ":append.*+=" \
| xargs sed -i 's/:append\(.*\)+=\([^"]*\)" */:append\1=\2" /'
or ...
| xargs grep -l ":remove.*+=" \
| xargs sed -i "s/:remove\(.*\)+=/:remove\1=/"
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Iea6235e7c76e252f4d473652957c2925f6b8845a
|
|
Add the power-supply configuration files for the ibm-cffps power
supplies used in the Rainier and Everest systems in order to get
telemetry data added to D-Bus via phosphor-hwmon.
Rainier power supplies on bus 3 at 0x68, 0x69, 0x6a, and 0x6b.
Everest power supplies on bus 3 at 0x68, 0x69, 0x6d, and 0x6b. Older
hardware has power supply at 0x6a instead of 0x6d.
Input voltage, input power, output voltage, and output current.
No critical or warning low values, to avoid logging errors when AC is
pulled, or other fault conditions handled by the PSU monitor. AC loss,
brownout, over-voltage, over-current, and other conditions should be
handled by the PSU monitor application.
No critical/warning high values, for similar doubled up fault logging.
Change-Id: I9f39e41e2dd0a7b77910207322506d8376f98772
Signed-off-by: Brandon Wyman <bjwyman@gmail.com>
|
|
This tells phosphor-virtual-sensors to look on D-Bus for a virtual
sensor config of type ModifiedMedian. This way we can use the same
recipe for different hardware configurations.
Change-Id: I3ebd0a636f07a0854251e06b952ad9646f12f637
Signed-off-by: Rashmica Gupta <rashmica.g@gmail.com>
|
|
There is an upcoming systemd change that doesn't handle what was being
done, which was to delay starting phosphor-hwmon from udev until the
chassis cooling type was on D-Bus.
This commit removes this method and goes down to a single hwmon config
file that only supports the air cooled system, which has 2 more fan
rotors than the water cooled one does.
This change also applies to the similar systems witherspoon-tacoma and
swift.
Resolves openbmc/phosphor-hwmon/#19.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Ic4ed46a5bf310fb1fef8704dcafc0376c441f8c4
|
|
Upstream bbclasses changed to typically use the `:${PN}` override
syntax, including the SYSTEMD_ variables. Change our systemd.bbclass
to do the same for consistency and perform a tree-wide variable
replacement.
Spot checked by building bletchley and witherspoon and checking
some of the SYSTEMD_LINK directives on installed packages under qemu.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I20a9dd809bff8af8759488734f80486c7228c6eb
|
|
Use nonarch_base_libdir instead of base_libdir, because the files are
always in /lib/udev/rules.d/. On ppc64le base_libdir is lib64, and the
files end up in the wrong spot.
Signed-off-by: Anton Blanchard <anton@ozlabs.org>
Change-Id: I3c24dae293f4166f1ed1826d09d4bde7cd7d0357
|
|
Change-Id: I9116ed7260e369136acb39eec15075db2d4dbeba
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
The Altitude measurement is from the computation of
the DPS310 pressure sensor with this
"Expression": "44330.0 * (1.0 - ((P0/101325.0) ^ (1/5.255)))"
Tested: busctl introspect xyz.openbmc_project.VirtualSensor \
/xyz/openbmc_project/sensors/altitude/Altitude returned
results consistent with location of the Rainier system.
Signed-off-by: Bruce Mitchell <bruce.mitchell@linux.vnet.ibm.com>
Change-Id: I07b83dd6b8f4ccf0755ccbdc81c40976a3e571cd
|
|
The repository supports it, so switch it over in bitbake.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I8d96c79b395ee2614ddd869091569f245426c5c7
|
|
The IBM rainier machine name is being replaced with the generic p10bmc.
Change-Id: I43d08c3be45d8cc8b03914b9bc257df2668e9fe0
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
Everest has the max31785 at a different i2c address that is behind a
mux, so install its hwmon config at that associated location.
Tested:
Hwmon instance for the max31785 starts successfully on Everest
(From meta-ibm rev: cd84eb53a79edcabddd5e7720f9e0389f4e96151)
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Change-Id: Ide9ca8bd76d708ef9453dc7d02526dfbb1dd8a30
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Add the max31785 fan controller device to hwmon.
(From meta-ibm rev: 71404ba4966e32bb4ed9a120062d669ed642d851)
Change-Id: I4b2cd1c5379e76ccf40f52dc6ceca6a98f931f40
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The max31785-msl application is now a package within the phosphor-hwmon
recipe, so that package needs to be enabled and installed on
`ibm-ac-server` alias of machines which have a max31785 chip. These
machines require that the minimum ship level(msl) be verified on them
using this application.
Tested:
Built phosphor-hwmon package after enabling max31785-msl package
Verified application, config file, and service existed in image
(From meta-ibm rev: 33184059fa07ca12e11fb9e8dde2d6a31e1f029e)
Change-Id: I186fb6ca930e4107738d4ed90d31b6233be3d6f2
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The phosphor-virtual-sensor code recently started checking the values of
the upper/lower warning/critical thresholds for the virtual sensors and
prints to the journal if they are exceeded. If the threshold values to
use aren't specified in the JSON file, it will just set them to zero so
any nonzero sensor value will trigger the trace.
So, even though code will not use the threshold values for the virtual
ambient temperature sensor, put some into the JSON anyway that should
never be exceeded to avoid these traces. If the temperature does happen
to go outside the range of between 0 and 100, then seeing the trace may
be interesting anyway.
(From meta-ibm rev: 9fdb9598d0eee4d9820962320391bb9f7e4568ea)
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I1c6c5f1faaaf58599a3840eed6ec4749a70a1364
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Rainier is only using the hwmontempsensor dbus-sensors service for now,
so remove the other ones. Without this, 8 other services would be
running at BMC ready state.
(From meta-ibm rev: b51345ced440ca935f8678d8521a690301e63db5)
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: If60d9a0ba585c029877c5fda77b5085cec394d04
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Use the virtual-sensor application to put a virtual ambient temperature
sensor on D-Bus. Currently, it just mirrors the value of the TMP275
ambient temperature sensor, but in the future the output will be based
on all three temp sensors on the panel after the remaining two show up
on D-Bus.
(From meta-ibm rev: f43eab1e5637cf87a38ca2e9a6acc33e5db3a0c3)
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I187d88c7e1245c7014aee8b9b6c0840daf1e622d
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Remove executable permissions from the `70-max31785-hwmon.rules` file to
eliminate the systemd-udevd warning that its marked executable.
(From meta-ibm rev: 46984b5eda5c40e63cb9fab6aa5e667cec7f5b68)
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Change-Id: Ic7405ed73f2d7875c57696ae4e5b30e380502fd6
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Mihawk cannot read the 250 soc sensor on the riser, this is because dts
defines pca9545riser@70 instead of pca9545@70.
(From meta-ibm rev: 731297ebde0eb4272d39260a30cd5f5b1f4e6f1a)
Change-Id: Ibcb72ef6be7c953cc35cc216e8cc45e283949e61
Signed-off-by: Ben Pai <Ben_Pai@wistron.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Mihawk can use up to eight 250-soc.
Tested:
The user can see the temperature when using 250-soc.
(From meta-ibm rev: 74b7557b08ed2582861cd7da390d84371ec2ff86)
Change-Id: I17b0d969d0902f6470287c6164f542ad84412f7d
Signed-off-by: Ben Pai <Ben_Pai@wistron.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
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>
|