commit | 9358f6bda1b5bcbf300fdb67804dc16a91ac7acc | [log] [tgz] |
---|---|---|
author | Konstantin Aladyshev <aladyshev22@gmail.com> | Thu Mar 14 14:23:40 2024 +0300 |
committer | Konstantin Aladyshev <aladyshev22@gmail.com> | Thu Mar 14 14:23:40 2024 +0300 |
tree | f4e0802013ad7bf23aa5d767a25dfac59dda094d | |
parent | 96439f1fa20dd8ba83491860327956396911eb1d [diff] |
Add fan_pwm to the possible sensors Add fan PWM output to the list of supported sensor types. Change-Id: Ia0c7970934fe403d4e6e0142af78b7815bcff0c9 Signed-off-by: Konstantin Aladyshev <aladyshev22@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).