| commit | 8d691e2753fda96e8bc7d45e546a8ec4612ca5bf | [log] [tgz] |
|---|---|---|
| author | Patrick Rudolph <patrick.rudolph@9elements.com> | Mon Sep 11 10:43:28 2023 +0200 |
| committer | Patrick Rudolph <patrick.rudolph@9elements.com> | Mon Nov 06 10:10:18 2023 +0100 |
| tree | 6d579cf1ef944fec59cfb8ed9cdae050119783a5 | |
| parent | 3ae1cb0979a3e76a2e1a95a36ea6dd919225c3e3 [diff] |
psusensor: Add support for MAX5970 MAX5970 support has been recently enabled in Linux [1] and is required for IBM Genesis3/SBP1. While the MAX5970 is an eFuse and not a regulator it's threated as such by setting a fixed output voltage that is always equal to the input voltage. MAX5970 provides input voltage and current readings. 1: https://github.com/torvalds/linux/commit/f5afdd13ed6c643c7243e685fe3cf5484b3fdfae Change-Id: I0aaecc92ad2fdb9a875a08301004cacb6dee1cce 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.