| commit | 48d2db99c7b810d4842aa4dff282101397778927 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Thu Mar 20 19:38:36 2025 -0400 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Sat May 31 10:03:00 2025 +0000 |
| tree | 09dea0969451a89024d9d337ff87be00231124c9 | |
| parent | 9ca8d347eddb12250a17ddbdff9e52de92f8d7e9 [diff] |
State.BMC: add event for RebootCause When the BMC comes out of reset, some chips provide a reason / cause of the last reboot. This is already saved in the BMC interface. Define an event which can also be used to record this. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I8fde0e341261a5d7a20af3c1a9f672dfe3b103a9
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