| commit | 3f8d0197bb897d217c032f98dbb57b5422edf773 | [log] [tgz] |
|---|---|---|
| author | Gunnar Mills <gmills@us.ibm.com> | Mon Jul 17 14:41:39 2023 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Fri Jan 19 09:59:41 2024 -0600 |
| tree | 4c092589a859d9cb9fed7337ead8b43060d2141e | |
| parent | 8daf5ff7dddfec4d8435456a99aaf5e3c34a4437 [diff] |
Cpu/PCIeSlot: Add {connecting, connected_to}
https://gerrit.openbmc.org/c/openbmc/phosphor-dbus-interfaces/+/64951
removes the current associated_pcie_slots, upstream_processor
association.
This commit adds that association back but with an existing association.
Redfish is adding this link to the PCIeDevice so will have to do
something like Cpu -> Connected_to -> PCIeSlot -> Containing ->
PCIeDevice to fill this out in bmcweb. If instead we put this on
PCIeDevice wouldn't be able to have this link for empty PCIeSlots.
[1] was the original commit for Cpu, PCIeDevice association.
https://gerrit.openbmc.org/c/openbmc/bmcweb/+/61509 is the commit adding
this Link to Redfish, it should be refreshed with this newly named
association.
Redfish describes this as "An array of links to the processors that are
directly connected or directly bridged to this PCIe slot."
Took descriptions from [2].
[1] https://github.com/openbmc/phosphor-dbus-interfaces/commit/df55704398ec8fc3cc608206f05a2226f134c786
[2] https://github.com/openbmc/phosphor-dbus-interfaces/commit/df32eb57476e86044a996c5f2b6765a772c10de4
Change-Id: I7a5be817b565de035e6166b07743f0ec8e919950
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