From: kholk11@gmail.com
To: linux-arm-msm@vger.kernel.org
Cc: linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
mark.rutland@arm.com, robh+dt@kernel.org, sboyd@kernel.org,
mturquette@baylibre.com, agross@kernel.org,
bjorn.andersson@linaro.org, marijns95@gmail.com,
AngeloGioacchino Del Regno <kholk11@gmail.com>
Subject: [PATCH v2 2/2] dt-bindings: clock: Document MSM8976 gcc compatible
Date: Tue, 15 Oct 2019 12:32:21 +0200 [thread overview]
Message-ID: <20191015103221.51345-3-kholk11@gmail.com> (raw)
In-Reply-To: <20191015103221.51345-1-kholk11@gmail.com>
From: AngeloGioacchino Del Regno <kholk11@gmail.com>
Document the Global Clock Controller driver (gcc-msm8976)
compatible string.
This driver is valid for MSM8976, MSM8956 and APQ variants.
Signed-off-by: AngeloGioacchino Del Regno <kholk11@gmail.com>
---
Documentation/devicetree/bindings/clock/qcom,gcc.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/clock/qcom,gcc.txt b/Documentation/devicetree/bindings/clock/qcom,gcc.txt
index d14362ad4132..565bba5df298 100644
--- a/Documentation/devicetree/bindings/clock/qcom,gcc.txt
+++ b/Documentation/devicetree/bindings/clock/qcom,gcc.txt
@@ -15,6 +15,7 @@ Required properties :
"qcom,gcc-msm8974"
"qcom,gcc-msm8974pro"
"qcom,gcc-msm8974pro-ac"
+ "qcom,gcc-msm8976"
"qcom,gcc-msm8994"
"qcom,gcc-msm8996"
"qcom,gcc-msm8998"
--
2.21.0
next prev parent reply other threads:[~2019-10-15 10:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 10:32 [PATCH v2 0/2] Global Clock Controller driver for MSM8976/56 kholk11
2019-10-15 10:32 ` kholk11 [this message]
2019-10-17 19:05 ` [PATCH v2 2/2] dt-bindings: clock: Document MSM8976 gcc compatible Rob Herring
2019-12-24 14:17 ` Vladimir Oltean
[not found] ` <20191015103221.51345-2-kholk11@gmail.com>
2019-12-26 22:25 ` [PATCH v2 1/2] clk: qcom: Add MSM8976/56 Global Clock Controller (GCC) driver Stephen Boyd
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=20191015103221.51345-3-kholk11@gmail.com \
--to=kholk11@gmail.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=marijns95@gmail.com \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.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).