| commit | 3a18b860ec24e63ab98159abc46713dcf5acea49 | [log] [tgz] |
|---|---|---|
| author | Lei YU <yulei.sh@bytedance.com> | Fri Feb 05 13:55:08 2021 +0800 |
| committer | Lei YU <yulei.sh@bytedance.com> | Fri Feb 05 13:55:56 2021 +0800 |
| tree | 18903ca2cd2a14551f9e405279f473bfd178f59e | |
| parent | feb19ef095c4ab9ec037b2f23ab6318f59a96eab [diff] |
meson: Fix psusensor The psu sensor's process name was incorrectly set to psutempsensor and is inconsistent with the service unit. Fix this and use `psu` as the configure option instead of `psu-temp`, because it is really psusensor including temperature/current/voltage/fan sensors. Tested: Verify the build binary is named as `psusensor`. Signed-off-by: Lei YU <yulei.sh@bytedance.com> Change-Id: Iee6bcdbb948a58dd10cfe26ab268944f1f9a14e6
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