commit | 845976677374232158458f876bf405729b092a1a | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Fri May 30 10:26:27 2025 -0400 |
committer | Patrick Williams <patrick@stwcx.xyz> | Fri May 30 10:26:27 2025 -0400 |
tree | 50a7829559195a5ecf2411ce9d25249fc328fd93 | |
parent | 04605fa2ad256f0bdedcfc1f9bcd1f24fdc4cd93 [diff] |
clang-tidy: format with config-clang-tidy Reformat the .clang-tidy file for consistency using the config-clang-tidy tool from openbmc-build-scripts. Change-Id: I2a292438a8ea2e71476284fa21e67ae238bd7e15 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-sensor
By 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).