| commit | 91354e4ba7c3fc2a72891559d44c32d95e098dec | [log] [tgz] |
|---|---|---|
| author | Ed Tanous <edtanous@google.com> | Tue Oct 04 18:05:44 2022 -0700 |
| committer | Ed Tanous <edtanous@google.com> | Tue Oct 04 18:05:44 2022 -0700 |
| tree | 5d397b76dcc0f39f8953c8e51901518fcf14427a | |
| parent | f6825b916c8a0c252511ff8b3bdfada05031b7f4 [diff] |
clang-format-15 Format with clang-15 Signed-off-by: Ed Tanous <edtanous@google.com> Change-Id: I7f8b90e8bfc48f996ac5bee4c7cbc66ecafa318c
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).