| commit | 8aeffd91ff3434f7812e9fdb6b0b03c6119921dd | [log] [tgz] |
|---|---|---|
| author | James Feist <james.feist@linux.intel.com> | Mon Sep 14 12:08:28 2020 -0700 |
| committer | James Feist <james.feist@linux.intel.com> | Mon Sep 14 21:10:02 2020 +0000 |
| tree | 39f29179b714a009a2c6cf7a06cdf7f6a753edb7 | |
| parent | 3f07764ca2457ff05ceb3d22d21ce3b70c8305ae [diff] |
Add retries into power control status commands On first boot we're seeing an occasional miss of the power status, but the match never being fired. This seems to be caused by the sensors overwelming power control by requesting too often. Add in a couple retries to make sure we get the status. Tested: On system with 100% production rate, cpu sensor readings were valid Change-Id: I19d3a342558db95c3a55ed8cb287df6629818c6a 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