All of lore.kernel.org
 help / color / mirror / Atom feed
From: viresh.kumar@st.com (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: SPEAr600: Change FSMC and SMI clock names
Date: Fri, 23 Mar 2012 08:59:28 +0530	[thread overview]
Message-ID: <4F6BEE18.1080209@st.com> (raw)
In-Reply-To: <1332420073-17703-1-git-send-email-sr@denx.de>

On 3/22/2012 6:11 PM, Stefan Roese wrote:
> Change FSMC and SMI clock names to match the ones needed for DT based
> probing.
> 

please keep spear-devel at list.st.com in cc. :)

> Signed-off-by: Stefan Roese <sr@denx.de>
> Cc: Viresh Kumar <viresh.kumar@st.com>
> ---
>  arch/arm/mach-spear6xx/clock.c |    4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/arm/mach-spear6xx/clock.c b/arch/arm/mach-spear6xx/clock.c
> index a86499a..f051804 100644
> --- a/arch/arm/mach-spear6xx/clock.c
> +++ b/arch/arm/mach-spear6xx/clock.c
> @@ -660,8 +660,8 @@ static struct clk_lookup spear_clk_lookups[] = {
>  	{ .dev_id = "dma",		.clk = &dma_clk},
>  	{ .dev_id = "jpeg",		.clk = &jpeg_clk},
>  	{ .dev_id = "gmac",		.clk = &gmac_clk},
> -	{ .dev_id = "smi",		.clk = &smi_clk},
> -	{ .dev_id = "fsmc-nand",	.clk = &fsmc_clk},
> +	{ .dev_id = "fc000000.flash",	.clk = &smi_clk},
> +	{ .dev_id = "d1800000.flash",	.clk = &fsmc_clk},
>  	/* clock derived from apb clk */
>  	{ .dev_id = "adc",		.clk = &adc_clk},
>  	{ .dev_id = "ssp-pl022.0",	.clk = &ssp0_clk},

Acked-by: Viresh Kumar <viresh.kumar@st.com>

@Arnd: I would start to apply these patches on my git tree from now
onwards and will send you pull request later.

-- 
viresh

      reply	other threads:[~2012-03-23  3:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-22 12:41 [PATCH] ARM: SPEAr600: Change FSMC and SMI clock names Stefan Roese
2012-03-23  3:29 ` Viresh Kumar [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=4F6BEE18.1080209@st.com \
    --to=viresh.kumar@st.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.