common.Threshold: use dict-of-dict for Value

The Dbus specification does not allow the key of a dict to be a
non-basic type, such as a struct:

    the first single complete type (the "key") must be a basic type
    rather than a container type.

If we try to instantiate an instance with a struct as a dict key, we
end up getting an EINVAL on the add-vtable call.

Switch to nested dictionary to avoid this violation.

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I2c512984e62166efec3f299d55efb39a9e93edbf
1 file changed
tree: 23aafe09455f2aa7d6d64904bd119637df1c3846
  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