| commit | 1e34cecad498e89fb52b4c73cb19e62a297f2329 | [log] [tgz] |
|---|---|---|
| author | Rashmica Gupta <rashmica.g@gmail.com> | Tue Aug 31 16:47:39 2021 +1000 |
| committer | Ed Tanous <ed@tanous.net> | Sat Sep 25 16:17:50 2021 +0000 |
| tree | 926cada01e7a7256ae8626067d70b512bdc0647c | |
| parent | 587941d0af66ac183984c832c4f0b2958c8daa38 [diff] |
thresholds: support hysteresis field if supplied At the moment dbus-sensors that use thresholds use a default hysteresis of (max - min) * 0.01. If a hysteresis field is specified for a threshold that is not NaN, use that instead. Tested by giving a sensor multiple thresholds, with and without hysteresis, changing the value of the sensor and observing that the threshold alarms are asserted and deasserted as expected. Signed-off-by: Rashmica Gupta <rashmica.g@gmail.com> Change-Id: I9c6c2ef3bb034157b0a6b3bd5c359dae7592d85b
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