| commit | 9f3a74edba3a0379f4b172ed998d9aae2101a920 | [log] [tgz] |
|---|---|---|
| author | Jayashree Dhanapal <jayashree-d@hcl.com> | Thu Jan 06 12:05:06 2022 +0530 |
| committer | Ed Tanous <ed@tanous.net> | Wed Feb 23 05:20:20 2022 +0000 |
| tree | 5a89b6e478ca19234264301e68710b740a4d7b06 | |
| parent | 27cac0bec1c8bc2f84bd91d5e9f74f0459f5a8fa [diff] |
Fix for hwmontemp sensor to avoid invoking same sensor Refactored the code by constructing a map to store the sensor bus & address as key and sensor information as value. Instead of iterating sensor configuration for every hwmon path, this will make the code efficient by configuring sensor details before iterating hwmon paths. Moreover, once a sensor name is found and all the sensor names under each config is constructed, then, sensor config from the configMap is removed. Therefore, this will avoid invoking a constructor for same sensor under different hwmon paths. Tested: Tested in Facebook YosemiteV2 platform and verified the hwmontemp sensors. Signed-off-by: Jayashree Dhanapal <jayashree-d@hcl.com> Change-Id: Iae06b2e1d4245e2f455b1366924694a55d3b0a05
dbus-sensors is a collection of sensor applications that provide the xyz.openbmc_project.Sensor collection of interfaces. They read sensor values from hwmon, d-bus, or direct driver access to provide readings. Some advance non-sensor features such as fan presence, pwm control, and automatic cpu detection (x86) are also supported.
runtime re-configurable from d-bus (entity-manager or the like)
isolated: each sensor type is isolated into its own daemon, so a bug in one sensor is unlikely to affect another, and single sensor modifications are possible
async single-threaded: uses sdbusplus/asio bindings
multiple data inputs: hwmon, d-bus, direct driver access