| commit | ab2ce4eaccf518e3fe707e1d5b43db67a6d5e8df | [log] [tgz] |
|---|---|---|
| author | Andrew Geissler <geissonator@yahoo.com> | Thu Oct 28 15:50:57 2021 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Mon Nov 15 17:16:43 2021 +0000 |
| tree | 0e069a936e1a0fcc4cf3d25c7df0f71d754bcc25 | |
| parent | 90116920633cdd49e68508d8009d2fec24237539 [diff] |
host-state: introduce new scheduled power on reason The xyz.openbmc_project.State.ScheduledHostTransition interface is utilized to schedule a host transition at some point in the future. Add this as a potential reason for the host RestartCause property. On IBM systems, the host needs to know when a scheduled transition is the reason for a boot. This property will be utilized by the host communication firmware to tell them. Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I438982223482f9819abaee25bbf5b85ae27392bc
YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.
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 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