| commit | 17ab6e056c0ea319067eff5963df70b67e9511fa | [log] [tgz] |
|---|---|---|
| author | James Feist <james.feist@linux.intel.com> | Tue Jun 25 12:28:13 2019 -0700 |
| committer | James Feist <james.feist@linux.intel.com> | Tue Jun 25 19:31:24 2019 +0000 |
| tree | a13d99d7a8cc10824ba83dd8a61d3af9c5ba92d4 | |
| parent | 996bad1157fd1b50564ecb1fbd9502667a6e23e4 [diff] |
Fix Threshold Parse We agreed on using Label field, so not having thresholds should be ok. Tested: PSU1&2 fanspeeds are back Change-Id: I99b27300a6ee3ebb92b637297adbcc058c6b223b 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