| commit | 49c17cbc22209de0f684f25126760096dce94b84 | [log] [tgz] |
|---|---|---|
| author | Jason Ling <jasonling@google.com> | Tue Oct 01 16:59:31 2019 -0700 |
| committer | Jason Ling <jasonling@google.com> | Thu Oct 03 11:38:54 2019 -0700 |
| tree | 328a9c27a52dafeae3f980f89d5c7e8030f9585f | |
| parent | 2adc95cb4d9ac879f66aa9ef12a6ce8b7c1578fe [diff] |
Force PSUSensors to start after EntityManager PSUSensors would start before EntityManager. This would cause an issue where PSUSensors would not be able to find the EntityManager service and as a result fail sensor creation. Tested: Reboot BMC, observed that PSUSensors started up after EntityManager instead of before Change-Id: I17a646038e923c37639d171eecbf1bee2d9fdc77 Signed-off-by: Jason Ling <jasonling@google.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