| commit | 6ee62940cb7e33290a2f5c3fa1a3286ae42e8806 | [log] [tgz] |
|---|---|---|
| author | Jayashree Dhanapal <jayashree-d@hcl.com> | Tue Dec 14 15:22:23 2021 +0530 |
| committer | Zhikui Ren <zhikui.ren@intel.com> | Fri Dec 09 23:50:02 2022 +0000 |
| tree | 57b1125972f5aa8f0a7528671c0209ae78107dac | |
| parent | 1e3842541db673c850625bfae4227fb88767a2a9 [diff] |
IpmbSensor:Add bus index for multiple IPMB bus
IPMB bus is a physical bus which is exposed using IPMB driver. IPMB
is an I2c based serial bus that interconnects the baseboard and
chassis management.
A BMC that includes IPMB interface support and also provides the
capability for system software to send and receive messages to
and from the IPMB using the BMC as a kind of communication
controller.
In OCP multi-host platform, multiple IPMB bus support is present.
Therefore, for each config, IPMB bus value will be passed from
entity-manager json config file.
Through this IPMB bus, BMC will send and receive messages and then
store the response for each configuration.
Example :
{
"Address": "0x01",
"Bus": "$bus",
"Name": "Temp_Sensor",
"Type": "IpmbSensor"
}
In the current patchset, only IPMB bus value is read and further
implementation using this value will be done in the following
patchset.
SDR Sensor :
https://gerrit.openbmc-project.xyz/c/openbmc/dbus-sensors/+/52164
https://gerrit.openbmc-project.xyz/c/openbmc/dbus-sensors/+/38905
IPMB GPIO State :
https://gerrit.openbmc-project.xyz/c/openbmc/dbus-sensors/+/47952
TESTED: Tested on Facebook YosemiteV2 hardware and verified the
IPMB bus value.
Signed-off-by: Jayashree Dhanapal <jayashree-d@hcl.com>
Change-Id: I0a47057da98ee81471ac9f6fac69a036853db7d1
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.