mctp: refactor matching logic and priming query Refactored the MCTP matching logic to remove code duplication and improve maintainability. 1. Extracted the physical topology extraction logic from NVMeSensorMain into a shared helper function `extractBusInfo` in MctpUtil. This removed identical duplicate extraction loops that were used for both the sensor configuration and the cached endpoint configurations. 2. Merged the cache priming D-Bus query for associations with the `performEmConfigQuery` function in MctpUtil. This eliminated the redundant `GetManagedObjects` call and inline property parsing, ensuring all EM queries follow the same execution and state tracking path. 3. Fixed inconsistent state setting in the cache priming loop to ensure we don't trigger redundant queries on startup for existing devices. Change-Id: I6d5495e4be2b864cde90b4dfec805b2815e3e395 Google-Bug-Id: 490106522 Signed-off-by: Hao Jiang <jianghao@google.com>
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
A typical dbus-sensors object support the following dbus interfaces:
Path /xyz/openbmc_project/sensors/<type>/<sensor_name>
Interfaces xyz.openbmc_project.Sensor.Value
xyz.openbmc_project.Sensor.Threshold.Critical
xyz.openbmc_project.Sensor.Threshold.Warning
xyz.openbmc_project.State.Decorator.Availability
xyz.openbmc_project.State.Decorator.OperationalStatus
xyz.openbmc_project.Association.Definitions
Sensor interfaces collection are described here.
Consumer examples of these interfaces are Redfish, Phosphor-Pid-Control, IPMI SDR.
dbus-sensor daemons are reactors that dynamically create and update sensors configuration when system configuration gets updated.
Using asio timers and async calls, dbus-sensor daemons read sensor values and check thresholds periodically. PropertiesChanged signals will be broadcasted for other services to consume when value or threshold status change. OperationStatus is set to false if the sensor is determined to be faulty.
A simple sensor example can be found here.
Sensor devices are described using Exposes records in configuration file. Name and Type fields are required. Different sensor types have different fields. Refer to entity manager schema for complete list.