From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@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>
Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 00/15] clk: qcom: use parent_hws/_data for APQ8064 clocks
Date: Fri, 9 Sep 2022 13:16:40 +0300 [thread overview]
Message-ID: <a7bd2a82-4015-7899-47ed-da7a5ce6141c@linaro.org> (raw)
In-Reply-To: <20220623120418.250589-1-dmitry.baryshkov@linaro.org>
On 23/06/2022 15:04, Dmitry Baryshkov wrote:
> This series converts the APQ8064/MSM8960 clock drivers, bindings and DTs
> to use parent_hws/_data and excplicit clock binding in DT.
>
> Dependencies: [1] (whole series), [2], [3]
>
> [1] https://lore.kernel.org/linux-arm-msm/20220521151437.1489111-1-dmitry.baryshkov@linaro.org/
> [2] https://lore.kernel.org/linux-arm-msm/20220617122922.769562-2-dmitry.baryshkov@linaro.org/
> [3] https://lore.kernel.org/linux-arm-msm/20220617122922.769562-3-dmitry.baryshkov@linaro.org/
>
Bjorn, Gracious ping for this patchset
> Dmitry Baryshkov (15):
> dt-bindings: clocks: qcom,gcc-apq8064: define clocks/-names properties
> dt-bindings: clocks: qcom,mmcc: define clocks/clock-names for MSM8960
> clk: qcom: gcc-msm8960: use ARRAY_SIZE instead of specifying
> num_parents
> clk: qcom: gcc-msm8960: use parent_hws/_data instead of parent_names
> clk: qcom: lcc-msm8960: use macros to implement mi2s clocks
> clk: qcom: lcc-msm8960: use parent_hws/_data instead of parent_names
> clk: qcom: mmcc-msm8960: use ARRAY_SIZE instead of specifying
> num_parents
> clk: qcom: mmcc-msm8960: move clock parent tables down
> clk: qcom: mmcc-msm8960: use parent_hws/_data instead of parent_names
> ARM: dts: qcom: apq8064: add clocks to the LCC device node
> ARM: dts: qcom: msm8960: add clocks to the LCC device node
> ARM: dts: qcom: apq8064: add clocks to the GCC device node
> ARM: dts: qcom: msm8960: add clocks to the GCC device node
> ARM: dts: qcom: apq8064: add clocks to the MMCC device node
> ARM: dts: qcom: msm8960: add clocks to the MMCC device node
>
> .../bindings/clock/qcom,gcc-apq8064.yaml | 9 +
> .../devicetree/bindings/clock/qcom,mmcc.yaml | 31 ++
> arch/arm/boot/dts/qcom-apq8064.dtsi | 35 ++
> arch/arm/boot/dts/qcom-msm8960.dtsi | 39 +-
> drivers/clk/qcom/gcc-msm8960.c | 436 ++++++++++-------
> drivers/clk/qcom/lcc-msm8960.c | 211 +++-----
> drivers/clk/qcom/mmcc-msm8960.c | 454 +++++++++++-------
> 7 files changed, 713 insertions(+), 502 deletions(-)
>
--
With best wishes
Dmitry
next prev parent reply other threads:[~2022-09-09 10:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 12:04 [PATCH 00/15] clk: qcom: use parent_hws/_data for APQ8064 clocks Dmitry Baryshkov
2022-06-23 12:04 ` [PATCH 01/15] dt-bindings: clocks: qcom,gcc-apq8064: define clocks/-names properties Dmitry Baryshkov
2022-06-24 15:56 ` Krzysztof Kozlowski
2022-06-23 12:04 ` [PATCH 02/15] dt-bindings: clocks: qcom,mmcc: define clocks/clock-names for MSM8960 Dmitry Baryshkov
2022-06-24 15:57 ` Krzysztof Kozlowski
2022-06-25 0:00 ` Dmitry Baryshkov
2022-08-30 7:17 ` Dmitry Baryshkov
2022-08-30 14:56 ` Krzysztof Kozlowski
2022-06-23 12:04 ` [PATCH 03/15] clk: qcom: gcc-msm8960: use ARRAY_SIZE instead of specifying num_parents Dmitry Baryshkov
2022-06-23 12:04 ` [PATCH 04/15] clk: qcom: gcc-msm8960: use parent_hws/_data instead of parent_names Dmitry Baryshkov
2022-06-23 12:04 ` [PATCH 05/15] clk: qcom: lcc-msm8960: use macros to implement mi2s clocks Dmitry Baryshkov
2022-06-23 12:04 ` [PATCH 06/15] clk: qcom: lcc-msm8960: use parent_hws/_data instead of parent_names Dmitry Baryshkov
2022-06-23 12:04 ` [PATCH 07/15] clk: qcom: mmcc-msm8960: use ARRAY_SIZE instead of specifying num_parents Dmitry Baryshkov
2022-06-23 12:04 ` [PATCH 08/15] clk: qcom: mmcc-msm8960: move clock parent tables down Dmitry Baryshkov
2022-06-23 12:04 ` [PATCH 09/15] clk: qcom: mmcc-msm8960: use parent_hws/_data instead of parent_names Dmitry Baryshkov
2022-06-23 12:04 ` [PATCH 10/15] ARM: dts: qcom: apq8064: add clocks to the LCC device node Dmitry Baryshkov
2022-06-23 12:04 ` [PATCH 11/15] ARM: dts: qcom: msm8960: " Dmitry Baryshkov
2022-06-23 12:04 ` [PATCH 12/15] ARM: dts: qcom: apq8064: add clocks to the GCC " Dmitry Baryshkov
2022-06-23 12:04 ` [PATCH 13/15] ARM: dts: qcom: msm8960: " Dmitry Baryshkov
2022-06-23 12:04 ` [PATCH 14/15] ARM: dts: qcom: apq8064: add clocks to the MMCC " Dmitry Baryshkov
2022-06-23 12:04 ` [PATCH 15/15] ARM: dts: qcom: msm8960: " Dmitry Baryshkov
2022-07-04 20:14 ` [PATCH 00/15] clk: qcom: use parent_hws/_data for APQ8064 clocks David Heidelberg
2022-09-09 10:16 ` Dmitry Baryshkov [this message]
2022-09-15 3:36 ` (subset) " Bjorn Andersson
-- strict thread matches above, loose matches on Subject: below --
2022-08-03 10:45 Shinjo Park
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=a7bd2a82-4015-7899-47ed-da7a5ce6141c@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.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).