summaryrefslogtreecommitdiff
path: root/arch/arm/mach-vt8500
diff options
context:
space:
mode:
authorBrian Norris <computersforpeace@gmail.com>2013-03-13 16:51:31 (GMT)
committerDavid Woodhouse <David.Woodhouse@intel.com>2013-03-14 12:48:54 (GMT)
commit5bc7c33ca93a285dcfe7b7fd64970f6314440ad1 (patch)
tree0ce80c4e6559c939c2eaf86c76950b177c4c157a /arch/arm/mach-vt8500
parent91d542f4dcc231749c36114ed8e26bb27d4521e4 (diff)
downloadlinux-fsl-qoriq-5bc7c33ca93a285dcfe7b7fd64970f6314440ad1.tar.xz
mtd: nand: reintroduce NAND_NO_READRDY as NAND_NEED_READRDY
This partially reverts commit 1696e6bc2ae83734e64e206ac99766ea19e9a14e ("mtd: nand: kill NAND_NO_READRDY"). In that patch 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. Cc: stable@kernel.org [3.5+] Reported-by: Alexander Shiyan <shc_work@mail.ru> Tested-by: Alexander Shiyan <shc_work@mail.ru> Signed-off-by: Brian Norris <computersforpeace@gmail.com> Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
Diffstat (limited to 'arch/arm/mach-vt8500')
0 files changed, 0 insertions, 0 deletions