nvmed: Support NVMe Get/Set Feature for OCP Latency Monitor (FID 0xC5) Support NVMe Get and Set Feature commands for OCP Latency Monitor (FID 0xC5) across Controller scope in NVMeFeatureStore. This allows querying and configuring OCP latency monitor settings via 4096-byte payload buffer and exposing them over D-Bus. Extract getFeatureDataLen helper to support variable-length feature payloads and reject unsupported feature IDs with InvalidArgument. Tested: Verified via gbmc ci run nvmed (8/8 tests passed). Google-Bug-Id: 549207952 Change-Id: Ie4b2b0055b49f7daa9aefcab0713319abfefd91a Signed-off-by: Guangzong Chen <guangzong@google.com> TAG=agy CONV=c36db835-257f-47bf-84bb-b773d9cd7e86
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 in Sensor interfaces.
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 in the my_first_sensors example.
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.