| commit | 0020fa3da6a30f7f63afb0d2de41b508b7a8f18d | [log] [tgz] |
|---|---|---|
| author | Brandon Wyman <bjwyman@gmail.com> | Thu May 05 18:46:58 2022 +0000 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Fri Aug 05 20:51:48 2022 +0000 |
| tree | a389a08c856e8887a43935acfc5e5ebc4bc59fb9 | |
| parent | 0c3f700ab84e21003bd784c70f89bec55f0207e7 [diff] |
sensor: Add new Accuracy interface
This will express the +/- percentage accuracy of the Value read. Default
to NaN (not a number).
Tested:
Local CI build against phosphor-dbus-interfaces clean.
Built p10bmc obmc-phosphor-image (devtool modify ...)
Find and view client.hpp and server.hpp for Accuracy, looks good.
Change-Id: I42b93c0267cf6ce397c922a0c161c41a56c8b30e
Signed-off-by: Brandon Wyman <bjwyman@gmail.com>
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 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