| commit | a959678ca810529e886adc40bcc4c8c59c0ee0e4 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Fri Apr 15 10:20:07 2022 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Fri Apr 15 10:20:10 2022 -0500 |
| tree | 28e7904366c1506c7e2722ab874d62c90e51fde2 | |
| parent | 03c4c8e263d1c756299e1f63398412b247c19760 [diff] |
expression: limit JSON value copy Switch 'auto' to 'auto&' to minimize the unnecessary JSON object copy. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: If2f89f1b7a895051f1fc240d8199b721788509ec
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).