| commit | 585d3a079d00382b1996740e78075867c03db3c7 | [log] [tgz] |
|---|---|---|
| author | Thu Ba Nguyen <tbnguyen@amperecomputing.com> | Tue Jul 20 20:25:15 2021 +0700 |
| committer | ThuBaNguyen <thu@os.amperecomputing.com> | Tue Jul 20 21:36:55 2021 +0700 |
| tree | bb7b359a2d8a7e097ae7fde06937a7f6bedda115 | |
| parent | 9f6d4fd6fad9a8d74e348317a13ee3c75e01b757 [diff] |
dbus-sensors: Change the host state match string When the CurrentHostState dbus property value ends with "Running", Dbus-sensors marks the host as running and starts reading the sensors with "PowerState=On" configuration. From commit "host state transitioning ...", phosphor-state-manager package updates the transition state "TransitioningToOff" or "TransitioningToRunning" to CurrentHostState property. This causes dbus-sensors detects the host is running when it is transiting to running state. This commit fixs that issue by changing the match string from "Running" to ".Running". Tested: 1. Power off the host. 2. Power on the host. 3. Make sure there is no threshold warnings/errors for the sensors with "PowerState=On" configuration. Signed-off-by: ThuBaNguyen <thu@os.amperecomputing.com> Change-Id: I3bde0f3d288614657869f54e286a2d690d92dcad
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