| commit | 091c92c0e1b320228abf3385e5284cc14ef20f68 | [log] [tgz] |
|---|---|---|
| author | Jayashree Dhanapal <jayashree-d@hcl.com> | Tue Jan 11 14:55:20 2022 +0530 |
| committer | Jayashree Dhanapal <jayashree-d@hcl.com> | Wed Jan 12 18:22:43 2022 +0530 |
| tree | 13335883d309f2e98b0aa0541dd1d1dd010cb045 | |
| parent | 3ec41c53ac70b69b023d7ed92bd2908104d7cdf4 [diff] |
Add Softshutdown and Hardshutdown threshold interface Added threshold interfaces like Softshutdown and Hardshutdown interfaces in dbus-sensors. This is similiar to warning and critical threshold interfaces. To enable this Softshutdown and Hardshutdown interfaces, need to set the Severity level in EM config. Severity value as 2 for Softshutdown and Severity value as 3 for Hardshutdown. TESTED: Tested on Facebook YosemiteV2 hardware. Verified the Hardshutdown and Softshutdown interfaces are created and displaying in dbus objects. Signed-off-by: Jayashree Dhanapal <jayashree-d@hcl.com> Change-Id: Ic9a6e719a8343321f894bc031688a17a3ed7fd67
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