| commit | bf7cbc8765d518d831888ca6619c86f3a7c2fba1 | [log] [tgz] |
|---|---|---|
| author | Zhikui Ren <zhikui.ren@intel.com> | Thu Jul 02 08:44:00 2020 -0700 |
| committer | Zhikui Ren <zhikui.ren@intel.com> | Tue Jul 21 17:11:26 2020 -0700 |
| tree | e7b8f51f923b62bc28a62f4c519719d99185b0cd | |
| parent | 375ade29c1d06d54e827b1f8a2e15193d7036fee [diff] |
Update checkThresholdsPowerDelay to user timer for LOW thresholds only When CPU is powered off, some volatges are expected to go below low thresholds. Add delay for low threshold assert events. No delays for all high threshold events. When a deassert event happens of a low threshold while there is an active timer for assert of the same threshold, instead of cancel the existing timer, start a timer for de-assrt the threshold. This fixes the issue that a low event can be missed because of the timer cancellation. Tested: Signed-off-by: Zhikui Ren <zhikui.ren@intel.com> Change-Id: I3b9b15ddf1ed084304e012aae1b6c540f855c8af
dbus-sensors is a collection of sensor applications that provide the xyz.openbmc_project.Sensor collection of interfaces. They read sensor values from hwmon, d-bus, or direct driver access to provide readings. Some advance non-sensor features such as fan presence, pwm control, and automatic cpu detection (x86) are also supported.
runtime re-configurable from d-bus (entity-manager or the like)
isolated: each sensor type is isolated into its own daemon, so a bug in one sensor is unlikely to affect another, and single sensor modifications are possible
async single-threaded: uses sdbusplus/asio bindings
multiple data inputs: hwmon, d-bus, direct driver access