public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Derek Ross" <dross@iders.ca>
To: <linux-mtd@lists.infradead.org>
Subject: Re: Are erase suspends possible?
Date: Tue, 2 Apr 2002 11:59:14 -0600	[thread overview]
Message-ID: <005701c1da70$1a0370f0$87657bc8@athlon> (raw)
In-Reply-To: 3371.1017706441@redhat.com

> dross@iders.ca said:
> > I was looking through the code in  cfi_cmdset_0001.c, and it appears
> > that erase suspends are not implemented. Is this correct? 
> 
> No. Erase suspend has been working for ages. What version of 
> cfi_cmdset_0001.c are you looking at?

Sorry, I'm still wrapping my brain around mtd.

I'm looking at a recent version, and it has
the function "cfi_intelext_suspend".

I was also looking at the function "do_write_oneword", and
internally, it seems to halt if an erase is in progress.

Also, the function, do_erase_oneblock seems to 
block during the erase.

What would be good for my application is if there
were two more functions:

"do_erase_oneblock_dont_wait",
which doesn't wait for the erase to finish, and
returns immediately,

and

"do_write_oneword_suspend_if_needed",
which will always write without delay, even
if it has to suspend an erase that's in progress.

I'm sure it wouldn't be difficult to write these
extra functions (especially "do_write_oneword_suspend_if_needed", 
which would just need an call to "cfi_intelext_suspend"), 
but I'm worried that it would 
be impossible to call using /dev/mtd and ioctl calls.

Also, my app will effective deactivate any other 
flash interaction during this phase, so I'm not
worried about JFFS interference.

Thanks,
Derek Ross.

  reply	other threads:[~2002-04-02 17:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-01 22:44 Are erase suspends possible? Derek Ross
2002-04-02  0:14 ` David Woodhouse
2002-04-02 17:59   ` Derek Ross [this message]
2002-04-03  0:38     ` David Woodhouse
2002-04-03 15:35       ` Derek Ross
2002-04-03 16:07         ` Joakim Tjernlund

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='005701c1da70$1a0370f0$87657bc8@athlon' \
    --to=dross@iders.ca \
    --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