Skip to contentSkip to conversation

NAND_NO_AUTOINCR

DISCUSSION Artem B. Bityuckiy 2 participants 2 messages Sep 19, 2004 Memory technology devices (MTD)

lore
Share & tools
lore

Artem B. Bityuckiy

author
#0 lore raw

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.

Signature · 3 lines
Best Regards,
Artem B. Bityuckiy,
St.-Petersburg, Russia.
#1 lore raw
Quoted 1 line · Artem B. Bityuckiy

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))

Quoted 3 lines

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