| commit | bbf22d8127d9f3830e2d413408ad00d2e07a3ddd | [log] [tgz] |
|---|---|---|
| author | Clyde Huang <chuang31@lenovo.com> | Thu Oct 27 09:36:27 2022 +0000 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Tue Nov 01 17:27:45 2022 +0000 |
| tree | 8b35649707a6a4fc401ebbf55d353ae5155f1c87 | |
| parent | f6b7e0a49db00a2286b8d0611133a7318df30bd5 [diff] |
fix the wrong URL link Signed-off-by: Clyde Huang <chuang31@lenovo.com> Change-Id: Idf447173d0b6f7cdc719b4850a15fcc88c5decdc
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).