linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: srinivas.kandagatla@linaro.org (Srinivas Kandagatla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] Support apq8064 global clock control
Date: Thu, 10 Jul 2014 09:16:33 +0100	[thread overview]
Message-ID: <1404980193-5967-1-git-send-email-srinivas.kandagatla@linaro.org> (raw)
In-Reply-To: <1402433906-19309-1-git-send-email-sboyd@codeaurora.org>

These two patches add full support for apq8064 in the global clock
controller driver. The first patch has already been on the list so
I've picked it up and resent because the second patch depends on it.

Am resending the series with the fix to my patch.

Changes since v1:
	- fixed comment log spotted by Andreas.
	- added few more sdcc clocks.

Srinivas Kandagatla (1):
  clk: qcom: add clocks necessary for apq8064 sdcc

Stephen Boyd (1):
  clk: qcom: Fully support apq8064 global clock control

 drivers/clk/qcom/gcc-msm8960.c               | 583 ++++++++++++++++++++++++++-
 include/dt-bindings/clock/qcom,gcc-msm8960.h |  11 +
 include/dt-bindings/reset/qcom,gcc-msm8960.h |  16 +
 3 files changed, 607 insertions(+), 3 deletions(-)

-- 
1.9.1

  parent reply	other threads:[~2014-07-10  8:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-10 20:58 [PATCH 0/2] Support apq8064 global clock control Stephen Boyd
2014-06-10 20:58 ` [PATCH 1/2] clk: qcom: add clocks necessary for apq8064 sdcc Stephen Boyd
2014-06-11  9:14   ` Andreas Färber
2014-06-11 11:11     ` Srinivas Kandagatla
2014-06-10 20:58 ` [PATCH 2/2] clk: qcom: Fully support apq8064 global clock control Stephen Boyd
2014-07-10  8:16 ` Srinivas Kandagatla [this message]
2014-07-10  8:18   ` [PATCH v2 1/2] clk: qcom: add clocks necessary for apq8064 sdcc Srinivas Kandagatla
2014-07-10  8:18   ` [PATCH v2 2/2] clk: qcom: Fully support apq8064 global clock control Srinivas Kandagatla
2014-07-15  8:39   ` [PATCH v2 0/2] Support " Srinivas Kandagatla

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=1404980193-5967-1-git-send-email-srinivas.kandagatla@linaro.org \
    --to=srinivas.kandagatla@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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).