| commit | 43341f5846e769b760a53ad6502b61e3782523b8 | [log] [tgz] |
|---|---|---|
| author | Andrew Geissler <geissonator@yahoo.com> | Fri Jan 22 14:14:31 2021 -0600 |
| committer | Andrew Geissler <geissonator@yahoo.com> | Wed Feb 24 13:55:53 2021 +0000 |
| tree | a465fb5833438f7a498401cd01fa5400a66fd233 | |
| parent | 66b591e165b53a80e431a543aa8c8e48beba585f [diff] |
transition: support transitioning chassis states The is along the same lines as the host transition state commit: https://github.com/openbmc/phosphor-dbus-interfaces/commit/9f65dfeaa5ab22cae03db45c9916868da9864f83 IBM has found a use case for also knowing when the chassis is in a transition from On to Off or vice versa. Some of our larger systems take a fairly significant amount of time to power on and off their chassis's. Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: Iffec13a3278f37e8ca5ca44bbe2e34970587aa37
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