MctpEndpoint: Integrate remove behavior into MctpdDevice
9498075d1375 ("Revert "MctpEndpoint: Introduce StaticEntity container
class"") outlines the need for a different design-point than we
set out on in ac513c858a9e ("MctpEndpoint: Introduce StaticEntity
container class"). The latter commit externalised the handling of
InterfacesRemoved events from the MctpDevice and MctpEndpoint classes
to use the signal as input to resume polling via a timer invoking
MctpDevice::setup(). This felt a little untidy at the time, but
manageable.
The improved understanding of the needs that drove the revert above
triggered me to reconsider this separation. Better encapsulation
of behavior is achieved by integrating the handling of endpoint
InterfacesRemoved signals into MctpDevice. MctpDevice is then
self-contained with respect to managing the lifecycle of its
MctpEndpoint. From here we can integrate handling of MctpDevice into
NVMeSensorMain such that its MctpEndpoint's remove event callback
triggers the required polling.
Change-Id: I7d0d69d7235c19ebfbdef83fe1094719fd82f2fd
Signed-off-by: Andrew Jeffery <andrew@codeconstruct.com.au>
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.