| commit | aab4a6c2af9df2d9f72e6e7c537b95c48c1d3386 | [log] [tgz] |
|---|---|---|
| author | Roger G. Coscojuela <roger.gili-coscojuela@sipearl.com> | Mon Sep 01 09:37:47 2025 +0200 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Mon Sep 08 13:40:53 2025 +0000 |
| tree | 088c6e96d245d6d39b23baf5f0501b47338706d2 | |
| parent | 0e14bf7dc6cb0dee8b2de6b29459e88b012e1829 [diff] |
Value.interface: Fix typo Just a typo fix in the description of volts enum. Change-Id: I9601408aa020e68c9cc26276207dc3879e95edac Signed-off-by: Roger G. Coscojuela <roger.gili-coscojuela@sipearl.com>
YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.
Before defining a new D-Bus interface or modifying an existing one, please read through the documented set of the common requirements and expectations.
This project can be built with meson. The typical meson workflow is: meson builddir && ninja -C builddir.
The meson files used to handle the YAML files are automatically generated and found under the gen subdirectory. When adding or removing YAML files, this must be regenerated. This can be done with the helper script found in the gen subdirectory: cd gen && ./regenerate-meson.
Only the xyz/openbmc_project and org/freedesktop interfaces are built by default. Other interfaces can be enabled by meson options:
-Ddata_com_ibm=true-Ddata_org_open_power=trueExample: meson builddir -Ddata_com_ibm=true && ninja -C builddir