Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-virtual-sensor / be3c77faafa5a9993dcec4b9ac3586eefb84b781
commitbe3c77faafa5a9993dcec4b9ac3586eefb84b781[log] [tgz]
authorLei YU <yulei.sh@bytedance.com>Fri Feb 07 02:51:23 2025 +0000
committerLei YU <yulei.sh@bytedance.com>Fri Feb 07 02:53:34 2025 +0000
treedf20d7f66b940012ffd038121b61b43b7d02014f
parent4224ca36acd8bf7089e1e2f566ef5235d0f86c97 [diff]
exprtk.wrap: Specify 0.0.3 release

The revision in exprtk.wrap points to a bad revision (possibly due to
the exprtk force push on github), and the revision fails to build with
clang++ as well.

The yocto now points to 0.0.3 release, change the revision here to make
it consistent and it compiles with clang++ now.

Signed-off-by: Lei YU <yulei.sh@bytedance.com>
Change-Id: I52cf9a6df21494933545238cf4c95b5287ce88f7
1 file changed
tree: df20d7f66b940012ffd038121b61b43b7d02014f
  1. subprojects/
  2. test/
  3. .clang-format
  4. .editorconfig
  5. .gitignore
  6. .prettierrc.yaml
  7. calculate.cpp
  8. calculate.hpp
  9. dbusSensor.cpp
  10. dbusSensor.hpp
  11. dbusUtils.cpp
  12. dbusUtils.hpp
  13. exprtkTools.hpp
  14. LICENSE
  15. main.cpp
  16. meson.build
  17. meson.options
  18. OWNERS
  19. phosphor-virtual-sensor.service.in
  20. README.md
  21. thresholds.hpp
  22. virtual_sensor_config.json
  23. virtualSensor.cpp
  24. 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).