public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/3] sunxi: sun4i: improve cpu clock selection method
Date: Sun, 29 Mar 2015 14:39:56 +0200	[thread overview]
Message-ID: <5517F29C.2070005@redhat.com> (raw)
In-Reply-To: <55168198.5030207@gmail.com>

Hi,

On 28-03-15 11:25, Iain Paton wrote:
> clock_set_pll1 would pick the next highest available cpu clock speed if
> a value not in the pre defined table was selected. this potentially
> results in overclocking the soc.
>
> reverse the selection method so that we select the next lowest speed
> and add the missing 912Mhz setting that's requested by sun7i which also
> uses the sun4i clock code.
>
> Signed-off-by: Iain Paton <ipaton0@gmail.com>

Thanks for the new set.

I've found one small issue with the second patch:
"sunxi: use CONFIG_SYS_CLK_FREQ to set cpu clock"

sun7i.h contained the following:

#define CONFIG_SYS_CLK_FREQ		24000000
#define CONFIG_TIMER_CLK_FREQ		CONFIG_SYS_CLK_FREQ

Which is a conflicting usage of CONFIG_SYS_CLK_FREQ compared to the new
usage introduced by your patch. I've fixed this by changing the above
to:

#define CONFIG_TIMER_CLK_FREQ		24000000

And run some compile and runtime tests.

Everything builds and works fine with this change added, so I've pushed
these 3 commits + one other fix to: u-boot-sunxi/master

And I will send out a pull-req shortly to get these fixes included into
the upcoming u-boot v2015.04 release.

Regards,

Hans


> ---
>   arch/arm/cpu/armv7/sunxi/clock_sun4i.c | 35 ++++++++++++++++++----------------
>   1 file changed, 19 insertions(+), 16 deletions(-)
>
> diff --git a/arch/arm/cpu/armv7/sunxi/clock_sun4i.c b/arch/arm/cpu/armv7/sunxi/clock_sun4i.c
> index 49f4032..c3e04af 100644
> --- a/arch/arm/cpu/armv7/sunxi/clock_sun4i.c
> +++ b/arch/arm/cpu/armv7/sunxi/clock_sun4i.c
> @@ -100,22 +100,23 @@ static struct {
>   	unsigned int freq;
>   } pll1_para[] = {
>   	/* This array must be ordered by frequency. */
> -	{ PLL1_CFG(16, 0, 0, 0), 384000000 },
> -	{ PLL1_CFG(16, 1, 0, 0), 768000000 },
> -	{ PLL1_CFG(20, 1, 0, 0), 960000000 },
> -	{ PLL1_CFG(21, 1, 0, 0), 1008000000},
> -	{ PLL1_CFG(22, 1, 0, 0), 1056000000},
> -	{ PLL1_CFG(23, 1, 0, 0), 1104000000},
> -	{ PLL1_CFG(24, 1, 0, 0), 1152000000},
> -	{ PLL1_CFG(25, 1, 0, 0), 1200000000},
> -	{ PLL1_CFG(26, 1, 0, 0), 1248000000},
> -	{ PLL1_CFG(27, 1, 0, 0), 1296000000},
> -	{ PLL1_CFG(28, 1, 0, 0), 1344000000},
> -	{ PLL1_CFG(29, 1, 0, 0), 1392000000},
> -	{ PLL1_CFG(30, 1, 0, 0), 1440000000},
>   	{ PLL1_CFG(31, 1, 0, 0), 1488000000},
> -	/* Final catchall entry */
> -	{ PLL1_CFG(31, 1, 0, 0), ~0},
> +	{ PLL1_CFG(30, 1, 0, 0), 1440000000},
> +	{ PLL1_CFG(29, 1, 0, 0), 1392000000},
> +	{ PLL1_CFG(28, 1, 0, 0), 1344000000},
> +	{ PLL1_CFG(27, 1, 0, 0), 1296000000},
> +	{ PLL1_CFG(26, 1, 0, 0), 1248000000},
> +	{ PLL1_CFG(25, 1, 0, 0), 1200000000},
> +	{ PLL1_CFG(24, 1, 0, 0), 1152000000},
> +	{ PLL1_CFG(23, 1, 0, 0), 1104000000},
> +	{ PLL1_CFG(22, 1, 0, 0), 1056000000},
> +	{ PLL1_CFG(21, 1, 0, 0), 1008000000},
> +	{ PLL1_CFG(20, 1, 0, 0), 960000000 },
> +	{ PLL1_CFG(19, 1, 0, 0), 912000000 },
> +	{ PLL1_CFG(16, 1, 0, 0), 768000000 },
> +	/* Final catchall entry 384MHz*/
> +	{ PLL1_CFG(16, 0, 0, 0), 0 },
> +
>   };
>
>   void clock_set_pll1(unsigned int hz)
> @@ -126,10 +127,12 @@ void clock_set_pll1(unsigned int hz)
>   		(struct sunxi_ccm_reg *)SUNXI_CCM_BASE;
>
>   	/* Find target frequency */
> -	while (pll1_para[i].freq < hz)
> +	while (pll1_para[i].freq > hz)
>   		i++;
>
>   	hz = pll1_para[i].freq;
> +	if (! hz)
> +		hz = 384000000;
>
>   	/* Calculate system clock divisors */
>   	axi = DIV_ROUND_UP(hz, 432000000);	/* Max 450MHz */
>

  reply	other threads:[~2015-03-29 12:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-28 10:25 [U-Boot] [PATCH v2 1/3] sunxi: sun4i: improve cpu clock selection method Iain Paton
2015-03-29 12:39 ` Hans de Goede [this message]
2015-03-30  7:52   ` Iain Paton
2015-03-30  8:49     ` Hans de Goede

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=5517F29C.2070005@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=u-boot@lists.denx.de \
    /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