| commit | c8fed20b29ec8a33190a02860bfa3b44cfb828ed | [log] [tgz] |
|---|---|---|
| author | Ed Tanous <edtanous@google.com> | Wed Jan 12 14:24:45 2022 -0800 |
| committer | Ed Tanous <ed@tanous.net> | Sat Feb 05 17:12:32 2022 +0000 |
| tree | 3b624fb4dd196e25e3e01aed0442b2c65a4d9808 | |
| parent | 74cffa8846cae2b083713cbf612d43f4b7f35432 [diff] |
Rearrange thresholds to be pair based It was pointed out in another review that the way the dbus interfaces are set up, they are all pair-wise, with a positive and negative end of the interface. This changes the data structures to match that reality, inventing a "ThresholdDefinition" object. This reduces the code, and allows us to promote the level definitions up to a higher scope in the structure. This greatly simplifies the thresProp structure to remove a number of elements that were redundant, and allows adding new thresholds easier in the future. Tested: Tested on Vegman system; Thresholds work as designed. Signed-off-by: Ed Tanous <edtanous@google.com> Change-Id: Ic9d5ba8282f78fe928689cb7fbd98d575a570200
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