nvme: support bridged MCTP endpoints
Updated nvmed to support bridged MCTP endpoints by parsing a list of
BusInfo interfaces from Entity-Manager. Moved the matching logic into
MctpReactorDevice::setup() to keep the device self-resolving and
encapsulate discovery logic. Refactored MctpReactorBusInfo to
maintain root-to-leaf order for consistency, and added an operator==
overload for subset matching.
Example EM config for a bridged device:
```
{
"Protocol": "mi_mctp",
"Type": "NVME1000",
"xyz.openbmc_project.Configuration.NVME1000.BusInfo0": {
"BusType": "USB",
"Port": "1.5.1",
"RootHubPath": "/sys/devices/platform/ahb/f0806000.usb"
},
"xyz.openbmc_project.Configuration.NVME1000.BusInfo1": {
"BusType": "MCTP Bridge",
"EIDOffset": 2
}
}
```
Tested: Ran unit tests in Docker container (test_mctp_util, test_nvme).
Google-Bug-Id: 509971428
Change-Id: I8633ed947d1c58d6fb948f5e6bd43e8521fa042e
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.