| commit | 5b3542ead70094b79aadcbba51205f48ba0cd8e7 | [log] [tgz] |
|---|---|---|
| author | George Liu <liuxiwei@inspur.com> | Tue Oct 31 17:27:12 2023 +0800 |
| committer | Zhikui Ren <zhikui.ren@intel.com> | Mon Jan 22 16:16:54 2024 +0000 |
| tree | f331dcf20219cd2295bc522a80c50a33be6eec68 | |
| parent | bcb062a07898594b0dae8f0b961bfee7875cd16f [diff] |
psusensor: Optimize the naming of some variables Some variable declarations and parameter types use `boost::container::flat_map`. The long type names make it difficult for other developers to read. This commit makes some minor optimizations, using `using` to declare an alias to increase the readability of the code. Tested: built psusensor successfully and works fine. Signed-off-by: George Liu <liuxiwei@inspur.com> Change-Id: I9b632c27fc67694d2de384f6e7c88bf66b97f78e
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.