diff mbox series

[v3] clk: qcom: Elaborate on "active" clocks in the RPM clock bindings

Message ID 20171013112635.32296-1-linus.walleij@linaro.org
State Accepted
Commit 5e70ca8753c8d9749d206a4fdb14f22a6ba1d893
Headers show
Series [v3] clk: qcom: Elaborate on "active" clocks in the RPM clock bindings | expand

Commit Message

Linus Walleij Oct. 13, 2017, 11:26 a.m. UTC
The concept of "active" clocks is just explained in a bried comment in the
device driver, let's explain it a bit more in the device tree bindings
so everyone understands this.

Cc: devicetree@vger.kernel.org
Acked-by: Rob Herring <robh@kernel.org>

Signed-off-by: Linus Walleij <linus.walleij@linaro.org>

---
ChangeLog v2->v3:
- Collect Rob's ACK.
ChangeLog v1->v2:
- Reword slighty in accordance with Stephens feedback.
---
 Documentation/devicetree/bindings/clock/qcom,rpmcc.txt | 8 ++++++++
 1 file changed, 8 insertions(+)

-- 
2.13.5

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Comments

Linus Walleij Oct. 30, 2017, 2:19 p.m. UTC | #1
On Fri, Oct 13, 2017 at 1:26 PM, Linus Walleij <linus.walleij@linaro.org> wrote:

> The concept of "active" clocks is just explained in a bried comment in the

> device driver, let's explain it a bit more in the device tree bindings

> so everyone understands this.

>

> Cc: devicetree@vger.kernel.org

> Acked-by: Rob Herring <robh@kernel.org>

> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>

> ---

> ChangeLog v2->v3:

> - Collect Rob's ACK.

> ChangeLog v1->v2:

> - Reword slighty in accordance with Stephens feedback.


Gentle ping on this patch.

Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Stephen Boyd Nov. 2, 2017, 6:46 a.m. UTC | #2
On 10/13, Linus Walleij wrote:
> The concept of "active" clocks is just explained in a bried comment in the

> device driver, let's explain it a bit more in the device tree bindings

> so everyone understands this.

> 

> Cc: devicetree@vger.kernel.org

> Acked-by: Rob Herring <robh@kernel.org>

> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>

> ---


Applied to clk-next

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
diff mbox series

Patch

diff --git a/Documentation/devicetree/bindings/clock/qcom,rpmcc.txt b/Documentation/devicetree/bindings/clock/qcom,rpmcc.txt
index a7235e9e1c97..32c6e9ce64c3 100644
--- a/Documentation/devicetree/bindings/clock/qcom,rpmcc.txt
+++ b/Documentation/devicetree/bindings/clock/qcom,rpmcc.txt
@@ -16,6 +16,14 @@  Required properties :
 
 - #clock-cells : shall contain 1
 
+The clock enumerators are defined in <dt-bindings/clock/qcom,rpmcc.h>
+and come in pairs: FOO_CLK followed by FOO_A_CLK. The latter clock
+is an "active" clock, which means that the consumer only care that the
+clock is available when the apps CPU subsystem is active, i.e. not
+suspended or in deep idle. If it is important that the clock keeps running
+during system suspend, you need to specify the non-active clock, the one
+not containing *_A_* in the enumerator name.
+
 Example:
 	smd {
 		compatible = "qcom,smd";