| commit | a47e082e2180e995648d8241844c9db7392d70f8 | [log] [tgz] |
|---|---|---|
| author | Andrew Jeffery <andrew@codeconstruct.com.au> | Thu Jan 04 11:11:32 2024 +1030 |
| committer | Andrew Jeffery <andrew@codeconstruct.com.au> | Fri Jan 12 01:48:55 2024 +0000 |
| tree | 28f88ff9ad006c820baeb21c0d8cdf521366d191 | |
| parent | e4f21f808916fb03a0163a746bc4f0ea813e7946 [diff] |
subprojects: Bump boost to 1.83
Bump to avoid issues such as the following:
```
In file included from ../src/Utils.hpp:3,
from ../src/Thresholds.hpp:3,
from ../src/sensor.hpp:6,
from ../src/PwmSensor.hpp:3,
from ../src/PwmSensor.cpp:17:
../src/VariantVisitors.hpp:18:10: fatal error: boost/type_index.hpp: No such file or directory
18 | #include <boost/type_index.hpp>
| ^~~~~~~~~~~~~~~~~~~~~~
```
1.83 is used by openbmc/openbmc@43471c8c565d346c1727ba2360db373035234c26
With the bump I can now successfully build dbus-sensors on Debian
Bookworm with `meson setup --cross-file=gcc-13 build`[1], even if boost
libraries and headers of varying version are installed via `apt`.
[1]: https://amboar.github.io/notes/2023/09/12/unstable-gcc-on-debian-stable.html
Change-Id: I43cb95167ede3271cc6ce6ea6ea5421911b575c0
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.