commit | 551087a5d6db7e45fa6e353dc94f24af0dbddd82 | [log] [tgz] |
---|---|---|
author | James Feist <james.feist@linux.intel.com> | Mon Dec 09 11:17:12 2019 -0800 |
committer | James Feist <james.feist@linux.intel.com> | Mon Dec 09 13:53:01 2019 -0800 |
tree | 7af0338baf7980006d8740dd0c100266a3a50ded | |
parent | 2424cb7c9752cbecc3d133a67cf1c20f8589f2c1 [diff] |
ipmbsensor fix errors / thresholds Make the sensor set the lowest possible value when multiple read errors occur. Also fix the sensor threshold settings based on the spec: A high-going threshold has its assertion events become set when the reading is >= the threshold, while for a low-going event the assertion becomes set when the reading is <= the threshold. Tested: fans boosted after putting me in recovery Change-Id: I0fc9edafb57afa61cf68124eec5d124cdbb51983 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