| commit | 5667808ac51d3dbb61829b7e420c56f401d57edf | [log] [tgz] |
|---|---|---|
| author | Jayashree Dhanapal <jayashree-d@hcl.com> | Tue Jan 04 17:27:20 2022 +0530 |
| committer | Jayashree Dhanapal <jayashree-d@hcl.com> | Mon Jan 10 18:10:40 2022 +0530 |
| tree | a53afb128791ed88ccd2ef3b30a3411b128fd5f8 | |
| parent | 3c969f656faa6c5301a7918810a7331b824295b0 [diff] |
Move threshold interfaces to common function Threshold Hardshutdown and Softshutdown interfaces needs to be created for sensors. Therefore, created a common function called getInterface() to access all the threshold interfaces from all the sensors source file and removed hasCriticalInterface(), hasWarningInterface() functions. Moreover, threshold interfaces from all the sensor constructor has been refactored to avoid duplicating functions. TESTED: Tested on Facebook YosemiteV2 hardware. Verified that the Warning and Critical interfaces are created and displaying in dbus objects. Signed-off-by: Jayashree Dhanapal <jayashree-d@hcl.com> Change-Id: I9c7d049c7d4445d7199bf63d8e729838990880e9
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