blob: 5d24ee15a0ed41f6d8423d3b4ebc42746b322e1f (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
|
power-mgt/powercap
------------------
The powercap sensors are populated in this node. Each child node in
the "powercap" node represents a power-cappable component.
For example : ::
system-powercap/
The OPAL_GET_POWERCAP and OPAL_SET_POWERCAP calls take a handle for
what powercap property to get/set which is defined in the child node.
The compatible property for the linux driver which will be
"ibm,opal-powercap"
Each child node has below properties:
`powercap-current`
Handle to indicate the current powercap
`powercap-min`
Absolute minimum possible powercap. This points to the soft powercap minimum
limit as exported by OCC. The powercap set in the soft powercap range may or
may not be maintained.
`powercap-max`
Maximum possible powercap
`powercap-hard-min`
This value points to the hard minimum powercap limit. The powercap set above
this limit is guaranteed unless there is a hardware failure
Powercap handle uses the following encoding: ::
| Class | Reserved | Attribute |
|-------|---------------|-----------|
Note: The format of the powercap handle is ``NOT`` ABI and may change in
the future.
.. code-block:: dts
power-mgt {
powercap {
compatible = "ibm,opal-powercap";
system-powercap {
name = "system-powercap";
powercap-current = <0x00000002>;
powercap-min = <0x00000000>;
powercap-max = <0x00000001>;
powercap-hard-min = <0x000000003>;
};
};
};
|
