| commit | 375ade29c1d06d54e827b1f8a2e15193d7036fee | [log] [tgz] |
|---|---|---|
| author | James Feist <james.feist@linux.intel.com> | Thu Jul 16 16:32:10 2020 -0700 |
| committer | James Feist <james.feist@linux.intel.com> | Tue Jul 21 21:45:07 2020 +0000 |
| tree | f6f29e5d3b5ff81f4a6b0493a6359cecc45465e2 | |
| parent | 59b8b9e5a5cfe67c74c5073aadff5baf8fd17d11 [diff] |
Fix NvmeSensor assert As NvmeSensor has many async captures, deleting the NvmeContext is not enough to make the destructor fire, we must also manually stop all timers and connections. Tested: DC Cycled, assert went away Change-Id: I64f3eab1451d73d723110a79ed5bb38419982088 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