commit | 5f07fa36bbca2e9c02cb2b7f1dba0fa618a48cf9 | [log] [tgz] |
---|---|---|
author | Manojkiran Eda <manojkiran.eda@gmail.com> | Mon Jun 17 14:26:17 2024 +0530 |
committer | Manojkiran Eda <manojkiran.eda@gmail.com> | Mon Jun 17 14:27:27 2024 +0530 |
tree | aa568d6cfd4d7809928b392d8fe00b10532f3d6c | |
parent | 9358f6bda1b5bcbf300fdb67804dc16a91ac7acc [diff] |
Fix spelling mistakes using codespell This commit corrects various spelling mistakes throughout the repository. The corrections were made automatically using `codespell`[1] tool. [1]: https://github.com/codespell-project/codespell Change-Id: Ib9913e28d2bd3a9cf98e47326a57d9b35ab223ef Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
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", "Type": "ModifiedMedian" } }
Sensors added this way can only use a set of restricted calculations. Currently 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).