| commit | b729eac553278609494e30a37c63fec4ef62b7af | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Mon Mar 21 10:14:47 2022 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Mon Mar 21 10:14:49 2022 -0500 |
| tree | b72532d4def9fca79892c92c68634fa4bdc6bc09 | |
| parent | 1204b43374720e9b338ea0aa6be75d8d27e0477e [diff] |
meson: simplify dependencies Leverage wrapfile `[provide]` directives to simplify the dependency searching in the meson.build. Change-Id: I01c308089b1b6586f552a10cbcd0641faec4ae26
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).