Add org/open_power D-Bus interfaces
In an effort to define all of the D-Bus interfaces in one place, this
commit adds the interfaces from the openpower-dbus-interfaces
repository.
To compile these interfaces, use the --enable-openpower-dbus-interfaces
configure flag.
Change-Id: I801cab4ac979e56d8325a42c14319a0b7cd094bb
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
diff --git a/org/open_power/OCC/PassThrough.interface.yaml b/org/open_power/OCC/PassThrough.interface.yaml
new file mode 100644
index 0000000..3fc968c
--- /dev/null
+++ b/org/open_power/OCC/PassThrough.interface.yaml
@@ -0,0 +1,28 @@
+description: >
+ Implement to provide pass-through mechanism to the On Chip Controller (OCC).
+methods:
+ - name: Send
+ description: >
+ Pass through a command to the OCC.
+ parameters:
+ - name: command
+ # TODO via https://github.com/openbmc/openbmc/issues/1160. This should
+ # change to array[byte]. As of now, the REST server maps any numeric
+ # data to int32.
+ type: array[int32]
+ description: >
+ An array of integers representing the command and payload. This
+ should still be bytes worth of data (as though using array[byte]),
+ so each entry in the array should pack as many bytes as possible.
+ returns:
+ - name: response
+ # TODO via https://github.com/openbmc/openbmc/issues/1160. This should
+ # change to array[byte]. As of now, the REST server maps any numeric
+ # data to int32.
+ type: array[int32]
+ description: >
+ An array of integers representing the response. This
+ should still be bytes worth of data (as though using array[byte]),
+ so each entry in the array should pack as many bytes as possible.
+
+# vim: tabstop=8 expandtab shiftwidth=4 softtabstop=4
diff --git a/org/open_power/OCC/Status.interface.yaml b/org/open_power/OCC/Status.interface.yaml
new file mode 100644
index 0000000..ea99fa4
--- /dev/null
+++ b/org/open_power/OCC/Status.interface.yaml
@@ -0,0 +1,23 @@
+description: >
+ Implement to indicate status of the OCC.
+
+properties:
+ - name: OccActive
+ type: boolean
+ description: >
+ Indicates whether OCC is active or not
+ - name: ThrottleProcTemp
+ type: boolean
+ default: 0
+ description: >
+ Indicates processor throttling due to an over temperature condition
+ - name: ThrottleProcPower
+ type: boolean
+ default: 0
+ description: >
+ Indicates processor throttling due to reaching the power cap limit
+ - name: ThrottleMemTemp
+ type: boolean
+ default: 0
+ description: >
+ Indicates memory throttling due to an over temperature condition