Ed Tanous | f7b0e07 | 2020-11-05 08:34:43 -0800 | [diff] [blame] | 1 | description: > |
| 2 | Implement to provide control of voltage regulator devices from dbus |
| 3 | Control.VoltageRegulatorProfile.Supported is read only. Implementation of |
| 4 | the Supported property populates the list of supported modes. In the case |
| 5 | where the VR has a well defined default, implementations should place the |
| 6 | default in index 0. |
| 7 | Control.VoltageRegulatorProfile.Current is read/write and sets the |
| 8 | implementation specific mode for the voltage regulator to run in. The |
| 9 | definitions of said enum are implementation defined, as systems likely will |
| 10 | have a multitude of possible states. Some examples of naming might be |
| 11 | "HighPower" or "LowPower" in the case of bipolar power states, or might be |
| 12 | something more complex like, "Profile 1", "Profile 2", "Profile 3" if the VR |
| 13 | itself defines the interfaces. |
| 14 | Implementations may implement this alongside to a VoltageRegulatorControl |
| 15 | interface, and may react to the results of changes to the Control interface. |
| 16 | |
| 17 | properties: |
| 18 | - name: Supported |
| 19 | type: array[string] |
| 20 | flags: |
| 21 | - readonly |
| 22 | description: > |
| 23 | An implementation specific list of supported modes that the voltage |
| 24 | regulator control application can be configured to provide for a |
| 25 | platform. |
| 26 | - name: Selected |
| 27 | type: string |
| 28 | default: "Default" |
| 29 | description: > |
| 30 | The current mode the voltage regulator control application should |
| 31 | use. This can be read to verify the current mode, or written to |
| 32 | change to a new mode. |