| commit | bfaf2387affaeb6db926bfd34a224a4a14355196 | [log] [tgz] |
|---|---|---|
| author | James Feist <james.feist@linux.intel.com> | Fri Apr 19 13:57:17 2019 -0700 |
| committer | James Feist <james.feist@linux.intel.com> | Fri Apr 19 14:12:53 2019 -0700 |
| tree | ad40b3d9ba7e9217347425b431da24a0fff2e778 | |
| parent | 55ab2afb4bf20269b47d0929eb337943a170bffd [diff] |
PSUSensor: Fix rescan behavior The original object needs to be destroyed instead of using the move constructor so the dbus remove and added messages happen in the right order. Tested: Sensors available at boot Change-Id: I1d95c4e9871c961d6b742f8d862555b6bd808cea 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