From: sricharan@codeaurora.org (Sricharan R)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 11/14] dt-bindings: clock: Document qcom,krait-cc
Date: Mon, 13 Aug 2018 19:06:04 +0530 [thread overview]
Message-ID: <1534167367-17545-12-git-send-email-sricharan@codeaurora.org> (raw)
In-Reply-To: <1534167367-17545-1-git-send-email-sricharan@codeaurora.org>
From: Stephen Boyd <sboyd@codeaurora.org>
The Krait clock controller controls the krait CPU and the L2 clocks
consisting a primary mux and secondary mux. Add document for that.
Reviewed-by: Rob Herring <robh@kernel.org>
Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
---
.../devicetree/bindings/clock/qcom,krait-cc.txt | 34 ++++++++++++++++++++++
1 file changed, 34 insertions(+)
create mode 100644 Documentation/devicetree/bindings/clock/qcom,krait-cc.txt
diff --git a/Documentation/devicetree/bindings/clock/qcom,krait-cc.txt b/Documentation/devicetree/bindings/clock/qcom,krait-cc.txt
new file mode 100644
index 0000000..030ba60
--- /dev/null
+++ b/Documentation/devicetree/bindings/clock/qcom,krait-cc.txt
@@ -0,0 +1,34 @@
+Krait Clock Controller
+
+PROPERTIES
+
+- compatible:
+ Usage: required
+ Value type: <string>
+ Definition: must be one of:
+ "qcom,krait-cc-v1"
+ "qcom,krait-cc-v2"
+
+- #clock-cells:
+ Usage: required
+ Value type: <u32>
+ Definition: must be 1
+
+- clocks:
+ Usage: required
+ Value type: <prop-encoded-array>
+ Definition: reference to the clock parents of hfpll, secondary muxes.
+
+- clock-names:
+ Usage: required
+ Value type: <stringlist>
+ Definition: must be "hfpll0", "hfpll1", "acpu0_aux", "acpu1_aux", "qsb".
+
+Example:
+
+ kraitcc: clock-controller {
+ compatible = "qcom,krait-cc-v1";
+ clocks = <&hfpll0>, <&hfpll1>, <&acpu0_aux>, <&acpu1_aux>, <qsb>;
+ clock-names = "hfpll0", "hfpll1", "acpu0_aux", "acpu1_aux", "qsb";
+ #clock-cells = <1>;
+ };
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
next prev parent reply other threads:[~2018-08-13 13:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 13:35 [PATCH V11 00/14] Krait clocks + Krait CPUfreq Sricharan R
2018-08-13 13:35 ` [PATCH 01/14] ARM: Add Krait L2 register accessor functions Sricharan R
2018-08-13 13:35 ` [PATCH 02/14] clk: qcom: Add support for High-Frequency PLLs (HFPLLs) Sricharan R
2018-08-13 13:35 ` [PATCH 03/14] clk: qcom: Add HFPLL driver Sricharan R
2018-08-13 13:35 ` [PATCH 04/14] dt-bindings: clock: Document qcom,hfpll Sricharan R
2018-08-13 13:35 ` [PATCH 05/14] clk: qcom: Add MSM8960/APQ8064's HFPLLs Sricharan R
2018-08-13 13:35 ` [PATCH 06/14] clk: qcom: Add IPQ806X's HFPLLs Sricharan R
2018-08-13 13:36 ` [PATCH 07/14] clk: qcom: Add support for Krait clocks Sricharan R
2018-08-13 13:36 ` [PATCH 08/14] clk: qcom: Add KPSS ACC/GCC driver Sricharan R
2018-08-13 13:36 ` [PATCH 09/14] dt-bindings: arm: Document qcom,kpss-gcc Sricharan R
2018-08-13 13:36 ` [PATCH 10/14] clk: qcom: Add Krait clock controller driver Sricharan R
2018-08-13 13:36 ` Sricharan R [this message]
2018-08-13 13:36 ` [PATCH 12/14] clk: qcom: Add safe switch hook for krait mux clocks Sricharan R
2018-08-13 13:36 ` [PATCH 13/14] cpufreq: qcom: Re-organise kryo cpufreq to use it for other nvmem based qcom socs Sricharan R
2018-08-13 13:36 ` [PATCH 14/14] cpufreq: qcom: Add support for krait based socs Sricharan R
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1534167367-17545-12-git-send-email-sricharan@codeaurora.org \
--to=sricharan@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).