Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-dbus-interfaces / 3a665b28dcc0d9f6926a1f5eb20bc0d9d768418d
commit3a665b28dcc0d9f6926a1f5eb20bc0d9d768418d[log] [tgz]
authorAndrei Kartashev <a.kartashev@yadro.com>Sun Aug 29 00:45:04 2021 +0300
committerPatrick Williams <patrick@stwcx.xyz>Wed Sep 15 15:26:40 2021 +0000
tree8aa60fcbc542a9f7cfcdb48eea90b3e8a5a5ea6a
parent4573e652d37f10b2ae5a1b5b9ea1b79021546180 [diff]
Inventory.Item.Drive: add Protocol property

Protocol property aimed to represent connection protocol used by the
drive. Most common protocols are SATA, SAS, NVMe.

Signed-off-by: Andrei Kartashev <a.kartashev@yadro.com>
Change-Id: I17263f07d324e959f05ba5f3f3993d7d4d55fa52
1 file changed
tree: 8aa60fcbc542a9f7cfcdb48eea90b3e8a5a5ea6a
  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