commit | 7e295e295ee7165592a33a1d624b2c068cfeca44 | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Thu Aug 04 11:40:14 2022 -0500 |
committer | Patrick Williams <patrick@stwcx.xyz> | Thu Aug 04 11:40:14 2022 -0500 |
tree | f7a3c9ee92f14f5f14fd0d8cebf37e6cedb561f0 | |
parent | 26959667e5a6b0f825cf2dd57c465bc246a9dceb [diff] |
MAINTAINERS: remove file The MAINTAINERS file is deprecated in favor of OWNERS. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I7f4b5c513d6c5c84b960972da30bddba9c38d178
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).