commit | e667239d5a57ee3599c6378839e7858a545ae275 | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Fri Sep 02 09:03:24 2022 -0500 |
committer | Patrick Williams <patrick@stwcx.xyz> | Fri Sep 02 09:03:26 2022 -0500 |
tree | d3ae8689f297b3210b6f0c1e3c6f4c7687644c3e | |
parent | 7e295e295ee7165592a33a1d624b2c068cfeca44 [diff] |
remove dependency on sdeventplus This repository doesn't really use sdeventplus, other than for running the dbus-loop, but there is already trivial code in sdbusplus for that. Simplify and remove the dependency. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I8af7ad87a4fd87df400e810941fe58e412aedb24
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).