From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] spl: add a new stub spl_early_board_init() for early SoC-specific setup
Date: Tue, 8 Mar 2016 18:23:02 -0500 [thread overview]
Message-ID: <20160308232302.GV23166@bill-the-cat> (raw)
In-Reply-To: <1457437036-22938-1-git-send-email-yamada.masahiro@socionext.com>
On Tue, Mar 08, 2016 at 08:37:16PM +0900, Masahiro Yamada wrote:
> We are generally supposed to implement SoC/board-specific SPL init
> code in spl_board_init(), but it is called after spl_init() where the
> FDT is setup and devices are bound.
>
> This new stub spl_early_board_init() would be useful to put something
> really SoC-specific, for example, debug_uart_init().
>
> In fact, I was hit by some problems on FDT setup when I was tackling
> on a completely new platform. I wished I could use the debug UART
> earlier in situations like that.
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
This is usually done with s_init() and uniphier opts out of that. I
would conceed however that things could use some further clean-up and
organization here.
--
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/20160308/3f70b5a7/attachment.sig>
next prev parent reply other threads:[~2016-03-08 23:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 11:37 [U-Boot] [PATCH] spl: add a new stub spl_early_board_init() for early SoC-specific setup Masahiro Yamada
2016-03-08 23:23 ` Tom Rini [this message]
2016-03-09 9:48 ` Masahiro Yamada
2016-03-08 23:33 ` Simon Glass
2016-03-09 9:49 ` Masahiro Yamada
2016-03-13 2:51 ` Simon Glass
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=20160308232302.GV23166@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