| commit | 0cd3adbafa0ca712645b5c01722ff4c7a49fea6f | [log] [tgz] |
|---|---|---|
| author | Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com> | Fri Apr 26 02:34:41 2024 -0500 |
| committer | Dhruvaraj S <dhruvaraj@gmail.com> | Thu May 16 14:16:40 2024 +0000 |
| tree | 4bd0be1ae6dedf49ef4508e0a9f05a7d60d07fbb | |
| parent | b77f80647113037e831d5aa488ed333d508ae0b6 [diff] |
com.ibm: Add additional properties to hardware dump This commit introduces two new properties to the Hardware dump D-Bus interface: - ErrorLogId: References the log entry that triggered the dump. - FailingUnitId: Identifies the failing hardware unit causing the dump. These additions help in associating dumps with specific error logs and identifying the hardware unit involved in failures. Change-Id: Ied6899327cfee3c5fa4381c24ccfcba68ffc1a8c Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.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