| commit | 8c71ba70a3bc4835cd11952f9bff497ccfb94dd1 | [log] [tgz] |
|---|---|---|
| author | Vijay Lobo <vijaylobo@gmail.com> | Thu Jun 24 23:37:30 2021 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Mon Aug 02 20:08:40 2021 +0000 |
| tree | 0f8f4e5013f085590fd564e3ae853ec82ac37f7b | |
| parent | 0ef46c1e65fb6e88667d468bad88932be481ab54 [diff] |
PEL.Entry: Add Subsystem property Adding subsystem property to support PEL creation. This subsystem property can be used to identify a failing area in the system. These subsystem values can be enums but keeping them as strings can save decoding effort at the far end. The PEL spec has more than 70 unique values and these can be extended as new hardware shows up. Signed-off-by: Vijay Lobo <vijaylobo@gmail.com> Change-Id: I5de076c167f81780c0121c6482d6a6f5b3c63641
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