Add ObjectManager path requirement for Voltage Regulator interfaces

Add the requirement/expectation of org.freedesktop.DBus.ObjectManager on
services implementing Control.VoltageRegular{Mode,Control}.

The ObjectManager is expected to be implemented at
/xyz/openbmc_project/vr.

Currently, dbus-sdr specifically calls out the paths it uses to find the
ObjectManager, instead of using "/" which would find any ObjectManager
implemented at any location. "/xyz/openbmc_project/sensors" is listed in
dbus-sdr and in phosphor-dbus-interfaces now. This changes adds
"/xyz/openbmc_project/vr".

Change-Id: I6c74323189b74958301b445d6dc9a993a495e62f
Signed-off-By: Sui Chen <suichen@google.com>
2 files changed
tree: cacea335b7041c67667cd01da9430d99541cce98
  1. gen/
  2. subprojects/
  3. yaml/
  4. .gitignore
  5. .markdownlint.yaml
  6. .prettierrc.yaml
  7. .shellcheck
  8. LICENSE
  9. meson.build
  10. meson_options.txt
  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