From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: tegra: Use mem size from MC rather than ODMDATA
Date: Wed, 02 Jul 2014 15:53:51 -0600 [thread overview]
Message-ID: <53B47F6F.1090405@wwwdotorg.org> (raw)
In-Reply-To: <20140702211821.3EFF6380185@gemini.denx.de>
On 07/02/2014 03:18 PM, Wolfgang Denk wrote:
> Dear Stephen Warren,
>
> In message <1404331950-4916-1-git-send-email-swarren@wwwdotorg.org> you wrote:
>>
>> In at least Tegra124, the Tegra memory controller (MC) has a register
>> that controls the memory size. Read this to determine the memory size
>> rather than requiring this to be redundantly encoded into the ODMDATA.
>> This way, changes to the BCT (i.e. MC configuration) automatically
>> updated SW's view of the memory size, without requiring manual changes
>> to the ODMDATA.
>
> Is there a specific reason for not using get_ram_size()?
Since we know the exact RAM size, we may as well simply use it directly
rather than "probing" for it.
I know that if non-existent peripheral addresses are accessed by the
CPU, the CPU or some bus hangs. I'm not sure if the same applies to
addresses within the memory window where there is not actually RAM
present on a particular board, but I'd rather not risk it by touching
them during probing.
BTW, I'm out on vacation starting tomorrow, so may not respond soon.
next prev parent reply other threads:[~2014-07-02 21:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 20:12 [U-Boot] [PATCH] ARM: tegra: Use mem size from MC rather than ODMDATA Stephen Warren
2014-07-02 21:18 ` Wolfgang Denk
2014-07-02 21:53 ` Stephen Warren [this message]
2014-07-03 7:45 ` Wolfgang Denk
2014-07-03 11:01 ` Tom Rini
2014-07-24 21:00 ` Stephen Warren
2014-07-31 19:45 ` Stephen Warren
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=53B47F6F.1090405@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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