Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-virtual-sensor / f2e9422107583056bd2dac8ce3d6238bc7635126
commitf2e9422107583056bd2dac8ce3d6238bc7635126[log] [tgz]
authorTao Lin <lintao.lc@ieisystem.com>Tue Oct 31 17:38:17 2023 +0800
committerTao Lin <lintao.lc@ieisystem.com>Thu Nov 30 16:12:55 2023 +0800
treeed9c014ef72dd67dc9d67531e5c1d129f06b3b2a
parentae10c529c629f3b09cca2edf870e453b8588af9b [diff]
UpdateVirtualSensor uses information from signals

UpdateVirtualSensor uses information obtained from signals to avoid
extensive dbus queries.

Tested:
1:Execute DBus cmd to see if VirtualSensor can correctly obtain the
value of DbusSensor
    busctl tree xyz.openbmc_project.VirtualSensor
    busctl introspect xyz.openbmc_project.VirtualSensor xxx
2:Waiting for the value change of DbusSensor,Check if the value of
the virtual sensor has changed after the dbusSensor changes.

Fixes openbmc/phosphor-virtual-sensor#1

Change-Id: If11f9017b31ce5cf06f910a38c65637c55d74b24
Signed-off-by: Tao Lin <lintao.lc@ieisystem.com>
8 files changed
tree: ed9c014ef72dd67dc9d67531e5c1d129f06b3b2a
  1. subprojects/
  2. test/
  3. .clang-format
  4. .editorconfig
  5. .gitignore
  6. .prettierrc.yaml
  7. dbusSensor.cpp
  8. dbusSensor.hpp
  9. dbusUtils.cpp
  10. dbusUtils.hpp
  11. exprtkTools.hpp
  12. LICENSE
  13. meson.build
  14. meson.options
  15. OWNERS
  16. phosphor-virtual-sensor.service.in
  17. README.md
  18. thresholds.hpp
  19. virtual_sensor_config.json
  20. virtualSensor.cpp
  21. 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 configuraton from D-Bus

For example:

{
  "Desc": {
    "Config": "D-Bus",
    "Type": "ModifiedMedian"
  }
}

Sensors added this way can only use a set of restricted calculations. Currently the only type supported is 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).