commit | b886bfc5dbb3633a21e1a25df89951a56647d194 | [log] [tgz] |
---|---|---|
author | Andrew Jeffery <andrew@codeconstruct.com.au> | Wed Oct 11 23:25:43 2023 +1030 |
committer | Andrew Jeffery <andrew@codeconstruct.com.au> | Fri Oct 13 09:12:09 2023 +1030 |
tree | fcdeac4ff7f4f35df29eda50ab39a219e4815bb1 | |
parent | e98adf5bf33c6651fd9e854a37cc5056df5f683b [diff] |
subprojects: Fix libpeci provide variable name Since its introduction in libpeci with df5c868a14eb ("Declare meson dependency") the variable has been named `libpeci_dep`. It also appears that since its inception in 77141acb7f09 ("IntelCPUSensor: Use libpeci when communicating via peci-legacy") the variable name has been wrong in the dbus-sensors wrap. Fix the debus-sensors wrap so we can build with libpeci as a meson subproject. Tested: Before: ``` $ meson subprojects purge --confirm && rm -rf build ... $ meson setup build ... Executing subproject libpeci libpeci| Project name: libpeci libpeci| Project version: 1.0 libpeci| C compiler for the host machine: ccache cc (gcc 12.2.0 "cc (Debian 12.2.0-14) 12.2.0") libpeci| C linker for the host machine: cc ld.mold 1.10.1 libpeci| C++ compiler for the host machine: ccache c++ (gcc 12.2.0 "c++ (Debian 12.2.0-14) 12.2.0") libpeci| C++ linker for the host machine: c++ ld.mold 1.10.1 libpeci| Dependency sdbusplus found: YES 1.0.0 (cached) libpeci| Dependency systemd found: YES 252 (cached) libpeci| Dependency boost found: YES 1.81.0 (cached) libpeci| Build targets in project: 664 libpeci| Subproject libpeci finished. WARNING: Variable 'peci_dep' in the subproject 'subprojects/libpeci' is not found Dependency libpeci from subproject subprojects/libpeci found: NO src/meson.build:64:15: ERROR: Dependency 'libpeci' is required but not found. ``` After: ``` $ meson setup build ... Executing subproject libpeci libpeci| Project name: libpeci libpeci| Project version: 1.0 libpeci| C compiler for the host machine: ccache cc (gcc 12.2.0 "cc (Debian 12.2.0-14) 12.2.0") libpeci| C linker for the host machine: cc ld.mold 1.10.1 libpeci| C++ compiler for the host machine: ccache c++ (gcc 12.2.0 "c++ (Debian 12.2.0-14) 12.2.0") libpeci| C++ linker for the host machine: c++ ld.mold 1.10.1 libpeci| Dependency sdbusplus found: YES 1.0.0 (cached) libpeci| Dependency systemd found: YES 252 (cached) libpeci| Dependency boost found: YES 1.81.0 (cached) libpeci| Build targets in project: 664 libpeci| Subproject libpeci finished. Dependency libpeci from subproject subprojects/libpeci found: YES 1.0 ... ``` Change-Id: I18f9e89a25c184d7fdc38aea01ff5dbee118a974 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.