| commit | 63f386691107a67e5fbfeb11fbac4f434d7a3ee6 | [log] [tgz] |
|---|---|---|
| author | Zbigniew Kurzynski <zbigniew.kurzynski@intel.com> | Tue Jun 09 13:02:11 2020 +0200 |
| committer | Zbigniew Kurzynski <zbigniew.kurzynski@intel.com> | Tue Jun 09 13:24:32 2020 +0200 |
| tree | ad2da6f3b09ca73542b2012179cd823068262e27 | |
| parent | 38786d027f12e2f8204c210811cc9f10207e4a47 [diff] |
Moving some methods from threshold to utils
Two methods splitFileName and readFile seems to be more generic
and used not only by thresholds. Moving splitFileName and readFile
from the threshold namespace to utils.
Tested:
Manual tests where done on CPUSensor. No differences detected
comparing to results before these changes.
Signed-off-by: Zbigniew Kurzynski <zbigniew.kurzynski@intel.com>
Change-Id: I8ab58099eca740b6111a382f68f2ab32d7762a78
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