commit | ae10c529c629f3b09cca2edf870e453b8588af9b | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Fri Oct 20 11:19:44 2023 -0500 |
committer | Patrick Williams <patrick@stwcx.xyz> | Fri Oct 20 11:19:44 2023 -0500 |
tree | 51fb8d17ecf164de082dd0248da6f5add5b5f9b2 | |
parent | 14ef874265884320e4a31f5f39d6e964b2ef9b7b [diff] |
clang-format: copy latest and re-format clang-format-17 has some backwards incompatible changes that require additional settings for best compatibility and re-running the formatter. Copy the latest .clang-format from the docs repository and reformat the repository. Change-Id: I2c290b16ee59b4768ba96642db5c9317b8311ba3 Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
phosphor-virtual-sensor reads the configuration file virtual_sensor_config.json
from one of three locations:
/var/lib/phosphor-virtual-sensor
/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.
See virtual_sensor_config.json
in this repository for an example. Sensors added this way can use any expression that is accepted by exprtk.
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).