linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: Stephen Boyd <sboyd@kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Loic Poulain <loic.poulain@linaro.org>,
	devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] clk: qcom: Add Global Clock Controller driver for QCM2290
Date: Wed, 22 Sep 2021 15:53:27 -0500	[thread overview]
Message-ID: <YUuXxzGnc9iU/eYN@robh.at.kernel.org> (raw)
In-Reply-To: <20210919023308.24498-3-shawn.guo@linaro.org>

On Sun, Sep 19, 2021 at 10:33:08AM +0800, Shawn Guo wrote:
> Add Global Clock Controller (GCC) driver for QCM2290.  This is a porting
> of gcc-scuba driver from CAF msm-4.19, with GDSC support added on top.
> 
> Because the alpha_pll on the platform has a different register
> layout (offsets), its own clk_alpha_pll_regs_offset[] is used in the
> driver.
> 
> Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
> ---
>  drivers/clk/qcom/Kconfig                     |    7 +
>  drivers/clk/qcom/Makefile                    |    1 +
>  drivers/clk/qcom/gcc-qcm2290.c               | 3047 ++++++++++++++++++
>  include/dt-bindings/clock/qcom,gcc-qcm2290.h |  188 ++

Really this should be in the binding patch.

Acked-by: Rob Herring <robh@kernel.org>

>  4 files changed, 3243 insertions(+)
>  create mode 100644 drivers/clk/qcom/gcc-qcm2290.c
>  create mode 100644 include/dt-bindings/clock/qcom,gcc-qcm2290.h


  reply	other threads:[~2021-09-22 20:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-19  2:33 [PATCH v3 0/2] Add QCM2290 Global Clock Controller driver Shawn Guo
2021-09-19  2:33 ` [PATCH v3 1/2] dt-bindings: clk: qcom: Add QCM2290 Global Clock Controller bindings Shawn Guo
2021-09-22 20:52   ` Rob Herring
2021-10-13 19:39   ` Stephen Boyd
2021-09-19  2:33 ` [PATCH v3 2/2] clk: qcom: Add Global Clock Controller driver for QCM2290 Shawn Guo
2021-09-22 20:53   ` Rob Herring [this message]
2021-10-13 19:39   ` Stephen Boyd

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=YUuXxzGnc9iU/eYN@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.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=sboyd@kernel.org \
    --cc=shawn.guo@linaro.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).