| commit | f7ec40aa6c804f5e6a01a06b5a705bbb2168c63a | [log] [tgz] |
|---|---|---|
| author | Ed Tanous <edtanous@google.com> | Tue Oct 04 17:39:40 2022 -0700 |
| committer | Ed Tanous <edtanous@google.com> | Tue Oct 04 18:06:00 2022 -0700 |
| tree | 1b63f40b2b5b5abc10eff308be5a26129f352902 | |
| parent | 91354e4ba7c3fc2a72891559d44c32d95e098dec [diff] |
Move objectmanager into the PDI-specified location PDI specifies that the ObjectManager for sensors should be hosted at the sensor root. This commit makes that a reality. Tested: Could use some help here. I don't use phosphor-virtual-sensors, but other similar changes made to other daemons have been tested, along with the other patches in this topic. [1] https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/yaml/xyz/openbmc_project/Sensor/Value.interface.yaml#L18 Signed-off-by: Ed Tanous <edtanous@google.com> Change-Id: I45cead6eaa841140dd88364131b94d628ccfdaa8
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).