commit | c531268c53e2676ca82937ef67d1b0475467bc59 | [log] [tgz] |
---|---|---|
author | Matt Spinler <spinler@us.ibm.com> | Mon Mar 21 13:32:05 2022 -0500 |
committer | Matt Spinler <spinler@us.ibm.com> | Tue Apr 05 13:14:12 2022 +0000 |
tree | aeb87f5086ea27217aa0c8e00c5259d5d181ccf2 | |
parent | 3b99c1855fedd937cd2ce46ff0a4c1024847dff3 [diff] |
openpower: Add GetPELJSON method This method returns a PEL in JSON format so it can be returned in Redfish via an OEM attachment. It's a method and not a property on the PEL.Entry interface because it is fairly slow and it would bog down GetManagedObjects calls that don't care about it. Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I6d04cd4e301980f95736c05dd5e5b027d400d49b
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 and org/freedesktop interfaces are built by default. Other interfaces can be enabled by meson options:
-Ddata_com_ibm=true
-Ddata_org_open_power=true
Example: meson builddir -Ddata_com_ibm=true && ninja -C builddir