Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-virtual-sensor / a630f0812acae5d54c59dfc6bddf1264115f3689
commita630f0812acae5d54c59dfc6bddf1264115f3689[log] [tgz]
authorGeorge Liu <liuxiwei@ieisystem.com>Wed Aug 28 14:42:55 2024 +0800
committerGeorge Liu <liuxiwei@ieisystem.com>Wed Aug 28 14:42:55 2024 +0800
treee73ed73efdb52a69b89cdadcfef6198b1c864f26
parent150d5f6af7be3fbc3ac38f5dfab174830f08ee5b [diff]
Remove DEBUG flag

Since lg2 already supports the debug log level and the log level can
be modified in journald-maxlevel-policy.conf [1], there is no need to
add the DEBUG flag in this repo.

[1]: https://github.com/openbmc/openbmc/blob/master/meta-phosphor/recipes-core/systemd/phosphor-systemd-policy/journald-maxlevel-policy.conf

Signed-off-by: George Liu <liuxiwei@ieisystem.com>
Change-Id: I8a4a0564707478b8f8fdbbd128a2e2f7908c2ce6
1 file changed
tree: e73ed73efdb52a69b89cdadcfef6198b1c864f26
  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 configuration 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).