| commit | f20aa7c87360a0d2918377a86bbf04c85268d47d | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Tue Dec 06 10:40:07 2022 -0600 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Tue Dec 06 10:40:40 2022 -0600 |
| tree | ab168f361014b054add97f40caad038db8bbc4d7 | |
| parent | 83e3ac39fce0317b26cd7419d0d373541fa750da [diff] |
markdownlint: remove unneeded config Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Ic5b0d6fc23086236f7b371a82d02edf048df4354
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).