| commit | 883fb3a97b3ac47eab7d69e0841ff38ba5b9b2aa | [log] [tgz] |
|---|---|---|
| author | Josh Lehan <krellan@google.com> | Thu Feb 27 14:41:39 2020 -0800 |
| committer | Josh Lehan <krellan@google.com> | Wed Mar 04 13:23:26 2020 -0800 |
| tree | 687fe5f1cd248e467ce147c136f74d0f11e4563e | |
| parent | 14ce281a953e271ed10ae21a0fb03985e9ea45af [diff] |
Clean up logic within updateValue and checkThresholds Work around problems with floating-point equality Require small difference in order to publish new value Always check thresholds, regardless of magnitude of change This avoids problem of small change not triggering thresholds Using "Schmitt trigger" logic to avoid threshold jitter spam If threshold changed, threshold will always be checked next reading This avoids problem of threshold changes not taking immediate effect Added debugging counters for testing checkThresholds Signed-off-by: Josh Lehan <krellan@google.com> Change-Id: Ie8a0245382f7ce339ea3cb837a64b3fee119c71e
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