commit | 6736d4b2a77cec00a8919f26035176c8b8025a4d | [log] [tgz] |
---|---|---|
author | Andrei Kartashev <a.kartashev@yadro.com> | Fri Dec 18 18:59:21 2020 +0300 |
committer | Andrei Kartashev <a.kartashev@yadro.com> | Mon Dec 21 05:53:44 2020 +0000 |
tree | 29e149a2974f35ad373fe10f622aa4bd05c61e20 | |
parent | 937eb54e2fbdd917442bf359c8367219c23d4e36 [diff] |
cpusensor: change Min/Max values for power minValue and maxValue are currently hardcoded for all cpusensors to -128 and 127 respectively. There is no sense to have negative values for power sensors but CPU power consumption can be higher than 127W. Change Min/Max to 0...511 for power sensors. Tested: busctl introspect xyz.openbmc_project.CPUSensor /xyz/openbmc_project/sensors/power/Average_Power_CPU0 xyz.openbmc_project.Sensor.Value interface -- - .MaxValue property d 511 emits-change .MinValue property d 0 emits-change .Unit property s "xyz.openbmc_project.Sensor.Value.Unit.… emits-change .Value property d 64.393 emits-change writable Signed-off-by: Andrei Kartashev <a.kartashev@yadro.com> Change-Id: I0dafdd657194b1b4d709ce093b658a89120f81f9
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