Numonyx NOR and chip->mutex bug?

Michael Cashwell mboards at
Mon Feb 14 10:44:23 EST 2011

On Feb 10, 2011, at 12:20 PM, Joakim Tjernlund wrote:

> Michael Cashwell <mboards at> wrote on 2011/02/10 18:10:18:
>> On Feb 10, 2011, at 12:02 PM, Joakim Tjernlund wrote:
>>> And this reminds me that if the spec is to be trusted, the delay should be just before erase suspend, otherwise you miss the time between the initial erase and the first suspend.
>> Probably true to be completely sure. I bet the need for "repeated violations" is why I've been able to make it work by delaying after. But I agree.
> Yes, but you also indicated that a throw away status read made the problem go away?
> Can you move that status read to just before suspend and get the same results?

Well, sort of. The place where I've been doing the udelay or throw-away status read is when resuming, not suspending.

But interestingly, doing it right before the resume works just as well as right after.


More information about the linux-mtd mailing list