| commit | 70301b9c16dc5e3e220472933affb7906b513bf4 | [log] [tgz] |
|---|---|---|
| author | Gunnar Mills <gmills@us.ibm.com> | Mon Jul 17 14:57:36 2023 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Fri Jan 19 10:00:00 2024 -0600 |
| tree | 0807d9a9839684eade6f28b6c4c843c48013c9d7 | |
| parent | 3f8d0197bb897d217c032f98dbb57b5422edf773 [diff] |
Item Associations: Fix capitalization and clarify This capitalization was mixed, move to the exact capitalization of the interfaces. E.g. Cpu from [1]. Made clear it was Led.Group and Connector.Port being associated. [1] https://github.com/openbmc/phosphor-dbus-interfaces/blob/2117deabad40f9ac63815f3338e7ac3e1e3fe397/yaml/xyz/openbmc_project/Inventory/Item/Cpu.interface.yaml Change-Id: I2a4bc4142b5c93335259c98538e0e1754c920bff Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
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.
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.
Only the xyz/openbmc_project and org/freedesktop interfaces are built by default. Other interfaces can be enabled by meson options:
-Ddata_com_ibm=true-Ddata_org_open_power=trueExample: meson builddir -Ddata_com_ibm=true && ninja -C builddir