From mboxrd@z Thu Jan  1 00:00:00 1970
From: Dieter Kiermaier <dk-arm-linux@gmx.de>
Date: Tue, 23 Jun 2009 10:47:47 +0200
Subject: [U-Boot] [PATCH v2 1/3][repost] nand: Add Marvell Kirkwood NAND
	driver
In-Reply-To: <20090623083531.GC23512@game.jcrosoft.org>
References: <73173D32E9439E4ABB5151606C3E19E201D8E62E77@SC-VEXCH1.marvell.com>
	<200906231024.14530.dk-arm-linux@gmx.de>
	<20090623083531.GC23512@game.jcrosoft.org>
Message-ID: <200906231047.47343.dk-arm-linux@gmx.de>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Am Dienstag 23 Juni 2009 10:35:31 schrieb Jean-Christophe PLAGNIOL-VILLARD:

> > > I2C lowest priority (as per need)
> >
> > Can I do something to push I2C priority?
>
> If the I/O is shared with gpio you can use bitbanging with few hours

I think this would be the best to start - due to the fact that I need 
bitbanging for FPGA flashing, too.

>
> Best Regards,
> J.

@Prafulla:
in kirkwood/cpu.c
there are 2 functions:
kw_config_gpio()
kw_config_mpp()

If I implement additional functions like
kw_gpio_direction(int gpio, enum direction)
kw_gpio_set(int gpio, int value)
int value kw_gpio_get(int gpio)

If the functions are implemented in cpu.c are they accessible from cmd_xxx.c 
functions?

Would this be ok to get it mainline or should there be an special driver for 
gpio access?

Sorry for my newbie questions :)


Dieter