| commit | 1d4979c7e3996a4ab80915f320536cc9e78f41e8 | [log] [tgz] |
|---|---|---|
| author | Jonathan Doman <jonathan.doman@intel.com> | Thu Sep 10 16:32:04 2020 -0700 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Fri Oct 16 20:33:06 2020 +0000 |
| tree | 8ae55cbccb22918249801a91edfdfe3033788320 | |
| parent | 0ab181d32e31713d5fd429bd62dd883df84e0d74 [diff] |
Add OperatingConfig interfaces
In order to advertise Intel Speed Select capabilities through the
Redfish OperatingConfig resources (schema 2020.2), define D-Bus
interfaces so that the Redfish server can get properties from the
application which does the Speed Select discovery.
Speed Select provides a set of processor-specific power and frequency
profiles. Currently, the only known use case of this interface is for a
Redfish client to view the profile attributes and select a profile.
Hence, the interface resembles the Redfish schema.
The intended intitial use case is that for supported CPUs,
CurrentOperatingConfig will be implemented on cpu objects (under
inventory/ tree), and child objects under each cpu will implement
OperatingConfig. For example:
|-/xyz/openbmc_project/inventory/system/chassis/motherboard/cpu0
| =xyz.openbmc_project.Control.Processor.CurrentOperatingConfig
|
|-/xyz/openbmc_project/inventory/system/chassis/motherboard/cpu0/config0
| =xyz.openbmc_project.Inventory.Item.Cpu.OperatingConfig
|
|-/xyz/openbmc_project/inventory/system/chassis/motherboard/cpu0/config3
=xyz.openbmc_project.Inventory.Item.Cpu.OperatingConfig
Signed-off-by: Jonathan Doman <jonathan.doman@intel.com>
Change-Id: I1663729c274aeaa5c3e78388690e9c6dd4aa3570
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 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