| commit | cafd72f6b9ebb6d3be02a8733489a7221d339e18 | [log] [tgz] |
|---|---|---|
| author | Matt Simmering <matthew.simmering@intel.com> | Fri Dec 16 15:35:12 2022 -0800 |
| committer | Matt Simmering <matthew.simmering@intel.com> | Wed Aug 16 10:13:24 2023 -0700 |
| tree | 36e4fcdead6aa0d94a33ac30b791ca9e522ab7a7 | |
| parent | 38857578d7243fb60f2b266d291526b5b97d0fc5 [diff] |
psu-sensor: Add devmgmt and powercallback to PSU Some PSU sensors are dependent on system power state. Without change the device initialization would fail and dbus-sensors and entity-manager wouldn't come back to properly instantiate. Same intention as this hwmontempsensor change: https://github.com/openbmc/dbus-sensors/commit/a1456c4abafc697e7caa6b8e95ac9ddb35c4e7d1 Tested: Same sensors are getting created. Sensors are getting created/destroyed on host power events based on their PowerState. Signed-off-by: Matt Simmering <matthew.simmering@intel.com> Change-Id: I3ee719cf65df225f964148d3994eec4d758d72a1
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.