commit | 98be984491da67666534f9b958fa689ca22d645c | [log] [tgz] |
---|---|---|
author | Zbigniew Kurzynski <zbigniew.kurzynski@intel.com> | Mon Sep 07 18:49:15 2020 +0200 |
committer | Zbigniew Kurzynski <zbigniew.kurzynski@intel.com> | Tue Sep 15 06:41:18 2020 +0000 |
tree | 5fec0c041053cbbd89ddc1e77ce501c25e1a4a32 | |
parent | 8aeffd91ff3434f7812e9fdb6b0b03c6119921dd [diff] |
Reading min, max values for ‘cap’ every 8 times. There is no need to read min and max values of CPU capabilities with every second. The CPU capabilities doesn’t change to often if ever. The hwmon updated the cap files with cycle of 10sec. Reading min and max value every 8 times should be enough in this case. Tested: Working as expected, no regression detected. Signed-off-by: Zbigniew Kurzynski <zbigniew.kurzynski@intel.com> Change-Id: I86c6b5542d3e2f3475aef3c5b05b305f87c6ef39
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