| commit | d653b75cd14493150b3823acb8eeeff1218c6284 | [log] [tgz] |
|---|---|---|
| author | Bruce Mitchell <bruce.mitchell@linux.vnet.ibm.com> | Mon Aug 23 13:09:00 2021 -0500 |
| committer | Bruce Mitchell <bruce.mitchell@linux.vnet.ibm.com> | Mon Aug 23 13:27:10 2021 -0500 |
| tree | 1833abe52c1ab8ac3689cfdbdbed292240a0fc34 | |
| parent | f1ace50bbb781c0febd15387110d1a03b11391f9 [diff] |
Corrects bug in using boost::container erase() Shawn pointed out an existing bug using boost::container erase() described here: https://gerrit.openbmc-project.xyz/c/openbmc/\ dbus-sensors/+/43410/70..74/src/IIOMain.cpp#196 This fixes that bug. Tested: on Everest's Storm King Op Panels with busctl introspect \ --no-pager xyz.openbmc_project.HwmonTempSensor /xyz/openbmc_project/\ sensors/temperature/Ambient_0_Temp Results functioning properly and consistent with location of the systems. Signed-off-by: Bruce Mitchell <bruce.mitchell@linux.vnet.ibm.com> Change-Id: Ibe5293c389cdd5796755e6d5bf41000d4c6d1c80
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