summaryrefslogtreecommitdiff
path: root/nand_spl
diff options
context:
space:
mode:
authorMarek Vasut <marex@denx.de>2012-08-30 17:39:38 +0400
committerScott Wood <scottwood@freescale.com>2012-09-18 03:54:43 +0400
commit9c790a748f6b61e36f7aaf0c8d5ed35c9b09f454 (patch)
tree918986d51e2675d7977e4399040ad50c0730dd41 /nand_spl
parente70bfa2986f9c028e3c21e0995285047a9baec27 (diff)
downloadu-boot-9c790a748f6b61e36f7aaf0c8d5ed35c9b09f454.tar.xz
mtd: nand: allow NAND_NO_SUBPAGE_WRITE to be set from driver
This is based on Linux kernel -next: commit 14f44abf1dafc20ba42ce8616a8fc8fbd1b3712b Author: Brian Norris <computersforpeace@gmail.com> Date: Fri Jul 13 09:28:24 2012 -0700 mtd: nand: allow NAND_NO_SUBPAGE_WRITE to be set from driver The NAND_CHIPOPTIONS_MSK has limited utility and is causing real bugs. It silently masks off at least one flag that might be set by the driver (NAND_NO_SUBPAGE_WRITE). This breaks the GPMI NAND driver and possibly others. Really, as long as driver writers exercise a small amount of care with NAND_* options, this mask is not necessary at all; it was only here to prevent certain options from accidentally being set by the driver. But the original thought turns out to be a bad idea occasionally. Thus, kill it. Note, this patch fixes some major gpmi-nand breakage. Signed-off-by: Marek Vasut <marex@denx.de> Cc: Brian Norris <computersforpeace@gmail.com> Cc: Eric Nelson <eric.nelson@boundarydevices.com> Cc: Fabio Estevam <festevam@gmail.com> Cc: Otavio Salvador <otavio@ossystems.com.br> Cc: Scott Wood <scottwood@freescale.com> Signed-off-by: Scott Wood <scottwood@freescale.com>
Diffstat (limited to 'nand_spl')
0 files changed, 0 insertions, 0 deletions