Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-virtual-sensor / 26ef5a65ca347a93b3e81565b46ccb99bd36f3d5
commit26ef5a65ca347a93b3e81565b46ccb99bd36f3d5[log] [tgz]
authorPatrick Williams <patrick@stwcx.xyz>Fri Jul 22 16:18:43 2022 -0500
committerPatrick Williams <patrick@stwcx.xyz>Wed Jul 27 22:00:50 2022 +0000
tree3a7e2c8e1f10070688cd5e5424a041b3fc2e25d8
parent8e11cccbd23b7a78e95bdafe0e93d19481eb4408 [diff]
OWNERS: switch 'matches' to 'matchers'

The original OWNERS template had a mistake which used 'matches' instead
of the field supported by the Gerrit plugin 'matchers'.  Update the
OWNERS file to have the correct field.

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I04274019c240f7100d7ce1ca20399976f935dd4d
1 file changed
tree: 3a7e2c8e1f10070688cd5e5424a041b3fc2e25d8
  1. subprojects/
  2. .clang-format
  3. .editorconfig
  4. .gitignore
  5. .markdownlint.yaml
  6. .prettierrc.yaml
  7. dbusSensor.hpp
  8. dbusUtils.hpp
  9. exprtkTools.hpp
  10. LICENSE
  11. MAINTAINERS
  12. meson.build
  13. OWNERS
  14. phosphor-virtual-sensor.service.in
  15. README.md
  16. thresholds.hpp
  17. virtual_sensor_config.json
  18. virtualSensor.cpp
  19. virtualSensor.hpp
README.md

phosphor-virtual-sensor

phosphor-virtual-sensor reads in virtual_sensor_config.json 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. At this stage 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).