mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Matthias Kaehlcke <matthias@kaehlcke.net>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 0/5] Add support for EDB93xx boards
Date: Mon, 11 Jan 2010 12:25:57 +0100	[thread overview]
Message-ID: <20100111112557.GU6923@pengutronix.de> (raw)
In-Reply-To: <20100111103700.GH14051@darwin>

On Mon, Jan 11, 2010 at 11:37:00AM +0100, Matthias Kaehlcke wrote:
> Hi Sascha,
> 
> El Mon, Jan 11, 2010 at 10:49:02AM +0100 Sascha Hauer ha dit:
> 
> > Thanks for the nice work. The patches look mostly fine. I wonder that
> > U-Boot ep93xx support has never made it to the mainline. Some comments
> > about the patches inline.
> 
> in late december i sent a (new) set of patches to the U-Boot mailing
> list. i still havn't received feedback, i suppose due to christmas,
> new year, ... my aim is to mainline ep93xx support, i am confident
> this will be accomplished soon.
> 
> > On Sun, Jan 10, 2010 at 12:28:38AM +0100, Matthias Kaehlcke wrote:
> > > Add support for the following Cirrus Logic EDB93xx boards:
> > > 
> > > EDB9301
> > > EDB9302
> > > EDB9302A
> > > EDB9307
> > > EDB9307A
> > > EDB93012
> > > EDB9315
> > > EDB9315A
> > > 
> > > This patchset has been tested on boards based on the EDB9301 and EDB9307A designs
> > > 
> > > Matthias Kaehlcke (5):
> > >   ARM: Add support for EP93xx SoCs
> > >   Add EP93xx ethernet driver
> > >   Add support for EP9xx GPIOs
> > >   Add PrimeCell PL010 serial driver
> > >   Add support for EDB93xx boards
> > > 
> > >  Documentation/boards.dox                        |    8 +
> > >  MAINTAINERS                                     |   11 +
> > >  arch/arm/Kconfig                                |    6 +
> > >  arch/arm/Makefile                               |    9 +
> > >  arch/arm/configs/edb93xx_defconfig              |  237 ++++++++
> > >  arch/arm/mach-ep93xx/Kconfig                    |  446 +++++++++++++++
> > >  arch/arm/mach-ep93xx/Makefile                   |    3 +
> > >  arch/arm/mach-ep93xx/clocksource.c              |   96 ++++
> > >  arch/arm/mach-ep93xx/gpio.c                     |  136 +++++
> > >  arch/arm/mach-ep93xx/include/mach/ep93xx-regs.h |  600 ++++++++++++++++++++
> > >  arch/arm/mach-ep93xx/include/mach/gpio.h        |   29 +
> > >  arch/arm/mach-ep93xx/led.c                      |   62 ++
> > >  arch/arm/mach-ep93xx/led.h                      |   26 +
> > >  arch/arm/mach-ep93xx/lowlevel_init.S            |   64 +++
> > 
> > Aren't the LED functions and thus the lowlevel_init board specific?
> > I can imagine many custom boards do not have LEDs connected to these
> > gpio pins.
> 
> custom board could do this, but probably shouldn't. the EP93xx
> explicitly 'reserves' specific GPIOs for a red and a green LED. these
> LEDs are used by the boot algorithm to give feed back before the
> bootloader is started.

Ah, I didn't know this. A good move from Cirrus that the software
developer can rely on some debug LEDs.

> 
> please tell me if this convinces you to leave the LED functions and
> lowlevel_init in the SoC part or if you prefer moving them to the
> board directory.

I'm fine with the LEDs being available for all ep93xx then.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

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

  reply	other threads:[~2010-01-11 11:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-09 23:28 Matthias Kaehlcke
2010-01-11  9:49 ` Sascha Hauer
2010-01-11 10:37   ` Matthias Kaehlcke
2010-01-11 11:25     ` Sascha Hauer [this message]
2010-01-11 21:31       ` [PATCH] Add support for EDB93xx boards [rev2] Matthias Kaehlcke
2010-01-12  9:52         ` Sascha Hauer
2010-01-12 19:30           ` Matthias Kaehlcke

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=20100111112557.GU6923@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=matthias@kaehlcke.net \
    /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