* NAND_NO_AUTOINCR
@ 2004-09-19 13:56 Artem B. Bityuckiy
2004-09-19 13:58 ` NAND_NO_AUTOINCR Thomas Gleixner
0 siblings, 1 reply; 2+ messages in thread
From: Artem B. Bityuckiy @ 2004-09-19 13:56 UTC (permalink / raw)
To: linux-mtd
It seems that NAND_NO_AUTOINCR option isn't really used in mtd, anyway...
What does the NAND_NO_AUTOINCR mean? I suspect that this means that in
read operations we can continue reading next consequitive pages without
new read operation cycle. Is it this?
Thanks.
--
Best Regards,
Artem B. Bityuckiy,
St.-Petersburg, Russia.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: NAND_NO_AUTOINCR
2004-09-19 13:56 NAND_NO_AUTOINCR Artem B. Bityuckiy
@ 2004-09-19 13:58 ` Thomas Gleixner
0 siblings, 0 replies; 2+ messages in thread
From: Thomas Gleixner @ 2004-09-19 13:58 UTC (permalink / raw)
To: Artem B. Bityuckiy; +Cc: linux-mtd
On Sun, 2004-09-19 at 15:56, Artem B. Bityuckiy wrote:
> It seems that NAND_NO_AUTOINCR option isn't really used in mtd, anyway...
It is used. :)
nand.h
#define NAND_CANAUTOINCR(chip) (!(chip->options & NAND_NO_AUTOINCR))
> What does the NAND_NO_AUTOINCR mean? I suspect that this means that in
> read operations we can continue reading next consequitive pages without
> new read operation cycle. Is it this?
Yes, most of the 1st generation chips (256/512 byte pagesize) have this
feature. It's important to be aware of this.
After reading a page, those chips are automatically transferring the
next page into the read buffer.
The 2nd generation chips (2K pagesize and a couple of the newer 512byte
pagesize chips) do not have this feature, so you must explicitely issue
a new page read command to get the next page data.
tglx
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2004-09-19 14:06 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-09-19 13:56 NAND_NO_AUTOINCR Artem B. Bityuckiy
2004-09-19 13:58 ` NAND_NO_AUTOINCR Thomas Gleixner
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox