From: Iain Paton <ipaton0@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/3] sunxi: sun4i: improve cpu clock selection method
Date: Mon, 30 Mar 2015 08:52:02 +0100 [thread overview]
Message-ID: <551900A2.3000905@gmail.com> (raw)
In-Reply-To: <5517F29C.2070005@redhat.com>
On 29/03/15 13:39, Hans de Goede wrote:
> 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
Apologies for missing that. Thanks for the fixup.
Did you see any compile or runtime errors?
I definately did build and boot the result several times before sending it,
especially to verify the behaviour of the first patch.
So I'm curious as to how I missed it and you found the issue.
Rgds,
Iain
next prev parent reply other threads:[~2015-03-30 7:52 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
2015-03-30 7:52 ` Iain Paton [this message]
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=551900A2.3000905@gmail.com \
--to=ipaton0@gmail.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