linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] clk: ux500: Ensure the FMSC clock is obtainable
Date: Tue, 15 Jan 2013 15:52:52 -0800	[thread overview]
Message-ID: <20130115235252.23734.21408@quantum> (raw)
In-Reply-To: <1355937587-31730-2-git-send-email-lee.jones@linaro.org>

Quoting Lee Jones (2012-12-19 09:19:45)
> The FMSC clock is traditionally used for NAND flash devices when
> used on the ux500 series platforms. This patch makes it searchable
> during a clock-name search.
> 
> Cc: Mike Turquette <mturquette@linaro.org>
> Cc: Ulf Hansson <ulf.hansson@linaro.org>
> Signed-off-by: Lee Jones <lee.jones@linaro.org>

Acked-by: Mike Turquette <mturquette@linaro.org>

Who do you want this series to go through?

Regards,
Mike

> ---
>  drivers/clk/ux500/u8500_clk.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/clk/ux500/u8500_clk.c b/drivers/clk/ux500/u8500_clk.c
> index 6b889a0..a601802 100644
> --- a/drivers/clk/ux500/u8500_clk.c
> +++ b/drivers/clk/ux500/u8500_clk.c
> @@ -324,7 +324,7 @@ void u8500_clk_init(void)
>  
>         clk = clk_reg_prcc_pclk("p3_pclk0", "per3clk", U8500_CLKRST3_BASE,
>                                 BIT(0), 0);
> -       clk_register_clkdev(clk, NULL, "fsmc");
> +       clk_register_clkdev(clk, "fsmc", NULL);
>  
>         clk = clk_reg_prcc_pclk("p3_pclk1", "per3clk", U8500_CLKRST3_BASE,
>                                 BIT(1), 0);
> -- 
> 1.7.9.5

  reply	other threads:[~2013-01-15 23:52 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-19 17:19 [PATCH 1/4] ARM: ux500: Provide a means to obtain the SMSC9115 clock when DT is enabled Lee Jones
2012-12-19 17:19 ` [PATCH 2/4] clk: ux500: Ensure the FMSC clock is obtainable Lee Jones
2013-01-15 23:52   ` Mike Turquette [this message]
2013-01-16  9:59     ` Lee Jones
2012-12-19 17:19 ` [PATCH 3/4] clk: ux500: Provide an alias for the SMSC911x Ethernet chip Lee Jones
2013-01-09  8:56   ` Lee Jones
2013-01-09 16:26     ` Ulf Hansson
2013-01-15 23:53     ` Mike Turquette
2012-12-19 17:19 ` [PATCH 4/4] net/smsc911x: Provide common clock functionality Lee Jones
2012-12-20 19:12   ` Linus Walleij
2012-12-20 19:24     ` Russell King - ARM Linux
2012-12-20 20:35       ` Lee Jones
2012-12-20 20:51         ` Russell King - ARM Linux
2012-12-21  9:13           ` Lee Jones
2012-12-21  9:24             ` Russell King - ARM Linux
2012-12-21 11:41               ` [PATCH 4/4 v2] " Lee Jones
2012-12-26  0:51                 ` Linus Walleij
2012-12-27 19:31                   ` Lee Jones
2013-01-03 11:14                 ` [PATCH 4/4 v3] " Lee Jones
2013-01-03 14:28                   ` Linus Walleij
2013-01-07 14:16                     ` Lee Jones
2013-01-09  8:55                     ` Lee Jones
2013-01-09 16:32                       ` Ulf Hansson
2013-01-17 10:25                       ` Linus Walleij
2013-01-17 10:47                         ` Lee Jones
2013-01-17 19:36                           ` David Miller
2013-01-09  8:56   ` [PATCH 4/4] " Lee Jones
2012-12-20 19:09 ` [PATCH 1/4] ARM: ux500: Provide a means to obtain the SMSC9115 clock when DT is enabled Linus Walleij

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=20130115235252.23734.21408@quantum \
    --to=mturquette@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).