nvmesensor: dynamic MCTP matching via BusInfo Removed the requirement for static MctpReactorConfigPath in NVME1000 Entity Manager configurations. Instead, implemented a dynamic matching mechanism based on physical topology (BusInfo). Added a background listener in MctpUtil that monitors associations between MCTP endpoints and Entity Manager configurations. When an association appears, it queries the configuration properties on demand and caches the full SensorData. Updated handleConfigurations in NVMeSensorMain to perform the matching by iterating over the cached configurations and comparing BusInfo with the sensor's BusInfo on the fly. This pushes the matching logic to the consumer and makes it future-proof against schema changes. Added cache priming on startup to handle pre-existing associations and configurations, ensuring listeners are registered before queries to avoid race conditions. Added a new constructor to MctpReactorDevice to accept a pre-resolved endpoint path, bypassing the Object Mapper lookup in setup(). This change decouples nvmesensor from static paths and specific setup agents, enabling support for dynamic buses like USB. Change-Id: I827a25b7e7d6cba2f7cf1e60c351b39f03b4d4dc 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.