| commit | fcbf32d0dc6c2cff58dfd5ce581a431425531a59 | [log] [tgz] |
|---|---|---|
| author | Josh Lehan <krellan@google.com> | Tue Oct 08 12:02:49 2019 -0700 |
| committer | Josh Lehan <krellan@google.com> | Wed Oct 09 21:26:43 2019 +0000 |
| tree | 19fbbd317a4b8e43178e65770eb3c038124b5937 | |
| parent | 166850f952213a5d6f16b48aafae724b68aee2c4 [diff] |
Ensuring EntityManager starts before all Sensor services This fix was needed by PSUSensor However, all of these Sensor services are written in a similar way All could probably benefit from this similar fix Adds Requires and After for EntityManager Also clean up dangling Requires that did not have After Tested: On PSUSensor only Signed-off-by: Josh Lehan <krellan@google.com> Change-Id: Ib132b642b88dfb344b28d27d55dfd89b49e917f4
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