From: Alban Bedel <alban.bedel@avionic-design.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: tegra: Use the IRAM for the early stack
Date: Mon, 9 Dec 2013 19:09:08 +0100 [thread overview]
Message-ID: <20131209190908.76a281e8@avionic-0020> (raw)
In-Reply-To: <52A5F95D.6020605@wwwdotorg.org>
On Mon, 09 Dec 2013 10:09:49 -0700
Stephen Warren <swarren@wwwdotorg.org> wrote:
> On 12/09/2013 10:06 AM, Alban Bedel wrote:
> > Unlike many other platforms the tegra platform has the luxury of
> > already having the SDRAM running during the early init, and it is used
> > for the early stack. However the memory test of the POST subsystem is
> > expecting the SDRAM to be unused, and on tegra platforms the test fail
> > to run as it destroy the stack.
> >
> > To fix the problem simply use the IRAM for the initial stack.
>
> Can't the POST code simply touch an unused RAM address?
The memtest is run pre-relocation to in fact avoid having to take care
about some special memory regions, beside the u-boot image and
pre-relocation code.
> There is IRAM content that needs to be preserved, so we need to make
> sure we don't stomp on that. Examples are:
>
> * BIT (Boot Information Table)
> * BCT that was used to boot the system
> * Perhaps the whole IRAM is filled with code/data in the LP0
> suspend/resume case.
BIC and BCT shouldn't be problem if enough IRAM is left for the
relocation. After relocation the stack move to the SDRAM anyway.
But for LP0 I don't really understand what the problem would be. Do the
u-boot loading+relocation needs to be run when comming out of LP0?
Alban
next prev parent reply other threads:[~2013-12-09 18:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 17:06 [U-Boot] [PATCH] ARM: tegra: Use the IRAM for the early stack Alban Bedel
2013-12-09 17:09 ` Stephen Warren
2013-12-09 18:09 ` Alban Bedel [this message]
2013-12-09 18:16 ` 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=20131209190908.76a281e8@avionic-0020 \
--to=alban.bedel@avionic-design.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.