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
diff --git a/xyz/openbmc_project/Control/Processor/CurrentOperatingConfig.interface.yaml b/xyz/openbmc_project/Control/Processor/CurrentOperatingConfig.interface.yaml
new file mode 100644
index 0000000..918f9f9
--- /dev/null
+++ b/xyz/openbmc_project/Control/Processor/CurrentOperatingConfig.interface.yaml
@@ -0,0 +1,11 @@
+description: >
+ Processor power and frequency configuration settings.
+properties:
+ - name: AppliedConfig
+ type: object_path
+ description: Path to currently selected configuration.
+ - name: BaseSpeedPriorityEnabled
+ type: boolean
+ description: >
+ Whether base speed prioritization is enabled in the currently selected
+ configuration.