| commit | f6825b916c8a0c252511ff8b3bdfada05031b7f4 | [log] [tgz] |
|---|---|---|
| author | Nan Zhou <nanzhoumails@gmail.com> | Tue Sep 20 20:52:43 2022 +0000 |
| committer | Nan Zhou <nanzhoumails@gmail.com> | Tue Sep 20 20:53:02 2022 +0000 |
| tree | 746cb002f74357425a8ff0445136fb23e0c6f09f | |
| parent | dc7770153b8fdfca26f1e7fd038033dff6b20456 [diff] |
virtualSensor: change EM's ObjectManager path EntityManager moves its ObjectManager in commit [1], this patch is to change accordingly. Please see [1] for why we made that change. [1] https://gerrit.openbmc.org/c/openbmc/entity-manager/+/57279 Tested: code compiles. I don't have a system with this repo enabled. But code inspection can show that only ObjectManager path changed. Signed-off-by: Nan Zhou <nanzhoumails@gmail.com> Change-Id: Ib5460433558d9d9d5e12465fe3d78a92159c573b
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).