commit | 4b98de56a69895d0c26e9abd6e236a73a236263a | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Mon Feb 03 14:14:17 2025 -0500 |
committer | Patrick Williams <patrick@stwcx.xyz> | Mon Mar 03 16:05:46 2025 +0000 |
tree | 319e1fc84908457a4686beb2813bded36812acec | |
parent | d000018abdbdbe7b979e04bbaf2e1d62cad326c6 [diff] |
meson: reformat with meson formatter Apply the `meson format` results. Change-Id: Id7af795e402928290b31fb085bd12a715122545b 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).