| commit | 8e11cccbd23b7a78e95bdafe0e93d19481eb4408 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Fri Jul 22 19:26:57 2022 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Fri Jul 22 19:26:57 2022 -0500 |
| tree | 5a3fe6d1d36c665cc6502e82b4a637c9b5ad29f8 | |
| parent | 190f6d06f563000eb0970d96247c453c00452933 [diff] |
sdbusplus: use shorter type aliases The sdbusplus headers provide shortened aliases for many types. Switch to using them to provide better code clarity and shorter lines. Possible replacements are for: * bus_t * exception_t * manager_t * match_t * message_t * object_t * slot_t Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I8c73d8de128b218ee4885a5e133314ad5d9a0ff8
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).