Numonyx NOR and chip->mutex bug?

Joakim Tjernlund joakim.tjernlund at
Thu Feb 10 12:20:53 EST 2011

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?

> I have an idea for an efficient fix. But it's tricky to not impact writing speed. Once it get the idea worked out I'll post for comment. I have some other commitments today, so honestly it'll likely be next week at this point.

Nice, looking forward to that.

More information about the linux-mtd mailing list