Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-dbus-interfaces / e96b86b7c938439e9076fa2c99642de1042d1fb3
commite96b86b7c938439e9076fa2c99642de1042d1fb3[log] [tgz]
authorBrandon Kim <brandonkim@google.com>Fri Sep 24 11:13:31 2021 -0700
committerBrandon Kim <brandonkim@google.com>Fri Sep 24 12:10:23 2021 -0700
tree993fe06b6ee59b6d9fb574218bd5691d5cbe032f
parent3a665b28dcc0d9f6926a1f5eb20bc0d9d768418d [diff]
Add Microcode property to CpuCore Interface

"Core" is one of the "ProcessorType" under the Processor Redfish Schema.
https://redfish.dmtf.org/schemas/v1/Processor.v1_12_0.json

Microcode is often exposed at the core level, expose it to CpuCore.

Signed-off-by: Brandon Kim <brandonkim@google.com>
Change-Id: Id7e3f66431883b5f25322e3f055c0c6ab84b8ece
1 file changed
tree: 993fe06b6ee59b6d9fb574218bd5691d5cbe032f
  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