From: Dieter Kiermaier <dk-arm-linux@gmx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/3][repost] nand: Add Marvell Kirkwood NAND driver
Date: Tue, 23 Jun 2009 13:23:18 +0200 [thread overview]
Message-ID: <200906231323.19050.dk-arm-linux@gmx.de> (raw)
In-Reply-To: <73173D32E9439E4ABB5151606C3E19E201D8E62EC2@SC-VEXCH1.marvell.com>
Am Dienstag 23 Juni 2009 12:38:05 schrieb Prafulla Wadaskar:
> > -----Original Message-----
> > From: Dieter Kiermaier [mailto:dk-arm-linux at gmx.de]
> > Sent: Tuesday, June 23, 2009 2:18 PM
> > To: Jean-Christophe PLAGNIOL-VILLARD
> > Cc: Prafulla Wadaskar; u-boot at lists.denx.de; Scott Wood;
> > Ashish Karkare; Prabhanjan Sarnaik; Ronen Shitrit
> > Subject: Re: [U-Boot] [PATCH v2 1/3][repost] nand: Add
> > Marvell Kirkwood NAND driver
> >
> > 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?
>
> Any way this driver will be arround TWSI controller interface by h/w
> Again if you are using different pins then may not be helpful for you
>
I2C by hardware is ok because the pins are not multiplexed with other
important functions as its the case for SPI.
And also I2C isn't _so_ important to bring up the first board revision :)
> > > 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.
>
> This is a good Idea, start your development with accessing GPIO registers
> directly
I start working on gpio stuff now and sending my patches to you. Maybe it is
helpful for others, too,
Dieter
>
> Regards..
> Prafulla . . .
next prev parent reply other threads:[~2009-06-23 11:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-14 17:02 [U-Boot] [PATCH v2 1/3][repost] nand: Add Marvell Kirkwood NAND driver Prafulla Wadaskar
2009-06-22 22:05 ` Scott Wood
2009-06-23 6:08 ` Prafulla Wadaskar
2009-06-23 7:02 ` Jean-Christophe PLAGNIOL-VILLARD
2009-06-23 7:52 ` Dieter Kiermaier
2009-06-23 8:01 ` Prafulla Wadaskar
2009-06-23 8:24 ` Dieter Kiermaier
2009-06-23 8:35 ` Jean-Christophe PLAGNIOL-VILLARD
2009-06-23 8:47 ` Dieter Kiermaier
2009-06-23 10:38 ` Prafulla Wadaskar
2009-06-23 11:23 ` Dieter Kiermaier [this message]
2009-06-23 12:06 ` Stefan Roese
2009-06-23 12:06 ` Prafulla Wadaskar
2009-06-23 12:14 ` Dieter Kiermaier
2009-06-26 7:32 ` Prafulla Wadaskar
2009-06-27 15:22 ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-07 10:31 ` Prafulla Wadaskar
2009-07-07 20:26 ` Jean-Christophe PLAGNIOL-VILLARD
-- strict thread matches above, loose matches on Subject: below --
2009-06-08 12:04 Prafulla Wadaskar
2009-06-13 14:01 ` Jean-Christophe PLAGNIOL-VILLARD
2009-06-19 9:27 ` Prafulla Wadaskar
2009-06-19 14:52 ` Scott Wood
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=200906231323.19050.dk-arm-linux@gmx.de \
--to=dk-arm-linux@gmx.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 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.