Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-dbus-interfaces / e7f718fc49e86ff9b2b363b2bfa048df1ca054f7
commite7f718fc49e86ff9b2b363b2bfa048df1ca054f7[log] [tgz]
authorRamesh Iyyar <rameshi1@in.ibm.com>Thu Jun 24 04:18:40 2021 -0500
committerPatrick Williams <patrick@stwcx.xyz>Tue Jul 06 18:30:55 2021 +0000
tree96c04a81c9a227a9552ea628f5df5921dc12c96d
parent531c90e34497bbc571c18c50fe078c0d86e61d91 [diff]
open_power: PEL: Added the GetPELIdFromBMCLogId method

In OpenPOWER based system, the application may need to get
the PEL id (aka Entry ID (EID) which is a unique id in the PEL)
by using BMC event log id so added the interface for the same.

Signed-off-by: Ramesh Iyyar <rameshi1@in.ibm.com>
Change-Id: I014fc885c9951af97a79957554e1aaa876f280c1
1 file changed
tree: 96c04a81c9a227a9552ea628f5df5921dc12c96d
  1. gen/
  2. subprojects/
  3. yaml/
  4. .gitignore
  5. .shellcheck
  6. LICENSE
  7. MAINTAINERS
  8. meson.build
  9. meson_options.txt
  10. 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 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