History log of /openbmc/phosphor-fan-presence/presence/fan.hpp (Results 1 – 3 of 3)
Revision Date Author Comments
# c65d91d6 21-Apr-2021 Matt Spinler <spinler@us.ibm.com>

presence: Sensor conflict checking for AnyOf

There can be more than one way to detect the presence of a fan, such as
by a GPIO and by a nonzero tach reading. The AnyOf redundancy policy
only requir

presence: Sensor conflict checking for AnyOf

There can be more than one way to detect the presence of a fan, such as
by a GPIO and by a nonzero tach reading. The AnyOf redundancy policy
only requires one of these to indicate present when determining the
overall fan presence state.

This commit adds the functionality to check for the case when one of the
method reports not present while another reports present. In this case,
the one reporting not present will be considered the wrong one, and
depending on the detection type either an information event log or just
a journal trace will be created.

Only one log per method per power cycle will occur. Since one of the
methods probably looks for nonzero tach readings, there is a 5 second
delay after a power on is detected before a conflict check is done.

If the GPIO method is where the problem is detected, an event log is
created. If it's instead the tach sensor method, then a trace will just
be put in the journal because there is already code watching for and
creating event logs for stopped tachs - the fan monitor code.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I72a764ecff4076d6dc40335b92d177b6b3cfa2d9

show more ...


# 9e9f599c 30-Sep-2020 Matt Spinler <spinler@us.ibm.com>

presence: Make error time be per fan

Previously there was a global value for the amount of time a fan needed
to be missing before an event log was created. This commit changes it
so that instead th

presence: Make error time be per fan

Previously there was a global value for the amount of time a fan needed
to be missing before an event log was created. This commit changes it
so that instead the value is specified per fan in the JSON.

This way, the times can be different or left off completely on a fan to
fan basis. The ErrorReporter object will only be created if there is at
least one fan with a time value.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I53bb91c88ec1b0352df11b2e988064c2ec02af45

show more ...


# 825e31e5 14-Jun-2017 Brad Bishop <bradleyb@fuzziesquirrel.com>

presence: Add fan utility

Add utility wrappers for reading/writing
xyz.openbmc_project.Inventory.Item.Present.

Change-Id: I9d6bb776e56b67b9cac1f991790886ec8105d4b1
Signed-off-by: Brad Bishop <bradl

presence: Add fan utility

Add utility wrappers for reading/writing
xyz.openbmc_project.Inventory.Item.Present.

Change-Id: I9d6bb776e56b67b9cac1f991790886ec8105d4b1
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>

show more ...