From: Jeffrey Hugo <jhugo@codeaurora.org>
To: Stephen Boyd <sboyd@kernel.org>, mturquette@baylibre.com
Cc: agross@kernel.org, bjorn.andersson@linaro.org,
marc.w.gonzalez@free.fr, robh+dt@kernel.org,
mark.rutland@arm.com, linux-arm-msm@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v6 1/6] dt-bindings: clock: Document external clocks for MSM8998 gcc
Date: Thu, 7 Nov 2019 15:21:42 -0700 [thread overview]
Message-ID: <bc3d173d-6b87-29d1-475d-e569dec826b2@codeaurora.org> (raw)
In-Reply-To: <20191107214730.781622084C@mail.kernel.org>
On 11/7/2019 2:47 PM, Stephen Boyd wrote:
> Quoting Jeffrey Hugo (2019-10-01 12:55:18)
>> The global clock controller on MSM8998 can consume a number of external
>> clocks. Document them.
>>
>> Signed-off-by: Jeffrey Hugo <jhugo@codeaurora.org>
>> Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
>> Reviewed-by: Rob Herring <robh@kernel.org>
>> ---
>> Documentation/devicetree/bindings/clock/qcom,gcc.txt | 10 ++++++++++
>> 1 file changed, 10 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/clock/qcom,gcc.txt b/Documentation/devicetree/bindings/clock/qcom,gcc.txt
>> index d14362ad4132..32d430718016 100644
>> --- a/Documentation/devicetree/bindings/clock/qcom,gcc.txt
>> +++ b/Documentation/devicetree/bindings/clock/qcom,gcc.txt
>> @@ -29,6 +29,16 @@ Required properties :
>> - #clock-cells : shall contain 1
>> - #reset-cells : shall contain 1
>>
>> +For MSM8998 only:
>> + - clocks: a list of phandles and clock-specifier pairs,
>> + one for each entry in clock-names.
>> + - clock-names: "xo" (required)
>> + "usb3_pipe" (optional)
>> + "ufs_rx_symbol0" (optional)
>> + "ufs_rx_symbol1" (optional)
>> + "ufs_tx_symbol0" (optional)
>> + "pcie0_pipe" (optional)
>
> This got wrecked by Taniya's changes to this file. Can you resend and
> rebase it? Sorry for the troubles.
>
I was afraid of that. I will rewrite and resend.
--
Jeffrey Hugo
Qualcomm Technologies, Inc. is a member of the
Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2019-11-07 22:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 19:54 [PATCH v6 0/6] MSM8998 Multimedia Clock Controller Jeffrey Hugo
2019-10-01 19:55 ` [PATCH v6 1/6] dt-bindings: clock: Document external clocks for MSM8998 gcc Jeffrey Hugo
2019-11-07 21:47 ` Stephen Boyd
2019-11-07 22:21 ` Jeffrey Hugo [this message]
2019-10-01 19:56 ` [PATCH v6 2/6] arm64: dts: msm8998: Add xo clock to gcc node Jeffrey Hugo
2019-10-01 19:57 ` [PATCH v6 3/6] clk: qcom: smd: Add XO clock for MSM8998 Jeffrey Hugo
2019-11-07 21:50 ` Stephen Boyd
2019-10-01 19:57 ` [PATCH v6 4/6] dt-bindings: clock: Add support for the MSM8998 mmcc Jeffrey Hugo
2019-11-07 21:55 ` Stephen Boyd
2019-11-07 22:35 ` Jeffrey Hugo
2019-11-08 6:42 ` Stephen Boyd
2019-10-01 19:57 ` [PATCH v6 5/6] clk: qcom: Add MSM8998 Multimedia Clock Controller (MMCC) driver Jeffrey Hugo
2019-10-01 19:58 ` [PATCH v6 6/6] arm64: dts: qcom: msm8998: Add mmcc node Jeffrey Hugo
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=bc3d173d-6b87-29d1-475d-e569dec826b2@codeaurora.org \
--to=jhugo@codeaurora.org \
--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=linux-kernel@vger.kernel.org \
--cc=marc.w.gonzalez@free.fr \
--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).