| commit | 19cb01d47975765a881fa4915c2a4f54d981e1bb | [log] [tgz] |
|---|---|---|
| author | James Feist <james.feist@linux.intel.com> | Mon Sep 16 13:43:52 2019 -0700 |
| committer | James Feist <james.feist@linux.intel.com> | Mon Sep 16 13:43:52 2019 -0700 |
| tree | c1b6ac04653457e14a69a03de86f2e155002cf7b | |
| parent | 8843b627a5450b8ca1d7a9ed91db337855186f87 [diff] |
Check thresholds each set Thresholds can be changed even if the reading isn't, call check thresholds each time so that if they are modified that we can set / unset the assert. Tested: Lowered sensor threshold, it got asserted Change-Id: Ibf3b874254e34be079f4e8d559e620e6922c5d3a Signed-off-by: James Feist <james.feist@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