| commit | a222ba7defa9394d8fdfc162bc2bd0ad9bf3d2d4 | [log] [tgz] |
|---|---|---|
| author | James Feist <james.feist@linux.intel.com> | Fri Mar 01 15:57:51 2019 -0800 |
| committer | James Feist <james.feist@linux.intel.com> | Fri Mar 01 15:57:51 2019 -0800 |
| tree | 9c8dfbaf3f46da0e4f4dc4e9a8eb04aea746094b | |
| parent | 63abdd45629567321c3dc7ed1a3668ee894b222d [diff] |
Fix threshold updating The object type was never stored so it was never updated. Also change threshold size to count of thresholds for if anything has multiple thresholds. Tested-by: set thresholds for front panel temp Change-Id: I0949261b87336eb4a85cf596805c02683fb30d9b 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