| commit | 961bf09a2c89585601175e74ec3cb2590b911aa8 | [log] [tgz] |
|---|---|---|
| author | James Feist <james.feist@linux.intel.com> | Wed Jul 01 16:38:12 2020 -0700 |
| committer | James Feist <james.feist@linux.intel.com> | Thu Jul 09 21:46:50 2020 +0000 |
| tree | a498c96fefb1d1d7d385c6d9b86c998c9f4e2400 | |
| parent | d7ae29a3483a3150d97d1cd238b96ed61c3591c9 [diff] |
Standardize read errors Each sensor handled read errors their own way, making it inconsistant. This helps to align them all in the base class, so that error handling happens the same for each sensor. It also aligns the power state change handling. Tested: Tested DC Cycling and Enabling/Disabling ME to make sure functional change correctly Change-Id: I1a191d27629602e1ca3871d933af07b15bf9f331 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