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>
7 files changed
tree: 5163e6e9eeb6ab37b249bb3ad62088780bf458ca
  1. gen/
  2. subprojects/
  3. yaml/
  4. .gitignore
  5. .markdownlint.yaml
  6. .prettierrc.yaml
  7. .shellcheck
  8. LICENSE
  9. meson.build
  10. meson.options
  11. OWNERS
  12. README.md
  13. requirements.md
README.md

phosphor-dbus-interfaces

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.

Building

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.

Configuration

Only the xyz/openbmc_project and org/freedesktop interfaces are built by default. Other interfaces can be enabled by meson options:

  • com/ibm - -Ddata_com_ibm=true
  • org/open_power - -Ddata_org_open_power=true

Example: meson builddir -Ddata_com_ibm=true && ninja -C builddir

References