| commit | af6b87c7f269f6ed3521639284fc6672c42c8a0f | [log] [tgz] |
|---|---|---|
| author | Richard Marian Thomaiyar <richard.marian.thomaiyar@linux.intel.com> | Wed Apr 03 23:54:28 2019 +0530 |
| committer | James Feist <james.feist@linux.intel.com> | Mon Apr 08 17:21:28 2019 +0000 |
| tree | 6892f90cc219f14fc43ee2ee1bafa6d9292b646c | |
| parent | 5242795fcba76e0e212dadd58eea511981c90f81 [diff] |
Fix: Move overriding logic to base sensor class Instead of having the overridden value check inside each sensor type, move the same to sensor base class, so that any future addition of new sensor model, will be able to inherit this feature automatically Tested: 1. Verified the behaviour of overriden value by setting the Value property. 2. restarting the sensor initializes the value back correctly Change-Id: Iddf280cafcf6d9299e1edc13b942683bf60ea89b Signed-off-by: Richard Marian Thomaiyar <richard.marian.thomaiyar@linux.intel.com>
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