public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v10] Marvell MV88F6281GTW_GE Board support
Date: Mon, 25 May 2009 09:08:12 +0200	[thread overview]
Message-ID: <200905250908.13242.sr@denx.de> (raw)
In-Reply-To: <73173D32E9439E4ABB5151606C3E19E201CF9E6A04@SC-VEXCH1.marvell.com>

On Monday 25 May 2009 06:48:40 Prafulla Wadaskar wrote:
> > > + */
> > > +
> > > +#include <common.h>
> > > +#include <netdev.h>
> > > +#include <asm/arch/kirkwood.h>
> > > +#include <asm/arch/mpp.h>
> > > +#include "mv88f6281gtw_ge.h"
> >
> > please move the mv88f6281gtw_ge.h
> > to include/asm-arm/arch-kirkwood/
>
> Sure... I will do it :-)

Sorry for the late reply, but for my taste such board specific headers don't 
belong into the "common" include/asm-arch/arch-kirkwood directory. The 
original location in the board directory is the best place (IMHO).

> > > +int board_init(void)
> > > +{
> > > +	/*
> > > +	 * default gpio configuration
> > > +	 * There are maximum 64 gpios controlled through 2 sets
> >
> > of registers
> >
> > > +	 * the  below configuration configures mainly initial LED status
> > > +	 */
> > > +	kw_config_gpio(MV88F6281GTW_GE_OE_VAL_LOW,
> > > +			MV88F6281GTW_GE_OE_VAL_HIGH,
> > > +			MV88F6281GTW_GE_OE_LOW,
> >
> > MV88F6281GTW_GE_OE_HIGH);
> >
> > > +
> > > +	/* Multi-Purpose Pins Functionality configuration */
> > > +	u32 kwmpp_config[] = {
> >
> > do you really need to configure all of this IO?
>
> Yes
> I device needs all IO initializations done to make sure unused MPPs must be
> configured to GPIOs. This is required to reduce overall boards noise that
> we have identified through h/w test in the lab
>
> > > +		MPP0_SPI_SCn,
> > > +		MPP1_SPI_MOSI,
> > > +		MPP2_SPI_SCK,
> > > +		MPP3_SPI_MISO,
> >
> > please add a device init api as done for davinci or at91
> > (could be done in an other patch)
>
> I could not get any reference for davinci or at91 for "device_init"
> Can you please provide me a specific pointer ?
>
> OR do you mean to create new api "device_init" to do soc/device specific
> init ? I think this is really not required here since it is specific to
> kirkwood implementation and may not apply for other architectures.
>
> In my opinion we do not need any specific init here in this code... Pls
> clarify...

I think the current code version is fine. We don't need to create an over-
complex API here.

Thanks.

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

      reply	other threads:[~2009-05-25  7:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-21  0:32 [U-Boot] [PATCH v10] Marvell MV88F6281GTW_GE Board support Prafulla Wadaskar
2009-05-22 11:06 ` Wolfgang Denk
2009-05-22 11:20   ` Prafulla Wadaskar
2009-05-22 13:40     ` Prafulla Wadaskar
2009-05-22 15:21     ` Wolfgang Denk
2009-05-25  4:19       ` Prafulla Wadaskar
2009-05-23  0:44 ` Jean-Christophe PLAGNIOL-VILLARD
2009-05-25  4:48   ` Prafulla Wadaskar
2009-05-25  7:08     ` Stefan Roese [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=200905250908.13242.sr@denx.de \
    --to=sr@denx.de \
    --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