| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
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>
|
