linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Enable clock controllers on MSM
Date: Thu, 23 Jan 2014 09:25:37 -0800	[thread overview]
Message-ID: <878uu6y5im.fsf@paris.lan> (raw)
In-Reply-To: <1389921904-3777-1-git-send-email-sboyd@codeaurora.org> (Stephen Boyd's message of "Thu, 16 Jan 2014 17:25:02 -0800")

Stephen Boyd <sboyd@codeaurora.org> writes:

> These patches add the clock controller nodes, enable the clock drivers
> on MSM based platforms, and hook it up enough to get the serial console
> working. This is based on the merge of Mike's clk-next branch with
> linux-next-20140116. The changes need the clk-next branch because that's
> where the DTS include files landed.

I forgot to repond to this earlier, but I tested this on top of -next
and it gets the dragonboard booting w/mainline.  Yay!

> Perhaps this can be applied after 3.14-rc1 is out?

Yeah, sounds good.

Kevin

> Stephen Boyd (2):
>   ARM: dts: msm: Add clock controller nodes and hook into uart
>   ARM: msm_defconfig: Enable MSM clock drivers
>
>  arch/arm/boot/dts/qcom-msm8660-surf.dts | 11 +++++++++++
>  arch/arm/boot/dts/qcom-msm8960-cdp.dts  | 18 ++++++++++++++++++
>  arch/arm/boot/dts/qcom-msm8974.dtsi     | 24 ++++++++++++++++++++++++
>  arch/arm/configs/msm_defconfig          |  4 ++++
>  4 files changed, 57 insertions(+)

  parent reply	other threads:[~2014-01-23 17:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-17  1:25 [PATCH 0/2] Enable clock controllers on MSM Stephen Boyd
2014-01-17  1:25 ` [PATCH 1/2] ARM: dts: msm: Add clock controller nodes and hook into uart Stephen Boyd
2014-01-17  1:25 ` [PATCH 2/2] ARM: msm_defconfig: Enable MSM clock drivers Stephen Boyd
2014-01-23 17:25 ` Kevin Hilman [this message]
2014-01-23 19:59   ` [PATCH 0/2] Enable clock controllers on MSM Kumar Gala
2014-01-23 20:43     ` Olof Johansson
2014-01-23 21:57       ` Kumar Gala
2014-01-23 22:08         ` Olof Johansson
2014-01-27 21:52         ` Mike Turquette

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=878uu6y5im.fsf@paris.lan \
    --to=khilman@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).