From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] clk: shmobile: rcar-gen2: Use kick bit to allow Z clock frequency change
Date: Tue, 25 Feb 2014 15:59:49 +0000 [thread overview]
Message-ID: <4429829.M2ek0hcn2h@avalon> (raw)
In-Reply-To: <530C9D2A.8030409@baylibre.com>
Hi Benoit,
Thank you for the patch.
On Tuesday 25 February 2014 14:39:54 Benoit Cousson wrote:
> The Z clock frequency change is effective only after setting the kick
> bit located in the FRQCRB register.
> Without that, the CA15 CPUs clock rate will never change.
>
> Fix that by checking if the kick bit is cleared and enable it to make
> the clock rate change effective. The bit is cleared automatically upon
> completion.
>
> Note: The kick bit is used as well to change 3 other emulation clocks:
> Debug Trace port clock (ZTR), Debug Trace bus clock (ZT), and Debug
> clock (ZTRD2). It is not clear from the spec [1] if there
> is any relation between the CPU clock rate and these emulation clocks.
> Moreover, these clocks are probably supposed to be controled by an
> external debugger / tracer like Lauterbach PowerTrace.
> For all these reasons, the current implementation does not expose these
> clock nodes and thus does not have to consider the multiple accesses
> to the kick bit.
>
> Signed-off-by: Benoit Cousson <bcousson+renesas@baylibre.com>
> Cc: Mike Turquette <mturquette@linaro.org>
> Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
>
> [1] R-Car-H2-v0.6-en.pdf - page 186
> ---
>
> Salut Laurent,
>
> If you have any information about these emulation clocks, please let me
> know.
I don't I'm afraid. All I know is that we don't use them for now, so I
wouldn't care :-)
> Moreover, the CCF clock driver is shared with the r8a7791, so a test on
> that platform will be good.
I can do that. I assume you're working on Lager then ?
How can I exercise the code ? Using cpufreq to change the CA15 clock frequency
? A brief test procedure would be appreciated.
> drivers/clk/shmobile/clk-rcar-gen2.c | 26 ++++++++++++++++++++++++--
> 1 file changed, 24 insertions(+), 2 deletions(-)
By the way the patch was corrupted with line wraps and additional spaces.
> diff --git a/drivers/clk/shmobile/clk-rcar-gen2.c
> b/drivers/clk/shmobile/clk-rcar-gen2.c
> index a59ec21..9f12746 100644
> --- a/drivers/clk/shmobile/clk-rcar-gen2.c
> +++ b/drivers/clk/shmobile/clk-rcar-gen2.c
> @@ -26,6 +26,8 @@ struct rcar_gen2_cpg {
> void __iomem *reg;
> };
>
> +#define CPG_FRQCRB 0x00000004
> +#define CPG_FRQCRB_KICK BIT(31)
> #define CPG_SDCKCR 0x00000074
> #define CPG_PLL0CR 0x000000d8
> #define CPG_FRQCRC 0x000000e0
> @@ -45,6 +47,7 @@ struct rcar_gen2_cpg {
> struct cpg_z_clk {
> struct clk_hw hw;
> void __iomem *reg;
> + void __iomem *kick_reg;
> };
>
> #define to_z_clk(_hw) container_of(_hw, struct cpg_z_clk, hw)
> @@ -83,17 +86,35 @@ static int cpg_z_clk_set_rate(struct clk_hw *hw,
> unsigned long rate,
> {
> struct cpg_z_clk *zclk = to_z_clk(hw);
> unsigned int mult;
> - u32 val;
> + u32 val, kick;
> + int i;
The loop counter will always be positive, please use an unsigned int.
>
> mult = div_u64((u64)rate * 32, parent_rate);
> mult = clamp(mult, 1U, 32U);
>
> + if (clk_readl(zclk->kick_reg) & CPG_FRQCRB_KICK)
> + return -EBUSY;
> +
> val = clk_readl(zclk->reg);
> val &= ~CPG_FRQCRC_ZFC_MASK;
> val |= (32 - mult) << CPG_FRQCRC_ZFC_SHIFT;
> clk_writel(val, zclk->reg);
>
> - return 0;
> + /*
> + * Set KICK bit in FRQCRB to update hardware setting and
> + * wait for completion.
> + */
> + kick = clk_readl(zclk->kick_reg);
> + kick |= CPG_FRQCRB_KICK;
> + clk_writel(kick, zclk->kick_reg);
Does CCF guarantee that two set_rate calls for different clocks will not occur
concurrently ? If so a brief comment would be nice. Otherwise we need a lock
around this.
> +
> + for (i = 1000; i; i--)
> + if (clk_readl(zclk->kick_reg) & CPG_FRQCRB_KICK)
> + cpu_relax();
> + else
> + return 0;
Please put braces around the for() content.
How many iterations does this need in practice ? I also wonder if we really
need to wait or if we could just return and assume the clock frequency will
change soon enough.
> +
> + return -ETIMEDOUT;
> }
>
> static const struct clk_ops cpg_z_clk_ops = {
> @@ -120,6 +141,7 @@ static struct clk * __init cpg_z_clk_register(struct
> rcar_gen2_cpg *cpg)
> init.num_parents = 1;
>
> zclk->reg = cpg->reg + CPG_FRQCRC;
> + zclk->kick_reg = cpg->reg + CPG_FRQCRB;
> zclk->hw.init = &init;
>
> clk = clk_register(NULL, &zclk->hw);
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-02-25 15:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 13:39 [PATCH] clk: shmobile: rcar-gen2: Use kick bit to allow Z clock frequency change Benoit Cousson
2014-02-25 15:59 ` Laurent Pinchart [this message]
2014-02-25 17:07 ` Benoit Cousson
2014-02-25 17:48 ` Laurent Pinchart
2014-02-26 20:54 ` Mike Turquette
2014-02-26 21:53 ` Laurent Pinchart
2014-02-27 0:50 ` Stephen Boyd
2014-02-27 22:46 ` Laurent Pinchart
2014-02-28 0:03 ` Stephen Boyd
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=4429829.M2ek0hcn2h@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-sh@vger.kernel.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).