Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-virtual-sensor / 6f128345845e973856cd3a67c14d99cde0711278
commit6f128345845e973856cd3a67c14d99cde0711278[log] [tgz]
authorGeorge Liu <liuxiwei@ieisystem.com>Fri Jul 25 16:39:53 2025 +0800
committerGeorge Liu <liuxiwei@ieisystem.com>Fri Jul 25 16:39:53 2025 +0800
tree4c20c5fa2245cea7f596d5cc4b99f045f59b46e5
parentf8fcdc2a9cb4bef1ddf3676ca84833acfbc79f8d [diff]
Remove unused variable 'path' in handleDbusSignalPropChange

The variable `path` was assigned using `msg.get_path()` but never used
in the logic. This patch removes the redundant line to clean up the
code and avoid unused variable warnings.

Change-Id: I4c1eee8e3688b5483509670b79ef515b7892d86e
Signed-off-by: George Liu <liuxiwei@ieisystem.com>
1 file changed
tree: 4c20c5fa2245cea7f596d5cc4b99f045f59b46e5
  1. subprojects/
  2. test/
  3. .clang-format
  4. .clang-tidy
  5. .editorconfig
  6. .gitignore
  7. .prettierrc.yaml
  8. calculate.cpp
  9. calculate.hpp
  10. dbusSensor.cpp
  11. dbusSensor.hpp
  12. dbusUtils.cpp
  13. dbusUtils.hpp
  14. exprtkTools.hpp
  15. LICENSE
  16. main.cpp
  17. meson.build
  18. meson.options
  19. OWNERS
  20. phosphor-virtual-sensor.service.in
  21. README.md
  22. thresholds.hpp
  23. virtual_sensor_config.json
  24. virtualSensor.cpp
  25. virtualSensor.hpp
README.md

phosphor-virtual-sensor

phosphor-virtual-sensor reads the configuration file virtual_sensor_config.json from one of three locations:

  1. The current directory.
  2. /var/lib/phosphor-virtual-sensor
  3. /usr/share/phosphor-virtual-sensor

By default the repository will install a sample config into (3).

There are two types of data in this file.

virtual sensor configuration information

See virtual_sensor_config.json in this repository for an example. Sensors added this way can use any expression that is accepted by exprtk.

information to get a virtual sensor configuration from D-Bus

For example:

{
  "Desc": {
    "Config": "D-Bus"
  }
}

Sensors added this way can only use a set of restricted calculations. Currently supported types are Average, Maximum, Minimum, Sum and ModifiedMedian.

The virtual sensor configuration information needs to be added into the relevant hardware configuration file in entity-manager. This method of adding a virtual sensor allows a recipe that builds for different hardware configurations to have different virtual sensors for each configuration.

The virtual sensor configuration in entity manager follows a different format to the JSON in virtual_sensor_config.json (specified in entity-manager/schemas/VirtualSensor.json).