diff options
author | Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com> | 2021-04-12 15:53:15 +0300 |
---|---|---|
committer | Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com> | 2021-04-12 15:54:13 +0300 |
commit | afe16dc5dc9300e29da18dafe92e496946b31d9f (patch) | |
tree | ed8fb38ba7089754d8880886b7fba7262e3daf83 /meta-phosphor/recipes-phosphor/ipmi | |
parent | 06b43dad66ee0d55e5c53f7ed9f73e59e86dff4a (diff) | |
download | openbmc-afe16dc5dc9300e29da18dafe92e496946b31d9f.tar.xz |
ibm: Add back fru-fault-monitor to Rainier and Everest systems
Commit f7b1f26 removed fru-fault-monitor from Rainier since the
idea then was to have PEL daemon set the Asserted property of
LED Group Object that is mapping to the Inventory D-Bus object.
However, that was not accepted by the community and we now have
a new way of monitoring faults.
With the new way, when monitor-operational-status feature is
enabled, fru-fault-monitor will watch Functional property of
xyz.openbmc_project.State.Decorator.OperationalStatus interface
and sets the Asserted property of appropriate LED Group D-Bus
objects that is mapped via "fault_led_group" association with
the Inventory D-Bus object.
When monitor-operational-status feature is enabled,
fru-fault-monitor will not monitor the OBMC events and would
only watch OperationalStatus. This is done because these 2
features will result in conflicting end result on the LEDs.
Change-Id: I739b5fc261b0c79d50a8dc34ab19a3e108e84edc
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
Diffstat (limited to 'meta-phosphor/recipes-phosphor/ipmi')
0 files changed, 0 insertions, 0 deletions