| commit | 262b9220e59434f8031d9dc24e481b28f420c73a | [log] [tgz] |
|---|---|---|
| author | Harvey Wu <Harvey.Wu@quantatw.com> | Wed Jan 04 10:35:41 2023 +0800 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Tue Sep 19 17:26:47 2023 +0000 |
| tree | 5163e6e9eeb6ab37b249bb3ad62088780bf458ca | |
| parent | 8e360784fc4edcc4de5b4b0f1fce5ffa7bf327fb [diff] |
Add new interface Debug.Pid.Thermal/Power
- According to the issue#27, adding new interface to record the driver
sensor name, driver sensor value and PID loop result to dbus.
interface:
Debug.Pid.ThermalPower => Record the sensor name and reading with the
highest temperature or power in the input
list. And record the result of pid loop
Debug.Pid.Zone => Record the pid config name that that is driving the
fans
refs:
https://github.com/openbmc/phosphor-pid-control/issues/27
Change-Id: I67051616958e07c148eabee658165082855c674d
Signed-off-by: Harvey Wu <Harvey.Wu@quantatw.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