commit | 7b7a9dea36cb59f5459a9d21fc6ed44272f28fa5 | [log] [tgz] |
---|---|---|
author | Jeff Lin <JeffLin2@quantatw.com> | Mon Feb 22 11:16:27 2021 +0800 |
committer | Jeff Lin <JeffLin2@quantatw.com> | Mon Feb 22 12:08:36 2021 +0800 |
tree | d205e0671d6f53fa11d43bb038b39d30901af048 | |
parent | 6cb732a31b7664089124b00e806311768bc24a87 [diff] |
Fix thresholds not found Due to the same attribute name "thresholds" in class 'ADCSensor' and 'Sensor', the function hasWarningInterface use this parameter from class ADCSensor and cause it can not found the correct thresholds. Rename the "thresholds" to "thresholdsIn" to avoid this problem. Tested: Add thresholds to adc, cpu, hwmon and fan sensor and verify pass. Signed-off-by: Jeff Lin <JeffLin2@quantatw.com> Change-Id: I6a8a5f7036dd9f195a7848ff03fa5f51966c2d2d
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