From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: spear600: Fix adc clock device name
Date: Wed, 2 Sep 2015 16:32:13 +0530 [thread overview]
Message-ID: <20150902110213.GD26744@linux> (raw)
In-Reply-To: <1441190517-20235-1-git-send-email-sr@denx.de>
On 02-09-15, 12:41, Stefan Roese wrote:
> The device name for the adc clock is incorrect. This results in the
> IIO ADC driver to fail while probing for the clock. This patch
> fixes the name and the ADC driver is now started correctly.
>
> Signed-off-by: Stefan Roese <sr@denx.de>
> Cc: Vipul Kumar Samar <vipulkumar.samar@st.com>
> Cc: Viresh Kumar <viresh.kumar@linaro.org>
> Cc: Mike Turquette <mturquette@linaro.org>
> ---
> drivers/clk/spear/spear6xx_clock.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/clk/spear/spear6xx_clock.c b/drivers/clk/spear/spear6xx_clock.c
> index 4f649c9..3e43244 100644
> --- a/drivers/clk/spear/spear6xx_clock.c
> +++ b/drivers/clk/spear/spear6xx_clock.c
> @@ -316,7 +316,7 @@ void __init spear6xx_clk_init(void __iomem *misc_base)
> /* clock derived from apb clk */
> clk = clk_register_gate(NULL, "adc_clk", "apb_clk", 0, PERIP1_CLK_ENB,
> ADC_CLK_ENB, 0, &_lock);
> - clk_register_clkdev(clk, NULL, "adc");
> + clk_register_clkdev(clk, NULL, "d8200000.adc");
>
> clk = clk_register_fixed_factor(NULL, "gpio0_clk", "apb_clk", 0, 1, 1);
> clk_register_clkdev(clk, NULL, "f0100000.gpio");
Sigh. Its fixed for all other boards, but this.
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
--
viresh
next prev parent reply other threads:[~2015-09-02 11:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 10:41 [PATCH] clk: spear600: Fix adc clock device name Stefan Roese
2015-09-02 11:02 ` Viresh Kumar [this message]
2015-09-02 11:03 ` Viresh Kumar
-- strict thread matches above, loose matches on Subject: below --
2015-03-19 13:34 Stefan Roese
2015-04-11 0:58 ` Michael 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=20150902110213.GD26744@linux \
--to=viresh.kumar@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).