Skip property changed signal on threshold initialization

When the sensor threshold config is changed, the sensor will be re-created,
These alarm are initialized as false. In case of there is any asserted event already,
needs to avoid the emit changed signal.

Tested:
Adjust the threshold to trigger the hwmon sensor threshold assert/deassert events,
there is no additional logs
1 | 05/08/20 | 17:07:54 UTC | Temperature #0x4a | Upper Non-critical going high | Asserted
2 | 05/08/20 | 17:08:12 UTC | Temperature #0x4a | Upper Non-critical going high | Deasserted
3 | 05/08/20 | 17:08:22 UTC | Temperature #0x4a | Upper Non-critical going high | Asserted
4 | 05/08/20 | 17:08:26 UTC | Temperature #0x4a | Upper Non-critical going high | Deasserted

Signed-off-by: Yong Li <yong.b.li@linux.intel.com>
Change-Id: Id152efe8f34a8ea00eb10004660b89c3275090d6
1 file changed
tree: 6ea55f54debe3617cb6bb8ee3ce1b5a22a0738b2
  1. cmake/
  2. include/
  3. service_files/
  4. src/
  5. tests/
  6. .clang-format
  7. .clang-ignore
  8. .gitignore
  9. cmake-format.json
  10. CMakeLists.txt
  11. Jenkinsfile
  12. LICENSE
  13. MAINTAINERS
  14. 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