Add threshold value scanning logic into cpusensor

Threshold values of a CPU sensor can be changed at runtime by BIOS
based on the thermal policy changes of the host machine. So this
commit adds runtime scanning logic for reading threshold values
from hwmon subsystem attributes.

Tested:
  Check threshold properties in xyz.openbmc_projects.CPUSensor.
  All threshold vaues should reflect peci hwmon values dynamically.

Change-Id: Ib5b0ce72f567437e69879a7e655d6f34f156013e
Signed-off-by: Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com>
3 files changed
tree: d1c4d46ebc026354a4cc923bbba7cb4423830f53
  1. cmake/
  2. include/
  3. service_files/
  4. src/
  5. tests/
  6. .clang-format
  7. .gitignore
  8. cmake-format.json
  9. CMakeLists.txt
  10. Jenkinsfile
  11. LICENSE
  12. MAINTAINERS
  13. 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