| commit | 16586b5a8d0e601452b8806e4c4a1353ad68c13f | [log] [tgz] |
|---|---|---|
| author | Alexander Hansen <alexander.hansen@9elements.com> | Fri Jul 18 10:19:17 2025 +0200 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Tue Aug 12 11:59:22 2025 +0000 |
| tree | ed58f10b209711313c007d37b9a23ae462a6c396 | |
| parent | cfc8707515c42a25fec386127e374163d3c9ffe7 [diff] |
fix description for Sensor.Value interface Since [1] was merged, the 'Value' property may be written to in some situations. Update the documentation for this interface. References: [1] https://gerrit.openbmc.org/c/openbmc/phosphor-dbus-interfaces/+/36333 Change-Id: I534267bb3068c658929b48ca25ff0bb2e646e4f7 Signed-off-by: Alexander Hansen <alexander.hansen@9elements.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