[PATCH] mtd: Apply Numonyx Axcell P33/P30 workaround for Lock/Unlock bug.

[Philippe De Muyter]

On Thu, Oct 21, 2010 at 11:39:58AM +0300, Artem Bityutskiy wrote:
> On Tue, 2010-10-19 at 16:24 +0200, Philippe De Muyter wrote:
> > Some flash chips have a small but annoying bug, documented in
> >     "Numonyx Axcell P33/P30 256-Mbit Specification Update"
> > 
> >     It states :
> >     When customer uses [...] block unlock, the block lock status might
> >     be altered inadvertently. Lock status might be set to either 01h
> >     or 03h unexpectedly (00h as expected data), which leads to
> >     program/erase failure on certain blocks.
> > 
> >     A workaround is given, (summary : issue a "Read Lock Status" before
> >     the "Lock" or "Unlock" command) which I have applied and tested
> >     with success.
> > 
> > Signed-off-by: Philippe De Muyter <phdm at macqel.be>
> 
> Is this Numonyx-specific issue? Should there be some kind of "if
> (numonyx)" statement?

This is clearly a bug specific to some Numonyx flashes.
My chips have Manufacturer ID: 0x89, Device ID: 0x881B, but there are
other chips in the same family.  The errata
http://www.numonyx.com/Documents/Specification%20Updates/509003_P3X_65nm_3V_256Mbit_Discrete.pdf does not list the ManufacturerIDs/DeviceIDs of the affected
chips.

Philippe

-- 
Philippe De Muyter  phdm at macqel dot be  Tel +32 27029044
Macq Electronique SA  rue de l'Aeronef 2  B-1140 Bruxelles  Fax +32 27029077