mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 4/5] BCM2835: add support (arch)
Date: Wed, 17 Oct 2012 09:25:48 +0200	[thread overview]
Message-ID: <20121017072548.GE30038@game.jcrosoft.org> (raw)
In-Reply-To: <20121017070139.GM27665@pengutronix.de>

On 09:01 Wed 17 Oct     , Sascha Hauer wrote:
> On Wed, Oct 17, 2012 at 08:51:35AM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > On 23:24 Tue 16 Oct     , Sascha Hauer wrote:
> > > On Tue, Oct 16, 2012 at 08:04:44PM +0200, Carlo Caione wrote:
> > > > +
> > > > +static struct clk ref_3_clk = {
> > > > +	.rate = 3 * 1000 * 1000,
> > > > +};
> > > > +
> > > > +static struct clk ref_1_clk = {
> > > > +	.rate = 1 * 1000 * 1000,
> > > > +};
> > > 
> > > Add a 'select COMMON_CLK' to your Kconfig and do a:
> > > 
> > > 	clk_dummy = clk_fixed("dummy", 0);
> > > 	clk_ref_3 = clk_fixed("ref3", 3 * 1000 * 1000);
> > > 	clk_ref_1 = clk_fixed("ref1", 1 * 1000 * 1000);
> > > 
> > > Then you can drop your clk code and get a clk_dump command
> > > which you can use to see what clocks you have.
> > > 
> > > > +static int bcm2835_gpio_init(void)
> > > > +{
> > > > +	add_generic_device("bcm2835-gpio", 0, NULL, BCM2835_GPIO_BASE, 0xB0, IORESOURCE_MEM, NULL);
> > > > +	return 0;
> > > > +}
> > > > +coredevice_initcall(bcm2835_gpio_init);
> > > > +
> > > > +static int bcm2835_clkdev_init(void)
> > > > +{
> > > > +	clkdev_add_table(clocks_lookups, ARRAY_SIZE(clocks_lookups));
> > > > +	return 0;
> > > > +}
> > > > +postcore_initcall(bcm2835_clkdev_init);
> > > > +
> > > > +static int bcm2835_clocksource_init(void)
> > > > +{
> > > > +	add_generic_device("bcm2835-cs", DEVICE_ID_SINGLE, NULL, BCM2835_ST_BASE, 0x1C, IORESOURCE_MEM, NULL);
> > > > +	return 0;
> > > > +}
> > > > +coredevice_initcall(bcm2835_clocksource_init);
> > > > +
> > > 
> > > Please consolidate the initcalls. A single function for the three above
> > > is enough.
> > > 
> > > > +void bcm2835_register_uart(void)
> > > 
> > > Please add the UART index to the function name.
> > as we discuss no need the uart1 use the same pin as uart0 and is a wired mini
> > uart
> 
> But it has a different register base. How do I decide which one I use?
why use a different at the end it the same pin

Best Regards,
J.

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2012-10-17  7:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-16 18:04 [PATCH 0/5] BCM2835/Raspberry-Pi support Carlo Caione
2012-10-16 18:04 ` [PATCH 1/5] BCM2835: add clocksource driver Carlo Caione
2012-10-16 18:04 ` [PATCH 2/5] BCM2835: add gpio driver Carlo Caione
2012-10-16 21:09   ` Sascha Hauer
2012-10-16 18:04 ` [PATCH 3/5] ARM1176: add support Carlo Caione
2012-10-16 18:04 ` [PATCH 4/5] BCM2835: add support (arch) Carlo Caione
2012-10-16 21:24   ` Sascha Hauer
2012-10-17  6:51     ` Jean-Christophe PLAGNIOL-VILLARD
2012-10-17  7:01       ` Sascha Hauer
2012-10-17  7:25         ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2012-10-17  8:31           ` Carlo Caione
2012-10-17 21:00             ` Sascha Hauer
2012-10-17 22:27     ` Carlo Caione
2012-10-18  7:02       ` Sascha Hauer
2012-10-16 18:04 ` [PATCH 5/5] Raspberry-Pi: add support (board) Carlo Caione
  -- strict thread matches above, loose matches on Subject: below --
2012-10-18 19:42 [PATCH 0/5] BCM2835/Raspberry-Pi support Carlo Caione
2012-10-18 19:42 ` [PATCH 4/5] BCM2835: add support (arch) Carlo Caione
2012-10-13 14:00 [PATCH 0/5] BCM2835/Raspberry-Pi support Carlo Caione
2012-10-13 14:00 ` [PATCH 4/5] BCM2835: add support (arch) Carlo Caione
2012-10-13 11:22 [PATCH 0/5] BCM2835/Raspberry-Pi Carlo Caione
2012-10-13 11:23 ` [PATCH 4/5] BCM2835: add support (arch) Carlo Caione

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=20121017072548.GE30038@game.jcrosoft.org \
    --to=plagnioj@jcrosoft.com \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.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