| commit | d993b640fa26d42389dee3a784cd7474068b5873 | [log] [tgz] |
|---|---|---|
| author | Sunny Srivastava <sunnsr25@in.ibm.com> | Wed May 11 09:46:30 2022 -0500 |
| committer | Sunny Srivastava <sunnsr25@in.ibm.com> | Tue Mar 12 09:40:17 2024 -0500 |
| tree | 13043fe4d998a1be4832238f9754c437c4cb2259 | |
| parent | 4206b1ac6fde78bcbaca6fc766af8a4dc34c6b0d [diff] |
Default value for LanesInUse set to MAXINT Changing the default value for property "LanesInUse" to accommodate situations where the reason behind failure to get the value is not known. Some of the reason behind could be hardware failure or the link is down or power to the I/O slot may be off. Signed-off-by: Sunny Srivastava <sunnsr25@in.ibm.com> Change-Id: If3bccd89382934f4bcf7ccf16f8068153d113d2c
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