From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] arm: Adds board_postclk_init to the init_sequence.
Date: Tue, 04 Sep 2012 21:17:58 +0200 [thread overview]
Message-ID: <504653E6.4020602@googlemail.com> (raw)
In-Reply-To: <1345141329-1084-2-git-send-email-mhubig@imko.de>
Dear Albert Aribaud,
On 16.08.12 20:22, Markus Hubig wrote:
> The board_postclk_init() function can be used to perform operations
> that requires a working timer early within the U-Boot init_sequence.
>
> Signed-off-by: Markus Hubig <mhubig@imko.de>
> Cc: Albert ARIBAUD <albert.u.boot@aribaud.net>
> ---
> arch/arm/lib/board.c | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/lib/board.c b/arch/arm/lib/board.c
> index f1951e8..109a1ac 100644
> --- a/arch/arm/lib/board.c
> +++ b/arch/arm/lib/board.c
> @@ -241,6 +241,9 @@ init_fnc_t *init_sequence[] = {
> fdtdec_check_fdt,
> #endif
> timer_init, /* initialize timer */
> +#ifdef CONFIG_BOARD_POSTCLK_INIT
> + board_postclk_init,
> +#endif
> #ifdef CONFIG_FSL_ESDHC
> get_clocks,
> #endif
>
how do you think about this suggestion? Will you accept it? Should I
apply both patches to u-boot-atmel?
Best regards
Andreas Bie?mann
next prev parent reply other threads:[~2012-09-04 19:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 18:22 [U-Boot] [PATCH 0/2] at91: Fixes the crippled console output on PortuxG20 Markus Hubig
2012-08-16 18:22 ` [U-Boot] [PATCH 1/2] arm: Adds board_postclk_init to the init_sequence Markus Hubig
2012-09-04 19:17 ` Andreas Bießmann [this message]
2012-09-04 19:34 ` Albert ARIBAUD
2012-09-04 19:35 ` Andreas Bießmann
2012-09-04 20:01 ` Albert ARIBAUD
2012-09-04 20:08 ` Andreas Bießmann
2012-08-16 18:22 ` [U-Boot] [PATCH 2/2] Fixes the crippled console output on PortuxG20 Markus Hubig
2012-09-04 20:10 ` Andreas Bießmann
2012-08-31 12:36 ` [U-Boot] [PATCH 0/2] at91: " Markus Hubig
2012-08-31 13:25 ` Andreas Bießmann
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=504653E6.4020602@googlemail.com \
--to=andreas.devel@googlemail.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