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

[Artem Bityutskiy]

On Thu, 2010-10-21 at 11:33 +0200, Philippe De Muyter wrote:
> 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.

CCed Nicolas correctly.

Anyway, if this affects only subset of chips, it make sense to make this
quirk conditional, because this might affect boot speed, e.g., if some
systems unlock all blocks on boot-up.

Nicolas, the original patch was here, would you validate it please?
http://lists.infradead.org/pipermail/linux-mtd/2010-October/032783.html

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)