From: Simon Horman <horms@verge.net.au>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-sh@vger.kernel.org, Magnus Damm <magnus.damm@gmail.com>,
linux-arm-kernel@lists.infradead.org,
"Rafael J. Wysocki" <rjw@sisk.pl>,
cpufreq@vger.kernel.org
Subject: Re: [PATCH v3 1/3] ARM: shmobile: sh73a0: wait for completion when kicking the clock
Date: Fri, 1 Mar 2013 11:52:25 +0900 [thread overview]
Message-ID: <20130301025222.GA32306@verge.net.au> (raw)
In-Reply-To: <1362054120-8600-2-git-send-email-g.liakhovetski@gmx.de>
On Thu, Feb 28, 2013 at 01:21:58PM +0100, Guennadi Liakhovetski wrote:
> To reconfigure clocks, controlled by FRQCRA and FRQCRB, a kick bit has to
> be set and to make sure the setting has taken effect, it has to be read
> back repeatedly until it is cleared by the hardware. This patch adds the
> waiting part, that was missing until now.
>
> Signed-off-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
This patch seems to be ready to be applied.
Magnus, could I get a review from you?
> ---
>
> As noted in patch 0/3, this patch affects existing systems, but AFAICS
> only theoretically - so far nobody is changing clock rates of any of the
> FRQCRA and FRQCRB clocks. Still, please, handle with care.
>
> arch/arm/mach-shmobile/clock-sh73a0.c | 23 +++++++++++++++++------
> 1 files changed, 17 insertions(+), 6 deletions(-)
>
> diff --git a/arch/arm/mach-shmobile/clock-sh73a0.c b/arch/arm/mach-shmobile/clock-sh73a0.c
> index 71843dd..34b5c5a 100644
> --- a/arch/arm/mach-shmobile/clock-sh73a0.c
> +++ b/arch/arm/mach-shmobile/clock-sh73a0.c
> @@ -21,6 +21,7 @@
> #include <linux/io.h>
> #include <linux/sh_clk.h>
> #include <linux/clkdev.h>
> +#include <asm/processor.h>
> #include <mach/common.h>
>
> #define FRQCRA IOMEM(0xe6150000)
> @@ -234,14 +235,24 @@ static struct clk *main_clks[] = {
> &sh73a0_extalr_clk,
> };
>
> -static void div4_kick(struct clk *clk)
> +static int frqcr_kick(void)
> {
> - unsigned long value;
> + int i;
> +
> + /* set KICK bit in FRQCRB to update hardware setting, check success */
> + __raw_writel(__raw_readl(FRQCRB) | (1 << 31), FRQCRB);
> + for (i = 1000; i; i--)
> + if (__raw_readl(FRQCRB) & (1 << 31))
> + cpu_relax();
> + else
> + return i;
> +
> + return -ETIMEDOUT;
> +}
>
> - /* set KICK bit in FRQCRB to update hardware setting */
> - value = __raw_readl(FRQCRB);
> - value |= (1 << 31);
> - __raw_writel(value, FRQCRB);
> +static void div4_kick(struct clk *clk)
> +{
> + frqcr_kick();
> }
>
> static int divisors[] = { 2, 3, 4, 6, 8, 12, 16, 18,
> --
> 1.7.2.5
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-sh" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2013-03-01 2:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 12:21 [PATCH v3 0/3] CPUFreq for kzm9g Guennadi Liakhovetski
2013-02-28 12:21 ` [PATCH v3 1/3] ARM: shmobile: sh73a0: wait for completion when kicking the clock Guennadi Liakhovetski
2013-03-01 2:52 ` Simon Horman [this message]
2013-03-19 3:42 ` Simon Horman
2013-03-19 5:15 ` Magnus Damm
2013-03-21 13:25 ` Simon Horman
2013-02-28 12:21 ` [PATCH/RFC v3 2/3] ARM: shmobile: sh73a0: add support for adjusting CPU frequency Guennadi Liakhovetski
2013-02-28 12:22 ` [PATCH/RFC v3 3/3] ARM: shmobile: kzm9g-reference: add CPUFreq support Guennadi Liakhovetski
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=20130301025222.GA32306@verge.net.au \
--to=horms@verge.net.au \
--cc=cpufreq@vger.kernel.org \
--cc=g.liakhovetski@gmx.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=rjw@sisk.pl \
/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