From: Michael Cashwell <mboards@prograde.net>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: linux-mtd@lists.infradead.org,
Holger brunck <holger.brunck@keymile.com>,
Stefan Bigler <stefan.bigler@keymile.com>
Subject: Re: Numonyx NOR and chip->mutex bug?
Date: Thu, 3 Feb 2011 10:24:59 -0500 [thread overview]
Message-ID: <6FC0E416-EEBD-453F-AAB9-88BB6D90BFAB@prograde.net> (raw)
In-Reply-To: <OF562F5C46.D2EDB17F-ONC125782C.00358774-C125782C.0036154D@transmode.se>
On Feb 3, 2011, at 4:50 AM, Joakim Tjernlund wrote:
>>> My failures were caused by the erase-resume status read "seeing" a non-busy WSM. Adding a 20µs delay before that read (actually after the command write, but it amounts to the same thing) prevents this from happening. By the time awakened "wait-for-completion" code does its first status read it sees the WSM as busy as it should until the erase actually finishes.
>
> Perhaps you can test for ESS(SR.6) too?
> something like:
> if DWS && !ESS
Hmmm. So instead of a blind delay it would loop (with a timeout) while DWS && ESS are both set (meaning the erase resume command just written hasn't yet taken effect). It does make sense that if the resume takes time to drop SR.7 (ready) that it would also take time to drop SR.6 (ESS).
I like that. I'll add that to the set of tests today and report back.
-Mike
next prev parent reply other threads:[~2011-02-03 15:24 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 18:14 Numonyx NOR and chip->mutex bug? Michael Cashwell
2011-01-25 18:56 ` Joakim Tjernlund
2011-01-25 22:03 ` Michael Cashwell
2011-01-25 23:09 ` Joakim Tjernlund
2011-02-02 16:20 ` Michael Cashwell
2011-02-02 17:37 ` Stefan Bigler
2011-02-02 20:12 ` Joakim Tjernlund
2011-02-02 21:19 ` Michael Cashwell
2011-02-03 8:11 ` Joakim Tjernlund
2011-02-03 9:50 ` Joakim Tjernlund
2011-02-03 15:24 ` Michael Cashwell [this message]
2011-02-03 16:38 ` Stefan Bigler
2011-02-03 23:18 ` Stefan Bigler
2011-02-04 10:47 ` Joakim Tjernlund
2011-02-04 11:04 ` Stefan Bigler
2011-02-04 12:26 ` Joakim Tjernlund
2011-02-04 12:35 ` Joakim Tjernlund
2011-02-04 12:42 ` Joakim Tjernlund
2011-02-04 13:05 ` Joakim Tjernlund
2011-02-04 13:25 ` Joakim Tjernlund
2011-02-04 16:45 ` Stefan Bigler
2011-02-04 16:55 ` Joakim Tjernlund
2011-02-04 17:09 ` Michael Cashwell
[not found] ` <OF42EF <F66AF016-8A2B-4116-BE49-CE05B91BE50F@prograde.net>
[not found] ` <OF42EF<F66AF016-8A2B-4116-BE49-CE05B91BE50F@prograde.net>
2011-02-05 10:29 ` Joakim Tjernlund
2011-02-05 19:19 ` Michael Cashwell
2011-02-05 21:47 ` Michael Cashwell
2011-02-06 9:46 ` Joakim Tjernlund
2011-02-06 15:49 ` Michael Cashwell
2011-02-06 17:29 ` Joakim Tjernlund
2011-02-06 21:13 ` Michael Cashwell
[not found] ` <OF2C1ABD39 <4D5005E4.1040506@keymile.com>
[not found] ` <OFFF2C6D34.91E5D6C3-ONC1257 <96BD3889-E8AD-408D-8275-ED1A5FD55F1B@prograde.net>
[not found] ` <OF2C1ABD39<4D5005E4.1040506@keymile.com>
[not found] ` <OFFF2C6D34.91E5D6C3-ONC1257<96BD3889-E8AD-408D-8275-ED1A5FD55F1B@prograde.net>
[not found] ` <OF9738D658.F46<4C117A67-5057-4ACD-8EBE-04E9C782570C@prograde.net>
[not found] ` <OF6D40AC82.1008D3DD-ONC1 <4D53E660.4020305@users.sourceforge.net>
2011-02-06 21:20 ` Joakim Tjernlund
2011-02-07 14:47 ` Stefan Bigler
2011-02-07 15:01 ` Joakim Tjernlund
2011-02-07 15:46 ` Michael Cashwell
2011-02-07 15:52 ` Stefan Bigler
2011-02-07 16:22 ` Joakim Tjernlund
2011-02-07 16:46 ` Michael Cashwell
2011-02-07 17:08 ` Stefan Bigler
2011-02-07 19:04 ` Michael Cashwell
2011-02-09 19:52 ` Michael Cashwell
2011-02-09 20:13 ` Joakim Tjernlund
2011-02-09 21:59 ` Michael Cashwell
2011-02-10 13:21 ` Anders Grafström
2011-02-10 14:04 ` Joakim Tjernlund
2011-02-10 15:04 ` Joakim Tjernlund
2011-02-10 15:59 ` Michael Cashwell
2011-02-10 16:05 ` Joakim Tjernlund
2011-02-10 16:41 ` Michael Cashwell
2011-02-10 16:46 ` Joakim Tjernlund
2011-02-10 17:02 ` Joakim Tjernlund
2011-02-10 17:10 ` Michael Cashwell
2011-02-10 17:20 ` Joakim Tjernlund
2011-02-10 17:47 ` Joakim Tjernlund
2011-02-10 18:26 ` Joakim Tjernlund
2011-02-11 18:03 ` Michael Cashwell
2011-02-12 10:47 ` Joakim Tjernlund
2011-02-14 15:59 ` Michael Cashwell
2011-02-14 15:44 ` Michael Cashwell
2011-02-10 16:43 ` Michael Cashwell
2011-02-10 17:54 ` Anders Grafström
2011-02-11 15:05 ` Michael Cashwell
2011-02-11 15:39 ` Joakim Tjernlund
2011-02-14 16:15 ` Michael Cashwell
2011-02-11 17:00 ` Joakim Tjernlund
2011-02-10 15:43 ` Michael Cashwell
2011-02-10 15:51 ` Joakim Tjernlund
2011-02-24 10:50 ` Joakim Tjernlund
2011-02-24 11:36 ` Joakim Tjernlund
2011-02-24 14:28 ` Michael Cashwell
2011-02-10 14:53 ` Joakim Tjernlund
2011-02-06 9:40 ` Joakim Tjernlund
2011-02-06 14:55 ` Michael Cashwell
2011-02-07 15:10 ` Michael Cashwell
2011-02-07 15:48 ` Joakim Tjernlund
2011-02-03 13:24 ` Michael Cashwell
2011-02-03 14:01 ` 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=6FC0E416-EEBD-453F-AAB9-88BB6D90BFAB@prograde.net \
--to=mboards@prograde.net \
--cc=holger.brunck@keymile.com \
--cc=joakim.tjernlund@transmode.se \
--cc=linux-mtd@lists.infradead.org \
--cc=stefan.bigler@keymile.com \
/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.