| commit | 26959667e5a6b0f825cf2dd57c465bc246a9dceb | [log] [tgz] |
|---|---|---|
| author | George Liu <liuxiwei@inspur.com> | Thu Jul 28 15:33:55 2022 +0800 |
| committer | George Liu <liuxiwei@inspur.com> | Thu Jul 28 15:33:55 2022 +0800 |
| tree | 107a6d1c28ec0aa56d85311edff25112b68e6294 | |
| parent | 26ef5a65ca347a93b3e81565b46ccb99bd36f3d5 [diff] |
Update to latest clang-format Refer:https://github.com/openbmc/docs/blob/ac5d544553934f8083c61c5986a1420261bc8a4c/style/cpp/.clang-format Signed-off-by: George Liu <liuxiwei@inspur.com> Change-Id: I80f24d12c18074b3294b158c2a2a515d548aa0e1
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).