| commit | 199c6c3dd27df14c9884086c025c767ff2efc3b1 | [log] [tgz] |
|---|---|---|
| author | Jagpal Singh Gill <paligill@gmail.com> | Fri Sep 06 09:41:02 2024 -0700 |
| committer | Jagpal Singh Gill <paligill@gmail.com> | Fri Nov 22 10:10:08 2024 -0800 |
| tree | 90feadc050d2a43637fe4d1b4e94ba77aaee4767 | |
| parent | 9d01e5ea679050cec1e38d5349ff5e63e39b35eb [diff] |
add cable connected & not-connected event Add the event to be generated when an expected cable is connected and not connected to a specific port. Change-Id: I9991372c53a25e4480d1944cd91006ec8850fc33 Signed-off-by: Jagpal Singh Gill <paligill@gmail.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