U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] am33xx, spl, siemens: enable debug uart output again
Date: Mon, 2 Mar 2015 08:59:32 -0500	[thread overview]
Message-ID: <20150302135932.GJ29891@bill-the-cat> (raw)
In-Reply-To: <54F409A9.7030907@denx.de>

On Mon, Mar 02, 2015 at 07:56:41AM +0100, Heiko Schocher wrote:
> Hello Simon,
> 
> Am 24.02.2015 14:31, schrieb Simon Glass:
> >Hi Heiko,
> >
> >On 23 February 2015 at 23:18, Heiko Schocher <hs@denx.de> wrote:
> >>a6b541b090: TI ARMv7: Don't use GD before crt0.S has set it
> >>
> >>moves the init of the debug uart at the very end of SPL code.
> >>Enable it for the siemens board earlier, as they print
> >>ddr settings ... all debug output before board_init_r()
> >>is here currently useless. Maybe we must rework this
> >>globally?
> >
> >Assuming we are talking about U-Boot proper, the DDR init should
> >happen in board_init_f(), specifically dram_init(). so I think this
> >code should be updated.
> >
> >If it is SPL, then DDR init should happen in SPL's board_init_f().
> 
> It is in SPL...
> 
> sdram_init() is called from:
> 
> ./arch/arm/cpu/armv7/am33xx/board.c from s_init() ...
> 
> >I sent a series a few weeks ago (available at u-boot-dm branch
> >spl-working) related to this topic:
> >
> >http://patchwork.ozlabs.org/patch/438581/
> 
> Ah ... Hmm... so "./arch/arm/cpu/armv7/am33xx/board.c" needs
> a rework, right?
> 
> Is a simple rename s_init() -> board_init_f() correct?

Right so, no, we can't just rename s_init to board_init_f.  This is what
I was talking about in the thread about the function Hans wants to add
to enable some bits in CP15 on sunxi, iirc.

In short, armv7 has a different set of abstraction hooks than the
previous ARM cores (armv8 followed what we have for v7) and I'm not
convinced in the end that it really won us anything.  See
http://lists.denx.de/pipermail/u-boot/2015-January/202350.html

For today you need to rework the Siemens code to print out the DDR
values (when desired) in spl_board_init() as we do not, or will not
shortly, have gd prior to board_init_f running.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150302/a64f3d60/attachment.sig>

  reply	other threads:[~2015-03-02 13:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-24  6:18 [U-Boot] [PATCH] am33xx, spl, siemens: enable debug uart output again Heiko Schocher
2015-02-24 13:31 ` Simon Glass
2015-03-02  6:56   ` Heiko Schocher
2015-03-02 13:59     ` Tom Rini [this message]
2015-03-04  7:42       ` Heiko Schocher
2015-03-04 16:40         ` Tom Rini
2015-03-05  6:22           ` Heiko Schocher
2015-03-05  8:46             ` Heiko Schocher
2015-03-05 14:50               ` Tom Rini
2015-03-06  7:24                 ` Heiko Schocher
2015-03-06 12:15                   ` Tom Rini
2015-05-14 10:37                   ` Heiko Schocher
2015-05-14 10:51                     ` Tom Rini
2015-05-14 12:46                       ` Simon Glass
2015-05-15  5:23                         ` Heiko Schocher

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=20150302135932.GJ29891@bill-the-cat \
    --to=trini@konsulko.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