commit | aedd2e2bb93b8b714d6c9fc3707ad5f9e8464447 | [log] [tgz] |
---|---|---|
author | Jiaqing Zhao <jiaqing.zhao@intel.com> | Sat May 21 22:14:20 2022 +0800 |
committer | Jiaqing Zhao <jiaqing.zhao@intel.com> | Sat May 21 22:25:54 2022 +0800 |
tree | 8cbadee53166b9c6f6ac4a17e2ab32ef1839ec59 | |
parent | 27faf7ca7d7b6ed3d47b450763b09bc240ccf91e [diff] |
README: Update Type for D-Bus config According to entity-manager schema, the first M of ModifiedMedian should be capitalized. Also adds a hyperlink to the schema. Tested: Configure phosphor-virtual-sensor with "Type": "ModifiedMedian", the sensor defined in entity-manager json is exposed successfully. Change-Id: I90fa91d3c45e24914610245eec43dd2924957855 Signed-off-by: Jiaqing Zhao <jiaqing.zhao@intel.com>
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).