| commit | 27faf7ca7d7b6ed3d47b450763b09bc240ccf91e | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Fri Apr 29 14:26:49 2022 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Fri Apr 29 14:26:56 2022 -0500 |
| tree | ff3faed2a8eba2980ea80bfc9cba34d51cb52329 | |
| parent | a959678ca810529e886adc40bcc4c8c59c0ee0e4 [diff] |
markdownlint, prettier: enable formatting Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I3f1eb4fd602cf9f6403836e554ad6d6f6e76f9db
phosphor-virtual-sensor reads in virtual_sensor_config.json 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. At this stage 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).