From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/4] ARM: atmel: arm926ejs: fix clock configuration
Date: Tue, 17 Mar 2015 09:10:12 +0100 [thread overview]
Message-ID: <5507E164.5000401@denx.de> (raw)
In-Reply-To: <5507DE95.3010200@atmel.com>
Hello Bo,
Am 17.03.2015 08:58, schrieb Bo Shen:
> Hi Heiko,
>
> On 03/17/2015 03:45 PM, Heiko Schocher wrote:
>> Hello Bo,
>>
>> Am 13.03.2015 10:19, schrieb Bo Shen:
>>> Config MCKR according to the datasheet sequence, or else it
>>> will cause the MCKR configuration failed.
>>>
>>> Remove timeout checking for clock configuration, if configure
>>> the clock failed, let the system hang while not run in wrong
>>> clock configuration.
>>>
>>> Signed-off-by: Bo Shen <voice.shen@atmel.com>
>>> ---
>>>
>>> arch/arm/mach-at91/arm926ejs/clock.c | 54
>>> +++++++++++++++++++-----------------
>>> 1 file changed, 28 insertions(+), 26 deletions(-)
>>
>> Tested on the corvus and taurus board.
>>
>> Tested-by: Heiko Schocher <hs@denx.de>
>
> Thanks.
>
>>> diff --git a/arch/arm/mach-at91/arm926ejs/clock.c
>>> b/arch/arm/mach-at91/arm926ejs/clock.c
>>> index f363982..8d6934e 100644
>>> --- a/arch/arm/mach-at91/arm926ejs/clock.c
>>> +++ b/arch/arm/mach-at91/arm926ejs/clock.c
>>> @@ -195,50 +195,52 @@ int at91_clock_init(unsigned long main_clock)
>>> void at91_plla_init(u32 pllar)
>>> {
>>> struct at91_pmc *pmc = (struct at91_pmc *)ATMEL_BASE_PMC;
>>> - int timeout = AT91_PLL_LOCK_TIMEOUT;
>>>
>>> writel(pllar, &pmc->pllar);
>>> - while (!(readl(&pmc->sr) & (AT91_PMC_LOCKA | AT91_PMC_MCKRDY))) {
>>> - timeout--;
>>> - if (timeout == 0)
>>> - break;
>>> - }
>>> + while (!(readl(&pmc->sr) & AT91_PMC_LOCKA))
>>> + ;
>>
>> just hanging is maybe also bad ... could we hang with adding a
>>
>> if (timeout == 0) {
>> debug("could not set PLL(A|B)\n");
>> timeout = AT91_PLL_LOCK_TIMEOUT;
>> }
>>
>> Thinking about it ... have we setup here the debug uart already?
>> If not, forget my comment
>
> Yes the uart is not ready. And one more thing, if the clock is not setup correctly, then the system will run in abnormal status. So, I remove the timeout check here.
Ok, thanks!
bye,
Heiko
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2015-03-17 8:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 9:19 [U-Boot] [PATCH 0/4] ARM: atmel: boards: enable SPL support Bo Shen
2015-03-13 9:19 ` [U-Boot] [PATCH 1/4] ARM: atmel: arm926ejs: fix clock configuration Bo Shen
2015-03-17 7:45 ` Heiko Schocher
2015-03-17 7:58 ` Bo Shen
2015-03-17 8:10 ` Heiko Schocher [this message]
2015-03-13 9:19 ` [U-Boot] [PATCH 2/4] ARM: atmel: at91sam9m10g45ek: enable spl support Bo Shen
2015-03-13 9:34 ` Masahiro Yamada
2015-03-13 9:36 ` Bo Shen
2015-03-13 9:19 ` [U-Boot] [PATCH 3/4] ARM: atmel: at91sam9x5ek: " Bo Shen
2015-03-13 9:19 ` [U-Boot] [PATCH 4/4] ARM: atmel: at91sam9n12ek: " Bo Shen
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=5507E164.5000401@denx.de \
--to=hs@denx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.