public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mach-mxs: readd just removed select CLKSRC_OF
Date: Wed, 16 Apr 2014 16:34:49 +0800	[thread overview]
Message-ID: <20140416083447.GB11602@dragon> (raw)
In-Reply-To: <1397546439-25153-1-git-send-email-lauri.hintsala@bluegiga.com>

On Tue, Apr 15, 2014 at 10:20:39AM +0300, Lauri Hintsala wrote:
> MXS based apx4devkit doesn't boot with latest Linux v3.15-rc1
> because commit ddb902cc34593ecb88c368f6e15db3cf829c56fe removed
> "select CLKSRC_OF" from the machine config.
> 
> CC: linux-arm-kernel at lists.infradead.org
> CC: Rob Herring <robh@kernel.org>
> CC: Shawn Guo <shawn.guo@linaro.org>

Acked-by: Shawn Guo <shawn.guo@linaro.org>

Hi, arm-soc folks,

I just sent a batch of fixes for 3.15 off my hand to you guys.  Can you
please apply this fix directly on arm-soc for 3.15?  Thanks.

Shawn

> Signed-off-by: Lauri Hintsala <lauri.hintsala@bluegiga.com>
> ---
> I think commit ddb902cc34593ecb88c368f6e15db3cf829c56fe might break
> also other armv4/5 based boards which are using CLKSRC_OF. There is
> already patch for MOXA ART SoCs: https://lkml.org/lkml/2014/4/11/308
> 
>  arch/arm/mach-mxs/Kconfig | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/arch/arm/mach-mxs/Kconfig b/arch/arm/mach-mxs/Kconfig
> index 8479413..b3eb28c 100644
> --- a/arch/arm/mach-mxs/Kconfig
> +++ b/arch/arm/mach-mxs/Kconfig
> @@ -17,6 +17,7 @@ config ARCH_MXS
>  	depends on ARCH_MULTI_V5
>  	select ARCH_REQUIRE_GPIOLIB
>  	select CLKSRC_MMIO
> +	select CLKSRC_OF
>  	select PINCTRL
>  	select SOC_BUS
>  	select SOC_IMX23
> -- 
> 1.8.3.2
> 

  reply	other threads:[~2014-04-16  8:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-15  7:20 [PATCH] ARM: mach-mxs: readd just removed select CLKSRC_OF Lauri Hintsala
2014-04-16  8:34 ` Shawn Guo [this message]
2014-04-16 13:44   ` Rob Herring

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=20140416083447.GB11602@dragon \
    --to=shawn.guo@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