public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: tglx@linutronix.de
Cc: linux-mtd@lists.infradead.org
Cc: "J.D. Bakker" <bakker@thorgal.et.tudelft.nl>
Subject: Re: Handling multiple NAND chips
Date: Sat, 26 Jul 2003 11:08:34 -0400	[thread overview]
Message-ID: <1059232112.539.5.camel@lapdancer.baythorne.internal> (raw)
In-Reply-To: <200307261339.13142.tglx@linutronix.de>

On Sat, 2003-07-26 at 07:39, Thomas Gleixner wrote:
> You can do this, but the question is, if it is really an advantage.

Dunno. In general, interrupt-driven operation is an advantage over
polling -- it lets us get on with something else while we're waiting for
the flash, and come straight back to the flash driver when it's done.
Given the latencies involved on NAND, though, it might not really be
worth the effort -- but I'd like to investigate.

-- 
dwmw2

  reply	other threads:[~2003-07-26 15:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-25 15:12 Handling multiple NAND chips J.D. Bakker
2003-07-25 15:36 ` David Woodhouse
2003-07-25 15:51   ` J.D. Bakker
2003-07-25 15:56     ` David Woodhouse
2003-07-26 10:22       ` J.D. Bakker
2003-07-26 11:39         ` Thomas Gleixner
2003-07-26 15:08           ` David Woodhouse [this message]
2003-07-26 17:20             ` Thomas Gleixner
2003-07-26 15:06         ` David Woodhouse
2003-07-26 18:20           ` J.D. Bakker
2003-07-26 19:05             ` David Woodhouse
2003-07-27 12:54       ` J.D. Bakker
2003-07-27 13:42         ` David Woodhouse
2003-07-27 13:58           ` J.D. Bakker
2003-07-27 16:28             ` David Woodhouse
2003-07-25 15:51 ` David Woodhouse
2003-07-26  0:27 ` Charles Manning
2003-07-26 10:32   ` J.D. Bakker

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=1059232112.539.5.camel@lapdancer.baythorne.internal \
    --to=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=tglx@linutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox