| commit | 39fadb9ef890e9b7393c8e993da55c651dd19d2c | [log] [tgz] |
|---|---|---|
| author | Matt Simmering <matthew.simmering@intel.com> | Thu May 04 21:47:29 2023 -0700 |
| committer | matthew.simmering <matthew.simmering@intel.com> | Thu Sep 14 19:44:27 2023 +0000 |
| tree | 62445de61833b4ae687d822f47a182b87de1d4bd | |
| parent | 016097cdd810505f3f8f28e04648870be55abc6b [diff] |
psusensor: Add extra CPU presence logic In the case of the psusensor service restarting we still need to check for CPU presence. This adds a handler that will get the number of CPUs that the BMC has in inventory. Tested: CPU presence map gets populated correctly. Change-Id: I17caba6cb602d34852270035fbbf71f3095b96be Signed-off-by: Matt Simmering <matthew.simmering@intel.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.