Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-virtual-sensor / 76e6c5afb92c06c5ed925e92752cde0f52a9c493
commit76e6c5afb92c06c5ed925e92752cde0f52a9c493[log] [tgz]
authorPatrick Williams <patrick@stwcx.xyz>Thu Jan 30 17:48:07 2025 -0500
committerPatrick Williams <patrick@stwcx.xyz>Thu Jan 30 17:48:07 2025 -0500
tree5b162860a90e7a47241888842e5618b8c4e5d679
parent74f835b014e6791b1783f689aa5c338879349e53 [diff]
build: use allowed over enabled or not-disabled

Meson feature options are typically in a tri-state of enabled, disabled,
or auto.  The enabled and disabled functions on an option (from
`get_option`) no longer return true for auto features.  Instead, the
expectation is to use `allowed()` which is true for both enabled and
auto.

Switch all uses of `enabled` to `allowed`.
Switch all uses of `not disabled` to `allowed`.

Change-Id: Ia2c951e0b40131650ee8fd1d7f76a322686a3898
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
1 file changed
tree: 5b162860a90e7a47241888842e5618b8c4e5d679
  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).