commit | 96439f1fa20dd8ba83491860327956396911eb1d | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Thu Dec 07 12:16:44 2023 -0600 |
committer | Patrick Williams <patrick@stwcx.xyz> | Thu Dec 07 12:16:45 2023 -0600 |
tree | 249107dd424bed43dffc0da7b7febbceeca85261 | |
parent | f2e9422107583056bd2dac8ce3d6238bc7635126 [diff] |
meson: adjust nlohmann-json dependency Simplify the dependency directive and align with the usage in other repositories. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I6b140e3a26314de110902bb4dceb1e8c57d80c3c
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).