summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVipin Kumar <vipin.kumar@st.com>2012-03-14 11:47:12 +0530
committerDavid Woodhouse <David.Woodhouse@intel.com>2012-03-27 00:59:02 +0100
commit467e6e7be2e26fd5bbaabd849717d37de99df8f1 (patch)
treedbb1b570db775fcc35b76e7c010fd0e267aec26b
parentb533f8d84f4f0807bf1bcf52017c6a267c8c4405 (diff)
downloadop-kernel-dev-467e6e7be2e26fd5bbaabd849717d37de99df8f1.zip
op-kernel-dev-467e6e7be2e26fd5bbaabd849717d37de99df8f1.tar.gz
mtd: nand/fsmc: Initialize the badblockbits to 7
Ideally, the block should have 0xff written on the bad block position. Any value other than 0xff implies a bad block. In practical situations, there can be bit flips in the oob area as well which means that a block with 0x7f being read at bad block position may imply a bad block but it is infact only a bit flip in the bad block byte. To resolve this problem, the block is marked as good if number of high bits is greater than or equal to badblockbits (initialized to 7) Signed-off-by: Vipin Kumar <vipin.kumar@st.com> Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com> Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
-rw-r--r--drivers/mtd/nand/fsmc_nand.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/mtd/nand/fsmc_nand.c b/drivers/mtd/nand/fsmc_nand.c
index 6a0bca17..91f5b34 100644
--- a/drivers/mtd/nand/fsmc_nand.c
+++ b/drivers/mtd/nand/fsmc_nand.c
@@ -802,6 +802,7 @@ static int __init fsmc_nand_probe(struct platform_device *pdev)
nand->ecc.size = 512;
nand->options = pdata->options;
nand->select_chip = fsmc_select_chip;
+ nand->badblockbits = 7;
if (pdata->width == FSMC_NAND_BW16)
nand->options |= NAND_BUSWIDTH_16;
OpenPOWER on IntegriCloud