| commit | 63190140769816aef577830e24c668445406096f | [log] [tgz] |
|---|---|---|
| author | DelphineCCChiu <Delphine_CC_Chiu@wiwynn.com> | Tue Nov 08 10:23:40 2022 +0800 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Wed Nov 09 21:44:05 2022 +0000 |
| tree | 659de945b7453d23d4048e13031a7ffb0d880001 | |
| parent | 36b527af49cf87d0bc7097ea6faba4904fbf8878 [diff] |
Add PowerCycleError parameter in Chassis Error yaml A new system is being designed which will utilize phosphor-state-manager and it requires the chassis system power cycle feature. When chassis power cycle target failed to complete, it need a parameter to represent chassis system power error status. Test plan: Build success and check the chassis system power parameter in configuration. Change-Id: I0de438b63f6221ec4fbffcdc070a65a48a2dafde Signed-off-by: Bonnie Lo <Bonnie_Lo@wiwynn.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