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
1 file changed
tree: 5a10e58e0a866fc5f63dc2562c1efea5cb77df9d
  1. include/
  2. service_files/
  3. src/
  4. subprojects/
  5. tests/
  6. .clang-format
  7. .clang-ignore
  8. .clang-tidy
  9. .gitignore
  10. Jenkinsfile
  11. LICENSE
  12. MAINTAINERS
  13. meson.build
  14. meson_options.txt
  15. OWNERS
  16. README.md
README.md

dbus-sensors

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.

key features

  • 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

sensor documentation