| commit | b6c0b914438d89d689ea98b64f4243e8f0c6d3bc | [log] [tgz] |
|---|---|---|
| author | James Feist <james.feist@linux.intel.com> | Tue Jul 09 12:21:44 2019 -0700 |
| committer | James Feist <james.feist@linux.intel.com> | Tue Jul 09 12:21:44 2019 -0700 |
| tree | 116a0fd0677d274be8bad6c259a92dc90caa8279 | |
| parent | be66441fbd7767659e0c37e41543d886bb31b457 [diff] |
Turn on a bunch of warnings Turn on as many warnings as easily possible from: https://github.com/lefticus/cppbestpractices/blob/e73393f25a85f83fed7399d8b65cb117d00b2231/02-Use_the_Tools_Available.md#L100 Tested: ipmitool sensor list still works Change-Id: Ied8fa66de9fcd25e448f8048c4f8216b426b6f55 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