commit | 75872ef8011c22a419fbc0cff50aad8ae68faa4c | [log] [tgz] |
---|---|---|
author | Konstantin Aladyshev <aladyshev22@gmail.com> | Thu May 13 11:17:58 2021 +0300 |
committer | Ed Tanous <ed@tanous.net> | Tue May 10 18:30:49 2022 +0000 |
tree | 5a10e58e0a866fc5f63dc2562c1efea5cb77df9d | |
parent | 7c97730b4119d60853ff291ffb3d89ffc6bf6c98 [diff] |
Always fill both values for a threshold interface If one of the thresholds for a threshold dbus interface is provided we have to set the other one as dbus properties are never optional. Tested: Before: xyz.openbmc_project.Sensor.Threshold.Warning interface - - .WarningAlarmHigh property b false .WarningHigh property d 14 After: xyz.openbmc_project.Sensor.Threshold.Warning interface - - .WarningAlarmHigh property b false .WarningAlarmLow property b false .WarningHigh property d 14 .WarningLow property d nan Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com> Change-Id: I0e9b885e8c0494d46d39af965047a7582255a48e
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