devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Turquette <mturquette@linaro.org>
To: Kumar Gala <galak@codeaurora.org>
Cc: devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	sboyd@codeaurora.org, linux-kernel@vger.kernel.org,
	agross@codeaurora.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4] clk: qcom: Add support for IPQ8064's global clock controller (GCC)
Date: Tue, 01 Jul 2014 21:20:57 -0700	[thread overview]
Message-ID: <20140702042057.23338.96243@quantum> (raw)
In-Reply-To: <6639D384-040E-498A-8C0B-B3FAF47692ED@codeaurora.org>

Quoting Kumar Gala (2014-06-30 09:08:33)
> 
> On Jun 17, 2014, at 2:46 PM, Kumar Gala <galak@codeaurora.org> wrote:
> 
> > Add a driver for the global clock controller found on IPQ8064 based
> > platforms. This should allow most non-multimedia device drivers to probe
> > and control their clocks.
> > 
> > This is currently missing clocks for USB HSIC and networking devices.
> > 
> > Signed-off-by: Kumar Gala <galak@codeaurora.org>
> > Signed-off-by: Andy Gross <agross@codeaurora.org>
> > Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
> > ---
> > v4:
> > * Fix usb utmi freq clk table
> > * Fix numbering issue in dt-bindings/clock/qcom,gcc-ipq806x.h
> > 
> > v3:
> > * Based on APQ8084 clk patches
> > * Added USB3 and SATA clks
> > * Minor clean ups (made hex numbers lowercase)
> > 
> > v2:
> > * dropped audio clock from commit message
> > * changed Kconfig symbol to IPQ_GCC_806X
> > * Fixed PXO/CXO clk freq to 25Mhz
> > 
> > .../devicetree/bindings/clock/qcom,gcc.txt         |    1 +
> > drivers/clk/qcom/Kconfig                           |    8 +
> > drivers/clk/qcom/Makefile                          |    1 +
> > drivers/clk/qcom/gcc-ipq806x.c                     | 2424 ++++++++++++++++++++
> > include/dt-bindings/clock/qcom,gcc-ipq806x.h       |  293 +++
> > include/dt-bindings/reset/qcom,gcc-ipq806x.h       |  132 ++
> > 6 files changed, 2859 insertions(+)
> > create mode 100644 drivers/clk/qcom/gcc-ipq806x.c
> > create mode 100644 include/dt-bindings/clock/qcom,gcc-ipq806x.h
> > create mode 100644 include/dt-bindings/reset/qcom,gcc-ipq806x.h
> 
> Mike,
> 
> Any update on pulling this in?

Looks good to me.

What's the story on getting a pull request for qcom clock stuff in the
future? For more mature clock drivers it is nice for a clock maintainer
(maybe Stephen in this case, based on patch count in drivers/clk/qcom?)
to batch up everything. It also helps lazy maintainers like me not have
to review every line of code for the non-controversial stuff.

Regards,
Mike

> 
> - k
> 
> -- 
> Employee of Qualcomm Innovation Center, Inc.
> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
> 

      reply	other threads:[~2014-07-02  4:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-17 19:46 [PATCH v4] clk: qcom: Add support for IPQ8064's global clock controller (GCC) Kumar Gala
2014-06-30 16:08 ` Kumar Gala
2014-07-02  4:20   ` Mike Turquette [this message]

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=20140702042057.23338.96243@quantum \
    --to=mturquette@linaro.org \
    --cc=agross@codeaurora.org \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sboyd@codeaurora.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).