Add DT documentation to add an idle state as a cooling device. The CPU is actually the cooling device but the definition is already used by frequency capping. As we need to make cpufreq capping and idle injection to co-exist together on the system in order to mitigate at different trip points, the CPU can not be used as the cooling device for idle injection. The idle state can be seen as an hardware feature and therefore as a component for the passive mitigation. Signed-off-by: Daniel Lezcano <daniel.lezcano@xxxxxxxxxx> --- Documentation/devicetree/bindings/arm/idle-states.txt | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/Documentation/devicetree/bindings/arm/idle-states.txt b/Documentation/devicetree/bindings/arm/idle-states.txt index 771f5d20ae18..702a19b6b0b2 100644 --- a/Documentation/devicetree/bindings/arm/idle-states.txt +++ b/Documentation/devicetree/bindings/arm/idle-states.txt @@ -346,6 +346,17 @@ follows: idle-states node. Please refer to the entry-method bindings documentation for properties definitions. + When the idle state is used as a cooling device, the #cooling-cells + must be added in order to allow registering it. + + - #cooling-cells: + Usage: Optional + Type: unsigned + Size: one cell + Definition: A cooling device specific information. At least + must be two. Refer to the thermal DT bindings for + more details. + =========================================== 4 - Examples =========================================== -- 2.17.1
