commit | 4224ca36acd8bf7089e1e2f566ef5235d0f86c97 | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Sat Feb 01 08:23:14 2025 -0500 |
committer | Patrick Williams <patrick@stwcx.xyz> | Sat Feb 01 08:23:14 2025 -0500 |
tree | 9759ee437a47238d8b58b5aee474c4880755db1e | |
parent | 76e6c5afb92c06c5ed925e92752cde0f52a9c493 [diff] |
clang-format: update latest spec and reformat Copy the latest format file from the docs repository and apply. Change-Id: I75589ffb25513a101efdcf6ce060538b5d000ffb 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" } }
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).