| commit | 45f2702d3377aea10dd11f02299fcede4c707d69 | [log] [tgz] |
|---|---|---|
| author | Jayashree Dhanapal <jayashree-d@hcl.com> | Tue Dec 07 12:56:35 2021 +0530 |
| committer | Jayashree Dhanapal <jayashree-d@hcl.com> | Wed Dec 29 07:12:03 2021 +0000 |
| tree | 72f5917943f28cd911a102ddd32061e8d6751ec2 | |
| parent | 0b207a624f925460797a51974b77b275d4c05e30 [diff] |
Refactoring threshold properties code. Multiple threshold interfaces like Hardshutdown and Softshutdown needs to be created for sensors. Therefore, array has been created to store multiple properties of thresholds. Threshold level, direction and properties can be accessed based on the array created. Moreover, lines of code has been reduced by refactoring existing threshold code. TESTED: Tested on Facebook YosemiteV2 hardware. Verified that the Warning and Critical interfaces and properties are created and displaying in dbus objects. Signed-off-by: Jayashree Dhanapal <jayashree-d@hcl.com> Change-Id: I98be6dd723a6f66336147ec572f161a6c5df3691
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