| commit | f69fbf998745bf006748c3b6ba6558443b560d21 | [log] [tgz] |
|---|---|---|
| author | Ed Tanous <edtanous@google.com> | Fri Jan 14 10:15:33 2022 -0800 |
| committer | Ed Tanous <ed@tanous.net> | Tue Jan 25 19:27:34 2022 +0000 |
| tree | a1fe591ee9f1cd5ecf5c93490a53a93742470f88 | |
| parent | 62fd8073d11ca26695f0c90d1a93e11c7059f079 [diff] |
Consistently use std::pair<double, double> limits There are a number of places in tach sensor where we jump from having a pair of doubles, so having a pair of ints, then back. All sensors take this as a double, so we should be consistent, even if tachsensor is only expected to have integer units. This was flagged by clang-tidy as part of the bugprone-misplaced-widening-cast check. Signed-off-by: Ed Tanous <edtanous@google.com> Change-Id: Iee1439f3af2bf8c15dc33f91c63859c5d1b776ca
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