| commit | 52497fd0fbd8adfe099a99f23515cd0341898e2e | [log] [tgz] |
|---|---|---|
| author | James Feist <james.feist@linux.intel.com> | Fri Jun 07 13:01:33 2019 -0700 |
| committer | James Feist <james.feist@linux.intel.com> | Fri Jun 14 12:12:15 2019 -0700 |
| tree | cd4f08e428b5f4a359d3e69601be589efaf73fee | |
| parent | 15266a96d758d4dbc1d3095e652ae083b24732c7 [diff] |
Change power control match to use host state Lower level signals were removed, use host state instead. Also fix bug that was introduced, std::abs(nan, number) returns nan, so checkThresholds wasn't being called. Tested: Put in prints and saw power/post state change to on Change-Id: I98df270237900c3a0b01c03ec7905851bc47e3b3 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