| commit | 3bcd823e3783bc49c1e75dec2d43a3ef54333c88 | [log] [tgz] |
|---|---|---|
| author | Josh Lehan <krellan@google.com> | Thu Oct 29 00:22:12 2020 -0700 |
| committer | Josh Lehan <krellan@google.com> | Mon Nov 09 17:54:41 2020 -0800 |
| tree | 458cd31808f61f74ccf8d652d1a7cf4f61788828 | |
| parent | 381636e2e13ca544039f6dca5d330a7e8498b0fa [diff] |
Add optional sensor reading logging instrumentation Noteworthy sensor readings, such as the first reading, a new minimum or maximum value, or ending a good or bad streak of readings, will now have some useful logging output. This feature defaults to disabled, to enable it, set "enableInstrumentation" constant to "true". Tested: It runs, and produces useful output, when enabled. When disabled, it does nothing. Signed-off-by: Josh Lehan <krellan@google.com> Change-Id: I4c1b5105ad6dbb92ae6a23f2b99e2a8b68b56dca
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