| commit | a2c7cea47f1708e6d8199061ca62da9b4a195946 | [log] [tgz] |
|---|---|---|
| author | Lei YU <yulei.sh@bytedance.com> | Wed Dec 23 14:07:28 2020 +0800 |
| committer | Ed Tanous <ed@tanous.net> | Wed Mar 10 04:58:45 2021 +0000 |
| tree | 6bc7e0c395725048188bc0563c4128870a906349 | |
| parent | a0683a889a12bf665595ccdcb349c5f4ab321eea [diff] |
psusensor: Fix incorrect event sensors
The event sensors are expected to track the sysfs paths that are in
limitEventMatch.
However, the code incorrectly adds paths like `tempx_max` into the event
sensors because it replace `input` with `xxx_alarm` and check if the
path exists or not.
When the path does not include `input`, it is not changed at all and the
path does exist, thus it is added into the event sensors incorrectly.
Fix it by checking the above case and skip such path.
Tested: Verify the sensors like `temp1_max` is not added into the event
sensors anymore.
Signed-off-by: Lei YU <yulei.sh@bytedance.com>
Change-Id: I219cb8ef966fc00c121359b0b1bcfc2b68cf0216
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