From: Stelian Pop <stelian@popies.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH RFC] at91sam9/at91cap: move common initialisation to cpu
Date: Fri, 14 Nov 2008 10:17:13 +0100 [thread overview]
Message-ID: <1226654233.8836.29.camel@galileo> (raw)
In-Reply-To: <20081113223224.GE25695@game.jcrosoft.org>
Le jeudi 13 novembre 2008 ? 23:32 +0100, Jean-Christophe
PLAGNIOL-VILLARD a ?crit :
> > Note however that serial and spi are not the only initialisations that
> > can be moved: the very same thing can be done with all the other device
> > initialisations.
> I've just put serial & spi for the RFC
Ok then.
[...]
> > Why don't just do at91_serial_hw_init() once, and test the CONFIG_USART*
> > inside the cpu specific at91_serial_hw_init function() ?
> >
> > This also eliminates that unneeded switch case in that function.
> The idea is too allow multiple serial at the same time.
>
> I've plan to add the multi serial support to the at91 serial drivers
I'm not sure exactly what you mean by "multi serial support" but isn't
this orthogonal to what I'm saying (putting the #ifdef CONFIG_USART0
inside the cpu specific file instead of board specific file) ?
Stelian.
--
Stelian Pop <stelian@popies.net>
next prev parent reply other threads:[~2008-11-14 9:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-07 19:38 [U-Boot] [PATCH RFC] at91sam9/at91cap: move common initialisation to cpu Jean-Christophe PLAGNIOL-VILLARD
2008-11-13 21:28 ` Stelian Pop
2008-11-13 22:32 ` Jean-Christophe PLAGNIOL-VILLARD
2008-11-14 9:17 ` Stelian Pop [this message]
2008-11-16 12:28 ` Remy Bohmer
2009-02-05 21:38 ` Jean-Christophe PLAGNIOL-VILLARD
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=1226654233.8836.29.camel@galileo \
--to=stelian@popies.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.