| commit | 17551b8ba54de37ed84f3c56e052f481075e3a07 | [log] [tgz] |
|---|---|---|
| author | Ed Tanous <edtanous@google.com> | Wed Jan 26 16:47:17 2022 -0800 |
| committer | Ed Tanous <ed@tanous.net> | Fri Feb 11 17:09:47 2022 +0000 |
| tree | 193afb9d2f8d513bdf0a887b0fa71ce5e134a949 | |
| parent | 51ad6674d51e6ad0900a1236ec3606d1daa3363b [diff] |
Remove isValidLevel() Every usage of isValidLevel is done after the levels have been parsed and are already known to be correct. Checking that Level is valid is wasteful, and in some cases, is already checked by getThresholdInterface, which can already bounds check this. This check is not needed. Signed-off-by: Ed Tanous <edtanous@google.com> Change-Id: I1d03c1c66ae37ca86a48175ec9c739c2d3966662
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