| commit | e4f21f808916fb03a0163a746bc4f0ea813e7946 | [log] [tgz] |
|---|---|---|
| author | Andrew Jeffery <andrew@codeconstruct.com.au> | Thu Jan 04 13:05:16 2024 +1030 |
| committer | Andrew Jeffery <andrew@codeconstruct.com.au> | Fri Jan 12 01:48:55 2024 +0000 |
| tree | c12cafdf3773cfc2d58165ce8bbcb4a1f57fdb80 | |
| parent | 1d7b4788943d5450e2c72965bb972369ae908b2c [diff] |
meson: Order dependencies as an approximate in-order tree traversal
meson appears to not be terribly fancy about resolving dependency
constraints. Dependencies appear to be evaluated in their order of
declaration, as an in-order tree traversal. This ordering is problematic
for escalating version constraints.
As a concrete example, we currently declare `dependency('sdbusplus')`
before `dependency('boost')`. sdbusplus itself depends on boost, without
a version constraint. If boost is available on the build system then
this is selected. However, dbus-sensors' boost dependency may have a
version constraint of e.g. >=1.83.0. In this arrangement we hit the the
following error:
```
sdbusplus| Run-time dependency Boost found: YES 1.81.0 (/usr/include)
...
Dependency boost found: NO found 1.81.0 but need: '>=1.83.0' (cached)
meson.build:67:8: ERROR: Dependency 'boost' is required but not found.
```
Declare (common) dependencies as an approximate in-order traversal to
avoid conflicts.
Change-Id: I0277061f3ac36361495183018293a61163d70a36
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.