common: Add new Priority interface

This commit introduces the new "Priority" interface, which is designed
to indicate the priority level of an entity. It can be used as a
decorator for other objects to specify their priority. While this
interface was initially developed for fan sensors, it can be applied to
various entities and is not limited to fans. This new interface provide
more specific information about the primary and secondary sensors, which
is needed for Redfish Fan schema.

bmcweb commit:
https://gerrit.openbmc.org/c/openbmc/bmcweb/+/57657

Change-Id: Iee875dbe627980139199a6d9a56fde3e5d651af0
Signed-off-by: Lakshmi Yadlapati <lakshmiy@us.ibm.com>
3 files changed
tree: 12b1bcc375ca16907a8a762037e8fddd6268acc9
  1. gen/
  2. subprojects/
  3. yaml/
  4. .gitignore
  5. .markdownlint.yaml
  6. .prettierrc.yaml
  7. .shellcheck
  8. LICENSE
  9. meson.build
  10. meson.options
  11. OWNERS
  12. README.md
  13. requirements.md
README.md

phosphor-dbus-interfaces

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

Before defining a new D-Bus interface or modifying an existing one, please read through the documented set of the common requirements and expectations.

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