| commit | ec9fc42563bd5c68193e58ef0f533c0952e86ed7 | [log] [tgz] |
|---|---|---|
| author | Andrew Geissler <geissonator@yahoo.com> | Mon Apr 19 16:29:13 2021 -0500 |
| committer | Andrew Geissler <geissonator@yahoo.com> | Wed Apr 28 11:30:00 2021 -0500 |
| tree | bdf2737fff3c4dac83f1d6fa72f6452e8a7f5452 | |
| parent | a9942a456555e99cc4aa3b68bea024f3c4c38dbc [diff] |
host: define new interface for checking condition With the introduction of the PLDM protocol as a mechanism to communicate with the host firmware, a more specific mechanism is needed for BMC software to check if the host is running. Utilizing the generic Execute() method is confusing, especially considering that all of the Command types may not be supported by all protocols. The plan is to deprecate the Control.Host, Execute() with the HeartBeat command type, in place of this new interface and property. Both IPMI and PLDM will implement this method and BMC software can query mapper for implementers on their specific systems. Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I102b07a0c795e6af3be48fedee9a31ae816dba11
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