From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Andy Gross <agross@kernel.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>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 4/4] ARM: dts: qcom: msm8660: add pxo/cxo clocks to the GCC node
Date: Thu, 14 Jul 2022 10:41:02 +0300 [thread overview]
Message-ID: <50ce334b-4c13-1eb3-0e6e-96c9ccee7e1d@linaro.org> (raw)
In-Reply-To: <Ys85KUGnlXlUI+zE@builder.lan>
On 14/07/2022 00:29, Bjorn Andersson wrote:
> On Mon 20 Jun 06:07 CDT 2022, Dmitry Baryshkov wrote:
>
>> Add pxo/cxo clocks to the GCC device tree node.
>>
>> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
>> ---
>> arch/arm/boot/dts/qcom-msm8660.dtsi | 6 ++++--
>> 1 file changed, 4 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/arm/boot/dts/qcom-msm8660.dtsi b/arch/arm/boot/dts/qcom-msm8660.dtsi
>> index 47b97daecef1..61e3ab0ebfd3 100644
>> --- a/arch/arm/boot/dts/qcom-msm8660.dtsi
>> +++ b/arch/arm/boot/dts/qcom-msm8660.dtsi
>> @@ -50,13 +50,13 @@ cpu-pmu {
>> };
>>
>> clocks {
>> - cxo_board {
>> + cxo_board: cxo_board {
>
> As requested by Krzysztof, please use clock-output-names to specify the
> name of the clock, and rename the node "cxo-board-clk".
Actually I believe Krzysztof agreed (and acked) this change, as it
follows the example of existing boards.
>
> Thanks,
> Bjorn
>
>> compatible = "fixed-clock";
>> #clock-cells = <0>;
>> clock-frequency = <19200000>;
>> };
>>
>> - pxo_board {
>> + pxo_board: pxo_board {
>> compatible = "fixed-clock";
>> #clock-cells = <0>;
>> clock-frequency = <27000000>;
>> @@ -129,6 +129,8 @@ gcc: clock-controller@900000 {
>> #power-domain-cells = <1>;
>> #reset-cells = <1>;
>> reg = <0x900000 0x4000>;
>> + clocks = <&pxo_board>, <&cxo_board>;
>> + clock-names = "pxo", "cxo";
>> };
>>
>> gsbi6: gsbi@16500000 {
>> --
>> 2.35.1
>>
--
With best wishes
Dmitry
next prev parent reply other threads:[~2022-07-14 7:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 11:07 [PATCH 1/4] dt-bindings: clock: qcom,gcc-msm8660: separate GCC bindings for MSM8660 Dmitry Baryshkov
2022-06-20 11:07 ` [PATCH 2/4] clk: qcom: gcc-msm8660: use ARRAY_SIZE instead of specifying num_parents Dmitry Baryshkov
2022-06-20 11:07 ` [PATCH 3/4] clk: qcom: gcc-msm8660: use parent_hws/_data instead of parent_names Dmitry Baryshkov
2022-06-20 11:07 ` [PATCH 4/4] ARM: dts: qcom: msm8660: add pxo/cxo clocks to the GCC node Dmitry Baryshkov
2022-06-20 11:17 ` Krzysztof Kozlowski
2022-06-20 11:25 ` Dmitry Baryshkov
2022-06-20 11:52 ` Krzysztof Kozlowski
2022-06-20 11:52 ` Krzysztof Kozlowski
2022-07-13 21:29 ` Bjorn Andersson
2022-07-14 7:41 ` Dmitry Baryshkov [this message]
2022-07-14 8:09 ` Krzysztof Kozlowski
2022-06-20 11:16 ` [PATCH 1/4] dt-bindings: clock: qcom,gcc-msm8660: separate GCC bindings for MSM8660 Krzysztof Kozlowski
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=50ce334b-4c13-1eb3-0e6e-96c9ccee7e1d@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=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;
as well as URLs for NNTP newsgroup(s).