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
1 file changed
tree: aeb87f5086ea27217aa0c8e00c5259d5d181ccf2
  1. gen/
  2. subprojects/
  3. yaml/
  4. .editorconfig
  5. .gitignore
  6. .markdownlint.yaml
  7. .prettierrc.yaml
  8. .shellcheck
  9. LICENSE
  10. MAINTAINERS
  11. meson.build
  12. meson_options.txt
  13. OWNERS
  14. README.md
README.md

phosphor-dbus-interfaces

YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.

Building

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.

Configuration

Only the xyz/openbmc_project and org/freedesktop interfaces are built by default. Other interfaces can be enabled by meson options:

  • com/ibm - -Ddata_com_ibm=true
  • org/open_power - -Ddata_org_open_power=true

Example: meson builddir -Ddata_com_ibm=true && ninja -C builddir

References