From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: ux500: Remove BML8580 clock
Date: Thu, 15 Aug 2013 11:42:02 -0700 [thread overview]
Message-ID: <20130815184202.4443.33356@quantum> (raw)
In-Reply-To: <1376257756-23575-1-git-send-email-linus.walleij@linaro.org>
Quoting Linus Walleij (2013-08-11 14:49:16)
> From: Lee Jones <lee.jones@linaro.org>
>
> There is no mention of the PRCMU_BML8580CLK in any of the Design
> Specifications for the chips supported in Mainline. In fact, where it
> is incorrectly used in the u8540 clock definition driver it would
> have the side effect of using the incorrect clock management address
> ([PRCM_BML8580CLK_MGT] 0x108 instead of the correct value 0x04C).
>
> Signed-off-by: Lee Jones <lee.jones@linaro.org>
Pulled into clk-next.
Thanks,
Mike
> ---
> drivers/clk/ux500/u8540_clk.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/clk/ux500/u8540_clk.c b/drivers/clk/ux500/u8540_clk.c
> index f262588..20c8add 100644
> --- a/drivers/clk/ux500/u8540_clk.c
> +++ b/drivers/clk/ux500/u8540_clk.c
> @@ -83,7 +83,7 @@ void u8540_clk_init(u32 clkrst1_base, u32 clkrst2_base, u32 clkrst3_base,
> clk_register_clkdev(clk, NULL, "lcd");
> clk_register_clkdev(clk, "lcd", "mcde");
>
> - clk = clk_reg_prcmu_opp_gate("bmlclk", NULL, PRCMU_BML8580CLK,
> + clk = clk_reg_prcmu_opp_gate("bmlclk", NULL, PRCMU_BMLCLK,
> CLK_IS_ROOT);
> clk_register_clkdev(clk, NULL, "bml");
>
> --
> 1.8.1.4
next prev parent reply other threads:[~2013-08-15 18:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-11 21:49 [PATCH] clk: ux500: Remove BML8580 clock Linus Walleij
2013-08-15 18:42 ` Mike Turquette [this message]
2013-08-16 9:15 ` Linus Walleij
2013-08-16 19:09 ` 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=20130815184202.4443.33356@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 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.