devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@somainline.org>
To: Dmitry Baryshkov <dmitry.baryshkov@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,
	Marijn Suijten <marijn.suijten@somainline.org>
Subject: Re: [PATCH v3 0/7] clk: qcom: gcc-msm8916: modernize the driver
Date: Mon, 20 Jun 2022 14:12:54 +0200	[thread overview]
Message-ID: <cb15fe73-2805-7776-307d-02e1b175301c@somainline.org> (raw)
In-Reply-To: <20220619212735.1244953-1-dmitry.baryshkov@linaro.org>



On 19.06.2022 23:27, Dmitry Baryshkov wrote:
> Please excuse me for the spam, I've erroneously sent v2 without the
> requested change.
> 
Please excuse me, I didn't notice and gave you R-bs on v2 instead..

Konrad
> Update gcc-msm8916 driver and bindings to use DT-specified clocks
> rather than fetching the clocks from the global clocks list.
> 
> Changes since v2:
>  - Use xo-board for the XO rather than RPM clock. This will be sorted
>    out separately (requested by Stephan Gerhold).
> 
> Changes since v1:
>  - None.
> 
> Dmitry Baryshkov (7):
>   dt-bindings: clk: qcom,gcc-*: use qcom,gcc.yaml
>   dt-bindings: clock: separate bindings for MSM8916 GCC device
>   clk: qcom: gcc-msm8916: use ARRAY_SIZE instead of specifying
>     num_parents
>   clk: qcom: gcc-msm8916: move clock parent tables down
>   clk: qcom: gcc-msm8916: move gcc_mss_q6_bimc_axi_clk down
>   clk: qcom: gcc-msm8916: use parent_hws/_data instead of parent_names
>   arm64: dts: qcom: msm8916: add clocks to the GCC device node
> 
>  .../bindings/clock/qcom,gcc-msm8916.yaml      |   61 +
>  .../bindings/clock/qcom,gcc-msm8976.yaml      |   21 +-
>  .../bindings/clock/qcom,gcc-msm8994.yaml      |   21 +-
>  .../bindings/clock/qcom,gcc-msm8996.yaml      |   25 +-
>  .../bindings/clock/qcom,gcc-msm8998.yaml      |   25 +-
>  .../bindings/clock/qcom,gcc-other.yaml        |    1 -
>  .../bindings/clock/qcom,gcc-qcm2290.yaml      |   25 +-
>  .../bindings/clock/qcom,gcc-sc7180.yaml       |   25 +-
>  .../bindings/clock/qcom,gcc-sc7280.yaml       |   21 +-
>  .../bindings/clock/qcom,gcc-sc8180x.yaml      |   25 +-
>  .../bindings/clock/qcom,gcc-sc8280xp.yaml     |   21 +-
>  .../bindings/clock/qcom,gcc-sdm845.yaml       |   25 +-
>  .../bindings/clock/qcom,gcc-sdx55.yaml        |   21 +-
>  .../bindings/clock/qcom,gcc-sdx65.yaml        |   21 +-
>  .../bindings/clock/qcom,gcc-sm6115.yaml       |   25 +-
>  .../bindings/clock/qcom,gcc-sm6125.yaml       |   25 +-
>  .../bindings/clock/qcom,gcc-sm6350.yaml       |   25 +-
>  .../bindings/clock/qcom,gcc-sm8150.yaml       |   25 +-
>  .../bindings/clock/qcom,gcc-sm8250.yaml       |   25 +-
>  .../bindings/clock/qcom,gcc-sm8350.yaml       |   21 +-
>  .../bindings/clock/qcom,gcc-sm8450.yaml       |   21 +-
>  arch/arm64/boot/dts/qcom/msm8916.dtsi         |   14 +
>  drivers/clk/qcom/gcc-msm8916.c                | 1020 +++++++++--------
>  23 files changed, 669 insertions(+), 870 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/clock/qcom,gcc-msm8916.yaml
> 

  parent reply	other threads:[~2022-06-20 12:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-19 21:27 [PATCH v3 0/7] clk: qcom: gcc-msm8916: modernize the driver Dmitry Baryshkov
2022-06-19 21:27 ` [PATCH v3 1/7] dt-bindings: clk: qcom,gcc-*: use qcom,gcc.yaml Dmitry Baryshkov
2022-06-20 12:05   ` Dmitry Baryshkov
2022-06-27 21:11   ` Marijn Suijten
2022-06-19 21:27 ` [PATCH v3 2/7] dt-bindings: clock: separate bindings for MSM8916 GCC device Dmitry Baryshkov
2022-06-20 12:06   ` Dmitry Baryshkov
2022-06-27 21:09   ` Marijn Suijten
2022-06-19 21:27 ` [PATCH v3 3/7] clk: qcom: gcc-msm8916: use ARRAY_SIZE instead of specifying num_parents Dmitry Baryshkov
2022-06-27 21:03   ` Marijn Suijten
2022-07-04 17:12     ` Dmitry Baryshkov
2022-06-19 21:27 ` [PATCH v3 4/7] clk: qcom: gcc-msm8916: move clock parent tables down Dmitry Baryshkov
2022-06-19 21:27 ` [PATCH v3 5/7] clk: qcom: gcc-msm8916: move gcc_mss_q6_bimc_axi_clk down Dmitry Baryshkov
2022-06-27 21:18   ` Marijn Suijten
2022-06-28 12:40     ` Dmitry Baryshkov
2022-06-19 21:27 ` [PATCH v3 6/7] clk: qcom: gcc-msm8916: use parent_hws/_data instead of parent_names Dmitry Baryshkov
2022-06-27 21:28   ` Marijn Suijten
2022-06-19 21:27 ` [PATCH v3 7/7] arm64: dts: qcom: msm8916: add clocks to the GCC device node Dmitry Baryshkov
2022-06-20 12:13   ` Konrad Dybcio
2022-06-27 21:29   ` Marijn Suijten
2022-06-20 12:12 ` Konrad Dybcio [this message]
2022-07-04 16:24   ` [PATCH v3 0/7] clk: qcom: gcc-msm8916: modernize the driver 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=cb15fe73-2805-7776-307d-02e1b175301c@somainline.org \
    --to=konrad.dybcio@somainline.org \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=marijn.suijten@somainline.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).