Re: [RFC "v2"] mtd: nand: reintroduce NAND_NO_READRDY as NAND_NEED_READRDY

Alexander Shiyan shc_work at mail.ru
Wed Mar 13 13:17:58 EDT 2013


Hello.

> This (somewhat) reverts commit 1696e6bc2ae83734e64e206ac99766ea19e9a14e.
> 
> In the patch "mtd: nand: kill NAND_NO_READRDY", I overlooked a few
> things.
> 
> The original documentation for NAND_NO_READRDY included "True for all
> large page devices, as they do not support autoincrement." I was
> conflating "not support autoincrement" with the NAND_NO_AUTOINCR option,
> which was in fact doing nothing. So, when I dropped NAND_NO_AUTOINCR, I
> concluded that I then could harmlessly drop NAND_NO_READRDY. But of
> course the fact the NAND_NO_AUTOINCR was doing nothing didn't mean
> NAND_NO_READRDY was doing nothing...
> 
> So, NAND_NO_READRDY is re-introduced as NAND_NEED_READRDY and applied
> only to those few remaining small-page NAND which needed it in the first
> place.
> 
> This is probably a candidate for stable, but there will certainly be
> conflicts, as drivers/mtd/nand/nand_ids.c has changed significantly.
> 
> Compile-tested only; I don't have a setup that requires this.
> 
> Reported-by: Alexander Shiyan <shc_work at mail.ru>
> Signed-off-by: Brian Norris <computersforpeace at gmail.com>

Thanks. I will check this version tomorrow.

---


More information about the linux-mtd mailing list