| commit | 7fd1de390723586dd94bd0b0119f8273d20ff46e | [log] [tgz] |
|---|---|---|
| author | SpencerKu <Spencer.Ku@quantatw.com> | Thu Sep 02 15:57:55 2021 +0800 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Fri Oct 22 21:09:50 2021 +0000 |
| tree | b59f574e3569b8e381b7399580f9136d1e617fde | |
| parent | 7862c230af8b5812d562c86d8fb6e5cab84f8bf7 [diff] |
Add "GenerationInUse" and "GenerationSupported" to PCIeDevice interface Add PCIeDevice properties "GenerationInUse" and "GenerationSupported" then let managerment APIs like redfish can expose the information. New property: GenerationInUse : The PCIe interface generation in use by the device GenerationSupported: The maximum PCIe generation supported by the device Dbus Sample output: NAME TYPE SIGNATURE RESULT/VALUE FLAGS [...] xyz.openbmc_project.PCIe.Device interface - - - .DeviceType property s "SingleFunction" emits-change .Function0ClassCode property s "0x060400" emits-change [...] .GenerationInUse property s "xyz.openbmc_project.Inventory.Item.PCIeSlot.Generations.Gen2" emits-change Signed-off-by: Spencer Ku <Spencer.Ku@quantatw.com> Change-Id: Ie1bf12a703dc85c3670487b146fb62f0dbae9908
YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.
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 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