| commit | 51fabad69b459b3826d5c8b3807068b596725013 | [log] [tgz] |
|---|---|---|
| author | Manikandan Elumalai <manikandan.hcl.ers.epl@gmail.com> | Wed Nov 18 16:01:38 2020 +0530 |
| committer | Naveen Moses <naveen.mosess@hcl.com> | Thu Oct 07 19:02:02 2021 +0530 |
| tree | d0d46f54e312e7415f94df5d83a6004e31da096c | |
| parent | 7f832232325ec1b0fc7324764aa1491a7807d36c [diff] |
Add Host selector yaml configuration Host selector interface is used to keep the position of the host selector HW switch as a property. This host selector position value decides which host or bmc is currently selected in a multihost bmc system so that the power and reset button events are routed to the currently selected host or bmc's power control events. Tested: It's tested in Facebook multi-host Yosemitev2 system, including in the Front panel with its selector button. Signed-off-by: Manikandan Elumalai <manikandan.hcl.ers.epl@gmail.com> Change-Id: I18b4bd779c467d7ddc5045c5380d93c1b8a73b74
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