From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH 2/3] ARM i.MX25/35: initialize barebox_loc earlier
Date: Mon, 15 Aug 2011 11:09:03 +0200 [thread overview]
Message-ID: <1313399344-21259-3-git-send-email-s.hauer@pengutronix.de> (raw)
In-Reply-To: <1313399344-21259-1-git-send-email-s.hauer@pengutronix.de>
Now that env_push_context is in a coredevice_initcall
we can initialize barebox_loc earlier so that we can
use it inside later initcalls.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
arch/arm/mach-imx/boot.c | 8 ++------
1 files changed, 2 insertions(+), 6 deletions(-)
diff --git a/arch/arm/mach-imx/boot.c b/arch/arm/mach-imx/boot.c
index b4bf93b..8482b60 100644
--- a/arch/arm/mach-imx/boot.c
+++ b/arch/arm/mach-imx/boot.c
@@ -41,7 +41,7 @@
* Note also that I suspect that the boot source pins are only sampled at
* power up.
*/
-static int imx_boot_save_loc(void)
+static int imx_25_35_boot_save_loc(void)
{
const char *bareboxloc = NULL;
uint32_t reg;
@@ -86,10 +86,6 @@ static int imx_boot_save_loc(void)
return 0;
}
-/*
- * This can only be called after env_push_context() has been called
- * so it is a late_initcall.
- */
-late_initcall(imx_boot_save_loc);
+coredevice_initcall(imx_25_35_boot_save_loc);
#endif
--
1.7.5.4
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2011-08-15 9:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-15 9:09 [PATCH] initialize barebox_loc on i.MX51 Sascha Hauer
2011-08-15 9:09 ` [PATCH 1/3] put env_push_context into postcore_initcall Sascha Hauer
2011-08-15 9:09 ` Sascha Hauer [this message]
2011-08-15 9:09 ` [PATCH 3/3] ARM i.MX51: set barebox_loc according to boot source Sascha Hauer
2011-08-17 9:25 ` [PATCH] initialize barebox_loc on i.MX51 Marc Reilly
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=1313399344-21259-3-git-send-email-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
/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