| commit | 900ee39c244ff5f913781f002edb4ae0f3286cbe | [log] [tgz] |
|---|---|---|
| author | George Liu <liuxiwei@ieisystem.com> | Wed Dec 17 16:20:23 2025 +0800 |
| committer | George Liu <liuxiwei@ieisystem.com> | Wed Dec 17 16:20:23 2025 +0800 |
| tree | 0be24f0e99d5412f020245f65f281f89681d725e | |
| parent | 6272a39308bf6c1945edabf54891157c8079165a [diff] |
Remove redundant is_method_error() checks The handlers registered through sdbusplus::bus::match_t only receive D-Bus signals. Signal messages are never sent as method-error replies, and therefore message.is_method_error() can never be true in these callbacks. This change removes all unnecessary is_method_error() checks from signal handlers to simplify the code and avoid confusion. Change-Id: I1e29c0e6bf82d2bcaf61ca05984bb98420dac9fd Signed-off-by: George Liu <liuxiwei@ieisystem.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-sensorBy 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).