| commit | f8fcdc2a9cb4bef1ddf3676ca84833acfbc79f8d | [log] [tgz] | 
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Wed Jul 09 11:27:40 2025 -0400 | 
| committer | Patrick Williams <patrick@stwcx.xyz> | Wed Jul 09 11:27:40 2025 -0400 | 
| tree | d7e7692fea56d1423b6ca9a5f442479e62f12325 | |
| parent | 845976677374232158458f876bf405729b092a1a [diff] | 
meson: use non-deprecated systemd packageconfig Systemd's packageconfig file has both `systemdsystemunitdir` and `systemd_system_unit_dir` defined. The non-underscore one appears to be a deprecated alias[1]. Move to the non-deprecated / underscore-separated variant. [1]: https://github.com/systemd/systemd/commit/4908de44b0a0409f84a7cdc5641b114d6ce8ba03 Change-Id: Ie551c0d3549c73c33e31ccb17149d4ad16170adb Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
phosphor-virtual-sensor reads the configuration file virtual_sensor_config.json from one of three locations:
/var/lib/phosphor-virtual-sensor/usr/share/phosphor-virtual-sensorBy default the repository will install a sample config into (3).
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" } }
Sensors added this way can only use a set of restricted calculations. Currently supported types are Average, Maximum, Minimum, Sum and 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).