From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V3] arm: timer and interrupt init rework
Date: Sat, 16 May 2009 08:11:50 +0200 [thread overview]
Message-ID: <4A0E5926.6010305@googlemail.com> (raw)
In-Reply-To: <1242244595-14934-1-git-send-email-plagnioj@jcrosoft.com>
Jean-Christophe PLAGNIOL-VILLARD wrote:
> actually the timer init use the interrupt_init as init callback
> which make the interrupt and timer implementation difficult to follow
>
> so now rename it as int timer_init(void) and use interrupt_init for interrupt
>
> btw also remane the corresponding file to the functionnality implemented
>
> as ixp arch implement two timer - one based on interrupt - so all the timer
> related code is moved to timer.c
>
> Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
ARM Cortex-A8 part
Signed-off-by: Dirk Behme <dirk.behme@googlemail.com>
...
> diff --git a/lib_arm/board.c b/lib_arm/board.c
> index 5d05d9b..37ed3e3 100644
> --- a/lib_arm/board.c
> +++ b/lib_arm/board.c
> @@ -266,7 +266,10 @@ init_fnc_t *init_sequence[] = {
> arch_cpu_init, /* basic arch cpu dependent setup */
> #endif
> board_init, /* basic board dependent setup */
> +#if defined(CONFIG_USE_IRQ)
> interrupt_init, /* set up exceptions */
> +#endif
> + timer_init, /* initialize timer */
> env_init, /* initialize environment */
> init_baudrate, /* initialze baudrate settings */
> serial_init, /* serial communications setup */
Btw.: Jean-Christophe: I'm happy that you removed the re-ordering of
boot sequence for the moment as discussed in [1] :)
Best regards
Dirk
[1] http://lists.denx.de/pipermail/u-boot/2009-May/051949.html
prev parent reply other threads:[~2009-05-16 6:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 19:56 [U-Boot] [PATCH V3] arm: timer and interrupt init rework Jean-Christophe PLAGNIOL-VILLARD
2009-05-16 6:11 ` Dirk Behme [this message]
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=4A0E5926.6010305@googlemail.com \
--to=dirk.behme@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