| commit | 412a5182efebacfd060650d7fd16e7c0dc6161b8 | [log] [tgz] |
|---|---|---|
| author | Jagpal Singh Gill <paligill@gmail.com> | Tue Jun 17 15:11:18 2025 -0700 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Wed Sep 24 20:13:32 2025 +0000 |
| tree | 90855e35b99ff93cc5b3a24cfa8a60336efaa54b | |
| parent | 58044a2d10d949cbab3fd0ee71bc5c5e231bef25 [diff] |
add configuration interface for ModbusRTUDetect Add the configuration interface for ModbusRTUDetect which exposes modbus configuration for discovering Modbus devices. This is based on EM Schema [1]. [1]: https://gerrit.openbmc.org/c/openbmc/entity-manager/+/77223 Change-Id: I3ab6d9bd102df3be0c400ea1e5291e5af0382fbd 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