| commit | 522846cf10edf2bee60aa6867594db1efd8cd585 | [log] [tgz] |
|---|---|---|
| author | Michal Orzel <michalx.orzel@intel.com> | Thu Aug 08 14:43:01 2024 +0200 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Tue Aug 20 10:09:58 2024 +0000 |
| tree | 970eb7b07dbc67f374e3666b5a7712b6d37c3294 | |
| parent | 2fa322280d730a5ef123c8fe749b90ded90cd293 [diff] |
telemetry: Unify reading parameter property names Changes name of "MetricParams" argument of ReportManager.AddReport method to "ReadingParameters", which is its equivalent from Report interface. This helps avoid possible confusion, whether those parameters should refer to the same thing or not. Change-Id: I18e504462fb379e5267cee2c4102cf61e2b157a8 Signed-off-by: Michal Orzel <michalx.orzel@intel.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