| commit | 41f49c0339096d5ed06d15c5e77d3382c125389d | [log] [tgz] |
|---|---|---|
| author | Zev Weiss <zev@bewilderbeest.net> | Wed Sep 21 17:27:18 2022 -0700 |
| committer | Zev Weiss <zev@bewilderbeest.net> | Thu Sep 22 12:39:08 2022 -0700 |
| tree | 9bb38b80354327780fd2db0715a4dd8f769df93f | |
| parent | 3ee959ad5e8691e352f1a8424a0dafe0d8ceaff0 [diff] |
DeviceMgmt: add I2CDeviceParams::deviceStatic() method This will be used to determine whether a given i2c device is statically instantiated via a device tree or if it's a dynamically-created device managed by userspace. As dbus-sensors daemons assume responsibility for device lifecycle management this can be used to distinguish between static and dynamic device nodes even if a previous process crashed after instantiating one (whereas a simple presence check might mistake a device that was instantiated but not cleaned up for a static device and thus never remove it). Signed-off-by: Zev Weiss <zev@bewilderbeest.net> Change-Id: I3911b0cace60689766993a8be3b8f160f71de2d1
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.