| commit | e3338528bbf422655610e7414a5c7b886558d135 | [log] [tgz] |
|---|---|---|
| author | James Feist <james.feist@linux.intel.com> | Tue Sep 15 15:40:30 2020 -0700 |
| committer | James Feist <james.feist@linux.intel.com> | Tue Sep 15 23:21:02 2020 +0000 |
| tree | e0463feaef13ff226d51f92ca11c306737a551c0 | |
| parent | d3da1280dd996d1c4677fdfb2c98bb95ed11f718 [diff] |
Move dbus connection into base sensor object This seems common through most sensors, might as well move it for consistency. Tested: sensors operational as normal Change-Id: I4e6c55cbb7171ee51700015f8c2ef8c05c90fb4e Signed-off-by: James Feist <james.feist@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