| commit | 0d4f2bdd0fff0db4546b6f78fc7b9982cc157bbf | [log] [tgz] |
|---|---|---|
| author | James Feist <james.feist@linux.intel.com> | Tue Mar 05 13:15:40 2019 -0800 |
| committer | James Feist <james.feist@linux.intel.com> | Wed Mar 06 22:21:47 2019 +0000 |
| tree | 6f32e32ca8957a294dfbce71be832523cbeda8e0 | |
| parent | 87bf1dda9d9224a55c5e92f3e56c74a9aaa517bb [diff] |
ipmbsensor: Add delay to init cmd Sometimes we run the init cmd too early and we start getting sensor readings that are out of range. Normally this is only 1-2 sensors. Add in a delay so that hopefully this won't happen. Also don't print errors too often. Tested-by: Power cycled multiple times and never saw NA for sensor readings. Change-Id: Ib1d336fc5b04b2c96e41b5de2a89d26c7a6d3e83 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