From: Yassine Oudjana <yassine.oudjana@gmail.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Loic Poulain <loic.poulain@linaro.org>,
Yassine Oudjana <y.oudjana@protonmail.com>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@somainline.org>,
Martin Botka <martin.botka@somainline.org>,
Marijn Suijten <marijn.suijten@somainline.org>,
Jami Kettunen <jami.kettunen@somainline.org>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/6] dt-bindings: clock: qcom,msm8996-apcc: Fix clocks
Date: Tue, 21 Jun 2022 21:28:45 +0400 [thread overview]
Message-ID: <XJ8UDR.9Y06T8FUTMOH2@gmail.com> (raw)
In-Reply-To: <CAA8EJprQTiU+=ajKSWbFfbHuVxjEiybTPNez66Ob+4YZ+fXW_A@mail.gmail.com>
On Tue, Jun 21 2022 at 20:07:50 +0300, Dmitry Baryshkov
<dmitry.baryshkov@linaro.org> wrote:
> On Tue, 21 Jun 2022 at 19:07, Yassine Oudjana
> <yassine.oudjana@gmail.com> wrote:
>>
>> From: Yassine Oudjana <y.oudjana@protonmail.com>
>>
>> The clocks currently listed in clocks and clock-names are the ones
>> supplied by this clock controller, not the ones it consumes. Replace
>> them with the only clock it consumes - the on-board oscillator (XO),
>> and make the properties required.
>>
>> Signed-off-by: Yassine Oudjana <y.oudjana@protonmail.com>
>> ---
>> .../bindings/clock/qcom,msm8996-apcc.yaml | 15
>> +++++++--------
>> 1 file changed, 7 insertions(+), 8 deletions(-)
>>
>> diff --git
>> a/Documentation/devicetree/bindings/clock/qcom,msm8996-apcc.yaml
>> b/Documentation/devicetree/bindings/clock/qcom,msm8996-apcc.yaml
>> index a20cb10636dd..c4971234fef8 100644
>> --- a/Documentation/devicetree/bindings/clock/qcom,msm8996-apcc.yaml
>> +++ b/Documentation/devicetree/bindings/clock/qcom,msm8996-apcc.yaml
>> @@ -26,22 +26,18 @@ properties:
>>
>> clocks:
>> items:
>> - - description: Primary PLL clock for power cluster (little)
>> - - description: Primary PLL clock for perf cluster (big)
>> - - description: Alternate PLL clock for power cluster (little)
>> - - description: Alternate PLL clock for perf cluster (big)
>> + - description: XO source
>>
>> clock-names:
>> items:
>> - - const: pwrcl_pll
>> - - const: perfcl_pll
>> - - const: pwrcl_alt_pll
>> - - const: perfcl_alt_pll
>> + - const: xo
>>
>> required:
>> - compatible
>> - reg
>> - '#clock-cells'
>> + - clocks
>> + - clock-names
>
> I think we can not list them as required, as then older DT files won't
> pass schema validation. But I'll leave this into the hands of Rob and
> Krzyshtof.
The old DT files that didn't have XO defined had a wrong
compatible string to begin with (fixed in [1]), so I don't
think it's a problem.
>> additionalProperties: false
>>
>> @@ -51,4 +47,7 @@ examples:
>> compatible = "qcom,msm8996-apcc";
>> reg = <0x6400000 0x90000>;
>> #clock-cells = <1>;
>> +
>> + clocks = <&xo_board>;
>> + clock-names = "xo";
>> };
>> --
>> 2.36.1
>>
>
>
> --
> With best wishes
> Dmitry
[1]
https://lore.kernel.org/linux-arm-msm/20210527192958.775434-1-konrad.dybcio@somainline.org/
next prev parent reply other threads:[~2022-06-21 17:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 16:06 [PATCH 0/6] clk: qcom: msm8996-cpu: Cleanup and migrate to parent_data Yassine Oudjana
2022-06-21 16:06 ` [PATCH 1/6] clk: qcom: msm8996-cpu: Rename DIV_2_INDEX to SMUX_INDEX Yassine Oudjana
2022-06-21 17:01 ` Dmitry Baryshkov
2022-06-21 16:06 ` [PATCH 2/6] clk: qcom: msm8996-cpu: Statically define PLL dividers Yassine Oudjana
2022-06-21 17:02 ` Dmitry Baryshkov
2022-07-14 8:32 ` Yassine Oudjana
2022-07-14 9:42 ` Dmitry Baryshkov
2022-06-21 16:06 ` [PATCH 3/6] clk: qcom: msm8996-cpu: Unify cluster order Yassine Oudjana
2022-06-21 17:03 ` Dmitry Baryshkov
2022-06-21 16:06 ` [PATCH 4/6] clk: qcom: msm8996-cpu: Convert secondary muxes to clk_regmap_mux Yassine Oudjana
2022-06-21 17:05 ` Dmitry Baryshkov
2022-06-21 16:06 ` [PATCH 5/6] dt-bindings: clock: qcom,msm8996-apcc: Fix clocks Yassine Oudjana
2022-06-21 17:07 ` Dmitry Baryshkov
2022-06-21 17:28 ` Yassine Oudjana [this message]
2022-06-21 17:32 ` Dmitry Baryshkov
2022-06-22 14:59 ` Krzysztof Kozlowski
2022-06-21 16:06 ` [PATCH 6/6] clk: qcom: msm8996-cpu: Use parent_data for all clocks Yassine Oudjana
2022-06-21 17:09 ` Dmitry Baryshkov
2022-07-13 21:32 ` [PATCH 0/6] clk: qcom: msm8996-cpu: Cleanup and migrate to parent_data Bjorn Andersson
2022-07-14 10:06 ` Dmitry Baryshkov
2022-09-09 10:21 ` Dmitry Baryshkov
2022-09-27 3:23 ` (subset) " Bjorn Andersson
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=XJ8UDR.9Y06T8FUTMOH2@gmail.com \
--to=yassine.oudjana@gmail.com \
--cc=agross@kernel.org \
--cc=angelogioacchino.delregno@somainline.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=jami.kettunen@somainline.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=marijn.suijten@somainline.org \
--cc=martin.botka@somainline.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=y.oudjana@protonmail.com \
/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).