From: Kumar Gala <galak@codeaurora.org>
To: Mike Turquette <mturquette@linaro.org>
Cc: devicetree@vger.kernel.org, sboyd@codeaurora.org,
linux-kernel@vger.kernel.org, agross@codeaurora.org,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v4] clk: qcom: Add support for IPQ8064's global clock controller (GCC)
Date: Mon, 30 Jun 2014 11:08:33 -0500 [thread overview]
Message-ID: <6639D384-040E-498A-8C0B-B3FAF47692ED@codeaurora.org> (raw)
In-Reply-To: <1403034411-13781-1-git-send-email-galak@codeaurora.org>
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?
- k
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
prev parent reply other threads:[~2014-06-30 16:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 19:46 Kumar Gala
2014-06-30 16:08 ` Kumar Gala [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=6639D384-040E-498A-8C0B-B3FAF47692ED@codeaurora.org \
--to=galak@codeaurora.org \
--cc=agross@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@linaro.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
all inboxes | Powered by JetHome®