From: Thomas Gleixner <tglx@linutronix.de>
To: "Artem B. Bityuckiy" <abityuckiy@yandex.ru>
Cc: linux-mtd@lists.infradead.org
Subject: Re: NAND_NO_AUTOINCR
Date: Sun, 19 Sep 2004 15:58:31 +0200 [thread overview]
Message-ID: <1095602310.28388.368.camel@thomas.tec.linutronix.de> (raw)
In-Reply-To: <414D901A.3000703@yandex.ru>
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
prev parent reply other threads:[~2004-09-19 14:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-19 13:56 NAND_NO_AUTOINCR Artem B. Bityuckiy
2004-09-19 13:58 ` Thomas Gleixner [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=1095602310.28388.368.camel@thomas.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=abityuckiy@yandex.ru \
--cc=linux-mtd@lists.infradead.org \
/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