Re: [PATCH] cpufreq: imx6q: Fix clock enable balance

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Aug 26, 2013 at 01:48:36PM +0200, Sascha Hauer wrote:
> For changing the cpu frequency the i.MX6q has to be switched to some
> intermediate clock during the PLL reprogramming. The driver tries
> to be clever to keep the enable count correct but gets it wrong. If
> the cpufreq is increased it calls clk_disable_unprepare twice
> on pll2_pfd2_396m. This puts all other devices which get their clock
> from pll2_pfd2_396m into a nonworking state.

So you're running into a problem in real?  The clk_disable_unprepare on
pll2_pfd2_396m below will only be executed when are leaving 396MHz
set-point.  It's there to balance the clk_prepare_enable on
pll2_pfd2_396m when we enters 396MHz set-point.

	if (freqs.old * 1000 <= clk_get_rate(pll2_pfd2_396m_clk)) {
		clk_prepare_enable(pll1_sys_clk);
		clk_disable_unprepare(pll2_pfd2_396m_clk);
	}

> 
> Fix this by removing the clk enabling/disabling altogether since the
> clk core will do this automatically during a reparent.

It seems clk core will only enable the parent clock during the
clk_set_parent() call, and only in case that the child clock is
prepared.  For example, I do not think pll2_pfd2_396m_clk and step_clk
will be altered to ON state.  Or am I missing something?

	clk_set_parent(step_clk, pll2_pfd2_396m_clk);
	clk_set_parent(pll1_sw_clk, step_clk);

Shawn

> 
> Signed-off-by: Sascha Hauer <s.hauer@xxxxxxxxxxxxxx>
> ---
>  drivers/cpufreq/imx6q-cpufreq.c | 17 -----------------
>  1 file changed, 17 deletions(-)
> 
> diff --git a/drivers/cpufreq/imx6q-cpufreq.c b/drivers/cpufreq/imx6q-cpufreq.c
> index e37cdae..2971d12 100644
> --- a/drivers/cpufreq/imx6q-cpufreq.c
> +++ b/drivers/cpufreq/imx6q-cpufreq.c
> @@ -117,28 +117,11 @@ static int imx6q_set_target(struct cpufreq_policy *policy,
>  	 *  - Reprogram pll1_sys_clk and reparent pll1_sw_clk back to it
>  	 *  - Disable pll2_pfd2_396m_clk
>  	 */
> -	clk_prepare_enable(pll2_pfd2_396m_clk);
>  	clk_set_parent(step_clk, pll2_pfd2_396m_clk);
>  	clk_set_parent(pll1_sw_clk, step_clk);
>  	if (freq_hz > clk_get_rate(pll2_pfd2_396m_clk)) {
>  		clk_set_rate(pll1_sys_clk, freqs.new * 1000);
> -		/*
> -		 * If we are leaving 396 MHz set-point, we need to enable
> -		 * pll1_sys_clk and disable pll2_pfd2_396m_clk to keep
> -		 * their use count correct.
> -		 */
> -		if (freqs.old * 1000 <= clk_get_rate(pll2_pfd2_396m_clk)) {
> -			clk_prepare_enable(pll1_sys_clk);
> -			clk_disable_unprepare(pll2_pfd2_396m_clk);
> -		}
>  		clk_set_parent(pll1_sw_clk, pll1_sys_clk);
> -		clk_disable_unprepare(pll2_pfd2_396m_clk);
> -	} else {
> -		/*
> -		 * Disable pll1_sys_clk if pll2_pfd2_396m_clk is sufficient
> -		 * to provide the frequency.
> -		 */
> -		clk_disable_unprepare(pll1_sys_clk);
>  	}
>  
>  	/* Ensure the arm clock divider is what we expect */
> -- 
> 1.8.4.rc3
> 

--
To unsubscribe from this list: send the line "unsubscribe cpufreq" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel Devel]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Forum]     [Linux SCSI]

  Powered by Linux