From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Stephen Boyd <swboyd@chromium.org>,
Michael Turquette <mturquette@baylibre.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Taniya Das <quic_tdas@quicinc.com>
Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 2/7] dt-bindings: clock: separate bindings for MSM8916 GCC device
Date: Sat, 18 Jun 2022 07:35:52 +0300 [thread overview]
Message-ID: <cd4eaead-4218-2de0-1929-7c8a2aafaff4@linaro.org> (raw)
In-Reply-To: <4a614c32-35c5-2dfa-3e15-d54c3c3c5836@linaro.org>
On 18/06/2022 04:40, Krzysztof Kozlowski wrote:
> On 17/06/2022 07:47, Dmitry Baryshkov wrote:
>> Separate bindings for GCC on Qualcomm MSM8916 platforms. This adds new
>> clocks/clock-names properties to be used for clock links.
>>
>> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
>> ---
>> .../bindings/clock/qcom,gcc-msm8916.yaml | 61 +++++++++++++++++++
>> .../bindings/clock/qcom,gcc-other.yaml | 1 -
>> 2 files changed, 61 insertions(+), 1 deletion(-)
>> create mode 100644 Documentation/devicetree/bindings/clock/qcom,gcc-msm8916.yaml
>>
>> diff --git a/Documentation/devicetree/bindings/clock/qcom,gcc-msm8916.yaml b/Documentation/devicetree/bindings/clock/qcom,gcc-msm8916.yaml
>> new file mode 100644
>> index 000000000000..564aa764b17b
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/clock/qcom,gcc-msm8916.yaml
>> @@ -0,0 +1,61 @@
>> +# SPDX-License-Identifier: GPL-2.0-only
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/clock/qcom,gcc-msm8916.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Qualcomm Global Clock & Reset Controller Binding for MSM8916
>> +
>> +maintainers:
>> + - Stephen Boyd <sboyd@kernel.org>
>> + - Taniya Das <quic_tdas@quicinc.com>
>> +
>> +description: |
>> + Qualcomm global clock control module which supports the clocks, resets and
>> + power domains on MSM8916.
>> +
>> + See also:
>> + - dt-bindings/clock/qcom,gcc-msm8916.h
>> +
>> +properties:
>> + compatible:
>> + const: qcom,gcc-msm8916
>> +
>> + clocks:
>> + items:
>> + - description: XO source
>> + - description: Sleep clock source
>> + - description: DSI phy instance 0 dsi clock
>> + - description: DSI phy instance 0 byte clock
>> + - description: External MCLK clock
>> + - description: External Primary I2S clock
>> + - description: External Secondary I2S clock
>> +
>> + clock-names:
>> + items:
>> + - const: xo
>> + - const: sleep_clk
>
> Just "sleep"
I was hesitating here as all other gcc drivers use 'sleep_clk'.
--
With best wishes
Dmitry
next prev parent reply other threads:[~2022-06-18 4:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 14:47 [PATCH 0/7] clk: qcom: gcc-msm8916: modernize the driver Dmitry Baryshkov
2022-06-17 14:47 ` [PATCH 1/7] dt-bindings: clk: qcom,gcc-*: use qcom,gcc.yaml Dmitry Baryshkov
2022-06-18 1:36 ` Krzysztof Kozlowski
2022-06-17 14:47 ` [PATCH 2/7] dt-bindings: clock: separate bindings for MSM8916 GCC device Dmitry Baryshkov
2022-06-18 1:40 ` Krzysztof Kozlowski
2022-06-18 4:35 ` Dmitry Baryshkov [this message]
2022-06-19 12:02 ` Krzysztof Kozlowski
2022-06-19 12:02 ` Krzysztof Kozlowski
2022-06-17 14:47 ` [PATCH 3/7] clk: qcom: gcc-msm8916: use ARRAY_SIZE instead of specifying num_parents Dmitry Baryshkov
2022-06-17 14:47 ` [PATCH 4/7] clk: qcom: gcc-msm8916: move clock parent tables down Dmitry Baryshkov
2022-06-17 14:47 ` [PATCH 5/7] clk: qcom: gcc-msm8916: move gcc_mss_q6_bimc_axi_clk down Dmitry Baryshkov
2022-06-17 14:47 ` [PATCH 6/7] clk: qcom: gcc-msm8916: use parent_hws/_data instead of parent_names Dmitry Baryshkov
2022-06-17 14:47 ` [PATCH 7/7] arm64: dts: qcom: msm8916: add clocks to the GCC device node Dmitry Baryshkov
2022-06-17 17:14 ` Stephan Gerhold
2022-06-17 20:34 ` Dmitry Baryshkov
2022-06-18 13:02 ` Stephan Gerhold
2022-06-18 13:10 ` Dmitry Baryshkov
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=cd4eaead-4218-2de0-1929-7c8a2aafaff4@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=quic_tdas@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=swboyd@chromium.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