From: Tom <Tom.Rix@windriver.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] MX51: Moved board specific values in config file
Date: Sat, 27 Mar 2010 15:14:11 -0500 [thread overview]
Message-ID: <4BAE6713.2060501@windriver.com> (raw)
In-Reply-To: <4BA87ED4.1020002@denx.de>
Stefano Babic wrote:
> Tom wrote:
>> Stefano Babic wrote:
>>> The lowlevel_init file contained some hard-coded values
>>> to setup the RAM. These board related values are moved into
>>> the board configuration file.
>> Why was only one value cleaned up?
>> Just from the patch, there are at least 4 more.
>
> Well, I prefer do not move a lot of configuration values inside the
> board config file and add only what it is really needed and when it is
> needed.
>
> The fixed values you have seen set the CCM in a known status before
> updating it to the final value, and this procedure should be the same
> for all boards, as I undestood from Freescale's doc.
>
> The patch adds configuration values to select the clock for DDR and the
> value of the related divider, and both depends on the board implementation.
>
>>> + orr r1,r1,#CONFIG_SYS_DDR_CLKSEL
>
> I'll fix it, thanks.
>
>> git am complains about the leading space
>> Please remove
>>> str r1, [r0, #CLKCTL_CBCMR]
>>> ldr r1, =0x13239145
>>> str r1, [r0, #CLKCTL_CBCDR]
>>> @@ -171,6 +172,7 @@
>>> ldr r1, =0x19239145
>>> str r1, [r0, #CLKCTL_CBCDR]
>>> ldr r1, =0x000020C0
>>> + orr r1,r1,#CONFIG_SYS_DDR_CLKSEL
>> This is a noop as it is defined as 0.
>> Is the value going to change ?
>
> That is correct. The value selects which clock must be used for the DDR.
> On the mx51evk, this value must be set to 0. However, I know already
> another target that uses another clock source for the RAM.
>
That is a good reason.
Just a cleanup is needed
Tom
> Stefano
>
next prev parent reply other threads:[~2010-03-27 20:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 16:23 [U-Boot] [PATCH] MX51: Moved board specific values in config file Stefano Babic
2010-03-21 0:25 ` Tom
2010-03-23 8:41 ` Stefano Babic
2010-03-27 20:14 ` Tom [this message]
2010-03-28 11:43 ` [U-Boot] [PATCH V2] " Stefano Babic
2010-04-23 10:06 ` Liu Hui-R64343
2010-04-23 12:25 ` Stefano Babic
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=4BAE6713.2060501@windriver.com \
--to=tom.rix@windriver.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