commit | 9969a5b4016bc8ae62e5f23aad476c6352dfac86 | [log] [tgz] |
---|---|---|
author | Wludzik, Jozef <jozef.wludzik@intel.com> | Wed Feb 03 15:39:37 2021 +0100 |
committer | Patrick Williams <patrick@stwcx.xyz> | Wed Feb 10 12:52:20 2021 +0000 |
tree | 8a5d5f6d1d7eb440d0c217bca33d9f5d34453fce | |
parent | 66119c0e3eadbcdc611c3f374ae83acbd066506e [diff] |
Changed array of sensor to single sensor in Telemetry.Report Changed array of sensor object paths to single object_path in ReadingParameters property in xyz.openbmc_project.Telemetry.Report interface. Same changed has been applied to AddReport method in xyz.openbmc_project.Telemetry.ReportManager interface. After deep dive into details there is no need to support collection of sensor for readings. Operations have to be performed on readings from individual sensor. Signed-off-by: Wludzik, Jozef <jozef.wludzik@intel.com> Change-Id: I602091e59def6e3f5fb48c0a8c6f828edf41527c
YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.
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 interfaces are built by default. Other interfaces can be enabled by meson options:
-Ddata_com_ibm=true
-Ddata_org_open_power=true
Example: meson builddir -Ddata_com_ibm=true && ninja -C builddir