public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 4/8] orion5x: Allow SDRAM initialization to be omitted
Date: Sat, 29 Jan 2011 08:36:03 +0100	[thread overview]
Message-ID: <4D43C363.30604@free.fr> (raw)
In-Reply-To: <1296262841-8819-4-git-send-email-mspang@csclub.uwaterloo.ca>

Le 29/01/2011 02:00, Michael Spang a ?crit :
> For the TS-7800, the FPGA contains a bootloader which handles
> the SDRAM initialization and loads a bootloader from RAM. We
> should not try to initialize RAM again while running from it.
>
> Signed-off-by: Michael Spang<mspang@csclub.uwaterloo.ca>
> ---
>   arch/arm/cpu/arm926ejs/orion5x/lowlevel_init.S |    4 ++++
>   1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/cpu/arm926ejs/orion5x/lowlevel_init.S b/arch/arm/cpu/arm926ejs/orion5x/lowlevel_init.S
> index 0523bd4..37d7d14 100644
> --- a/arch/arm/cpu/arm926ejs/orion5x/lowlevel_init.S
> +++ b/arch/arm/cpu/arm926ejs/orion5x/lowlevel_init.S
> @@ -86,6 +86,8 @@
>
>   lowlevel_init:
>
> +#ifndef CONFIG_SKIP_SDRAM_INIT
> +
>   	/* Use 'r4 as the base for internal register accesses */
>   	ldr	r4, =ORION5X_REGS_PHY_BASE
>
> @@ -289,5 +291,7 @@ lowlevel_init:
>   	orr	r2, r2, r6
>   	str	r2, [r3, #0x484]
>
> +#endif
> +
>   	/* Return to U-boot via saved link register */
>   	mov	pc, lr

That's basically making lowlevel_init empty, so I would prefer that you 
put #ifdef/#endif around the call to lowlevel_init in start.S and modify 
the orion5x Makefile to include lowlevel_init.S only if 
CONFIG_SKIP_DRAM_INIT is not defined.

(come to think of it, CONFIG_SKIP_LOWLEVEL_INIT is a bit of a misnomer 
since it actually skips not only lowlevelinit but also cpu_init_crit. 
Possibly one could even go as far as renaming CONFIG_SKIP_LOWLEVEL_INIT 
to CONFIG_SKIP_CPU_INIT_CRIT, and then reuse CONFIG_SKIP_LOWLEVEL_INIT 
for lowlevel_init; but that can be a separate patch, with a nifty doc 
update.)

Amicalement,
-- 
Albert.

  reply	other threads:[~2011-01-29  7:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-29  1:00 [U-Boot] [PATCH 1/8] arm926ej-s: Invalidate instruction cache in flush_cache Michael Spang
2011-01-29  1:00 ` [U-Boot] [PATCH 2/8] orion5x: Fix wrong address in orion5x_sdram_bar Michael Spang
2011-01-29  7:24   ` Albert ARIBAUD
2011-03-17 19:47     ` Michael Spang
2011-03-18  5:57     ` Rogan Dawes
2011-03-18  6:46       ` Michael Spang
2011-01-29  1:00 ` [U-Boot] [PATCH 3/8] orion5x: Increase maximum bank size to 128M Michael Spang
2011-01-29  7:26   ` Albert ARIBAUD
2011-01-29  1:00 ` [U-Boot] [PATCH 4/8] orion5x: Allow SDRAM initialization to be omitted Michael Spang
2011-01-29  7:36   ` Albert ARIBAUD [this message]
2011-03-17 19:52     ` Michael Spang
2011-01-29  1:00 ` [U-Boot] [PATCH 5/8] mvgbe: Support preserving the existing MAC address Michael Spang
2011-01-29  1:00 ` [U-Boot] [PATCH 6/8] Add board support for TS-7800 Michael Spang
2011-01-29  7:39   ` Albert ARIBAUD
2011-03-17 19:50     ` Michael Spang
2011-01-30 19:14   ` Wolfgang Denk
2011-01-29  1:00 ` [U-Boot] [PATCH 7/8] Add NAND " Michael Spang
2011-01-30 19:15   ` Wolfgang Denk
2011-01-29  1:00 ` [U-Boot] [PATCH 8/8] Add README " Michael Spang

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=4D43C363.30604@free.fr \
    --to=albert.aribaud@free.fr \
    --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