commit | 11efbb3c856af9d760e2d27ff276090d7b3510d5 | [log] [tgz] |
---|---|---|
author | Chicago Duan <duanzhijia01@inspur.com> | Mon Sep 26 16:36:44 2022 +0800 |
committer | Patrick Williams <patrick@stwcx.xyz> | Fri Oct 07 06:24:52 2022 -0500 |
tree | 2db5c365be9ea45dc69b0f06170aa7017d516c66 | |
parent | e8821cc87221fcb535e436b78c7106ba84164057 [diff] |
PowerSupply, Chassis: add powering association Create association documentation between Chassis and PowerSupply. For a machine with multiple chassis, it is necessary to indicate which chassis a PowerSupply is managed by. One example is that the ChassisID and PowerSupplyID in the Redfish URL need to match, so we can confirm it through this association. Signed-off-by: Chicago Duan <duanzhijia01@inspur.com> Change-Id: I6beb18fd0b621cec6cd4a38606e009cda40f9761 Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
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=true
Example: meson builddir -Ddata_com_ibm=true && ninja -C builddir