From: Thomas Gleixner <tglx@linutronix.de>
To: Ben Dooks <ben@fluff.org.uk>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Read/nBusy via interrupt
Date: Fri, 29 Oct 2004 01:13:43 +0200 [thread overview]
Message-ID: <1099005223.22387.501.camel@thomas> (raw)
In-Reply-To: <20041028230640.GB13105@home.fluff.org>
On Fri, 2004-10-29 at 00:06 +0100, Ben Dooks wrote:
> Does anyone here have any comments over the pros/cons of using
> an interrupt which goes off to wait for a NAND flash ready/not-busy
> signal?
Sure.
- It makes totaly sense for long lasting operations like program/erase.
- It's overkill for read operations.
You can make it work by supplying a wait function, which implements the
irq driven wait for program/erase. Don't forget the timeout !
tglx
next prev parent reply other threads:[~2004-10-28 23:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-28 23:06 Read/nBusy via interrupt Ben Dooks
2004-10-28 23:13 ` Thomas Gleixner [this message]
2004-10-28 23:43 ` Aras Vaichas
2004-10-29 7:33 ` Thomas Gleixner
2004-10-29 9:56 ` Aras Vaichas
2004-10-29 9:57 ` jasmine
2004-10-29 10:16 ` Thomas Gleixner
2004-11-01 0:01 ` Aras Vaichas
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=1099005223.22387.501.camel@thomas \
--to=tglx@linutronix.de \
--cc=ben@fluff.org.uk \
--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 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.