Fix for sensor labeling

In case when more than one item is available for the same type of sensor
and the same channel number, only one dbus sensor was created instead of
few.

This change fixes this shortcoming by adding the ‘item’ suffix to the sensor
label and allowing to distinguish created sensors from each other for
different items. In case of 'input' item the suffix is omitted.

For example, when 3 items are available like: power1 _average, power1 _cap,
power1 _input and the name file contains text ‘Power’, before this change
only one sensor will be created under name:

    |-/xyz/openbmc_project/sensors/power/Power_CPU1

After this change a 3 separate sensors will be created:

    |-/xyz/openbmc_project/sensors/power/Power_Average_CPU1
    |-/xyz/openbmc_project/sensors/power/Power_Cap_CPU1
    |-/xyz/openbmc_project/sensors/power/Power_CPU1

With this commit the name of each sensor will follow the title convention,
where each word starts with upper case.

Tested:
    Tested manually with different items for the same sensor reading.

Signed-off-by: Zbigniew Kurzynski <zbigniew.kurzynski@intel.com>
Change-Id: I981d216e92fbee3b2a45a251e3359e6d41923b7d
1 file changed
tree: c38c62bef8acb5fa7b22da1756ee2a244b1528b2
  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