| commit | a8f47e7f1dfc43b6b9775bee7ee9e529a21fd7a5 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Tue Jun 11 17:06:04 2024 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Thu Jun 13 22:09:43 2024 +0000 |
| tree | ddfa11818aba7d17337d30b233d22fbbe9106a2b | |
| parent | 8bd711ed214bc06296fb19d71970e7269f47cb56 [diff] |
postcode: add dbus paths
The default path for the post code objects is, from
phosphor-post-code-manager:
```
meson.build
16:conf_data.set_quoted('DBUS_OBJECT_NAME', '/xyz/openbmc_project/State/Boot/PostCode')
src/main.cpp
60: std::string dbusObjName = DBUS_OBJECT_NAME + std::to_string(node);
```
Add these constants to the interface YAML file so they can be used by
dbus clients.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: If255733aaf12cf7283e191c31fe13ba3025736d8
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