| commit | 9d46e5bb0fcad6c4a775dcef781c0ce4b9de1ff5 | [log] [tgz] |
|---|---|---|
| author | Michal Orzel <michalx.orzel@intel.com> | Wed Oct 02 16:08:37 2024 +0200 |
| committer | Michal Orzel <michalx.orzel@intel.com> | Fri Oct 04 06:08:59 2024 +0000 |
| tree | 8d5c0a1c820746b47731f224155bec19104ed1bc | |
| parent | 90cfce16584253a5f524c718ce5a6ae7c33f7b8c [diff] |
Telemetry: Update Report interface Updating Report interface to the state that is currently implemented in service code: - added `SetReadingProperties` method, which allows safe modification of `ReportingType` and `Interval` properties - made `ReportingType` and `Interval` properties read-only Change-Id: I9a9539a3f9a95b6a1eb19134a264f9438605a66d 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