| commit | c0ca7ee5062f9e7d7e7d6fcd44027668a137020e | [log] [tgz] |
|---|---|---|
| author | Richard Marian Thomaiyar <richard.marian.thomaiyar@linux.intel.com> | Wed Apr 24 21:22:52 2019 +0530 |
| committer | Richard Marian Thomaiyar <richard.marian.thomaiyar@linux.intel.com> | Thu Apr 25 00:52:46 2019 +0000 |
| tree | 7a4c13345c540d5ecad4404b3d641e44e8063b4c | |
| parent | a5e587230aa26c9ccc975b35a75621834346be6d [diff] |
Check thresholds for sensor override Fix bug, which got introduced when moving override logic to base class. This fixes to check thresholds for external set (i.e. sensor override). Tested: 1. Verified that threshold events are triggered, when updating Value property more than the threshold value 2. Verified that threshold events are set to low when Value property is updated to normal level Change-Id: I6a3cb9c66ebdc38c793b6397eb98f88ad9e1be55 Signed-off-by: Richard Marian Thomaiyar <richard.marian.thomaiyar@linux.intel.com>
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