| commit | 4d97058755ec6fd0502fac7066f66606e26d56fe | [log] [tgz] |
|---|---|---|
| author | Patrick Rudolph <patrick.rudolph@9elements.com> | Mon Oct 16 17:06:54 2023 +0200 |
| committer | Andrew Jeffery <andrew@codeconstruct.com.au> | Fri Oct 20 05:13:46 2023 +0000 |
| tree | db71e0bbc6a53c6dabc0318495f2c57dd38ea0f9 | |
| parent | b886bfc5dbb3633a21e1a25df89951a56647d194 [diff] |
nvmesensor: Mark drives as unavailable Fix a race condition where the NVMe sensor is marked available even though there's no NVMe drive plugged. When the power is already on when the sensor is created it will never be marked as unavailable, but 'not operational' when the communication failed multiple times. It will remain in this state until power is turned off. Mark the sensor as unavailable in the constructor to catch this corner case. For present NVMe drives this will set the available state after the first NVMe MI packet has been received. Fixes failSafe mode in phosphor-pid-control when no drive is present. Change-Id: Ifa3dcc080ecc9ef21213b2a901cf41b2ca0a3de2 Signed-off-by: Patrick Rudolph <patrick.rudolph@9elements.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.