From: Ralph Siemsen <ralphs@netwinder.org>
To: linux-mtd@lists.infradead.org
Subject: Unlocking with Intel J3 series flash
Date: Tue, 31 Jul 2007 11:35:47 -0400 [thread overview]
Message-ID: <20070731153547.GA24705@marvin.netwinder.org> (raw)
Greetings,
When using Intel J3 flash, unlocking operations are horribly slow.
The reason for this is that the J3 has "Flexible Block-locking" feature
(to quote that data sheet) which "allows blocks to be individually
locked and simultaneously unlocked".
Unlike other flash chips which power up either locked or unlocked,
the J3 series stores lock status in the flash itself (non-volatile).
Locking is reasonably fast (~64us) and can be done per-block, but
unlocking is very slow (~0.5s) and does the whole chip at once.
Current MTD code makes the situation much worse, because the
unlock() operation goes via cfi_varsize_frob() and iterates over
the block lists. This is of course correct behaviour when the
cells are indivudually un-lockable, however it results in minute-long
delays and many needeless erase cycles for the J3 series.
I am looking for ideas on how to deal with this. One idea would be
to introduce a cousin to the existing MTD_STUPID_LOCK, perhaps one
called MTD_STUPID_UNLOCK, which would then be used to ensure that
unlocking does not iterate over all flash blocks.
-R
next reply other threads:[~2007-07-31 15:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 15:35 Ralph Siemsen [this message]
2007-07-31 16:23 ` Unlocking with Intel J3 series flash Ben Dooks
2007-07-31 17:56 ` Ralph Siemsen
2007-08-02 12:03 ` Ralph Siemsen
2007-07-31 16:23 ` MikeW
2007-07-31 21:33 ` David Woodhouse
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=20070731153547.GA24705@marvin.netwinder.org \
--to=ralphs@netwinder.org \
--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