| commit | 95552670fb232d565cf25e0191f492133c8692f6 | [log] [tgz] |
|---|---|---|
| author | Aditya Kurdunkar <akurdunkar@nvidia.com> | Thu Aug 21 01:08:17 2025 +0530 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Thu Sep 04 16:29:35 2025 +0000 |
| tree | 49baf813b32d77d2684e055f3892cbbf926a0f2b | |
| parent | 3ea5c2f28f576068b7e0135507ad809bdeb1cd9b [diff] |
Sensors: Add Frequency namespace This patch adds the frequency namespace. Change-Id: Id8d1d8ec2e410561785b31f9e1b378a1b18ab6d4 Signed-off-by: Aditya Kurdunkar <akurdunkar@nvidia.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