summaryrefslogtreecommitdiff
path: root/drivers
diff options
context:
space:
mode:
authorMike Dunn <mikedunn@newsguy.com>2012-04-25 23:06:05 +0400
committerDavid Woodhouse <David.Woodhouse@intel.com>2012-05-14 08:09:58 +0400
commit86c2072be6f3c2150cc35f00233f2c31bdba2745 (patch)
tree56cfadbee0ea04a9436009743d5954ca447ebd96 /drivers
parent09cbe581e346229e33c48da00439419ff2fe6af7 (diff)
downloadlinux-86c2072be6f3c2150cc35f00233f2c31bdba2745.tar.xz
mtd: ecc_strength is at ecc step granularity
ecc_strength element of mtd_info will be the strength of one ecc step, not of the entire writesize, as was previously planned. This is the appropriate way because, as was pointed out¹, bit errors in excess of the strength of one step can cause a hard error if they all occur within the same ecc region. ¹ http://lists.infradead.org/pipermail/linux-mtd/2012-March/040313.html Signed-off-by: Mike Dunn <mikedunn@newsguy.com> Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com> Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
Diffstat (limited to 'drivers')
-rw-r--r--drivers/mtd/nand/nand_base.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/mtd/nand/nand_base.c b/drivers/mtd/nand/nand_base.c
index 512066e3d143..671f228d4c7c 100644
--- a/drivers/mtd/nand/nand_base.c
+++ b/drivers/mtd/nand/nand_base.c
@@ -3487,7 +3487,7 @@ int nand_scan_tail(struct mtd_info *mtd)
/* propagate ecc info to mtd_info */
mtd->ecclayout = chip->ecc.layout;
- mtd->ecc_strength = chip->ecc.strength * chip->ecc.steps;
+ mtd->ecc_strength = chip->ecc.strength;
/* Check, if we should skip the bad block table scan */
if (chip->options & NAND_SKIP_BBTSCAN)