summaryrefslogtreecommitdiffstats
path: root/common/imx-bbu-nand-fcb.c
diff options
context:
space:
mode:
authorSascha Hauer <s.hauer@pengutronix.de>2016-02-25 12:16:29 +0100
committerSascha Hauer <s.hauer@pengutronix.de>2016-03-04 08:27:34 +0100
commitb14ed856c37d81b48edbec3720c510b86f5d556c (patch)
treeccfe7d305c9537beb110bc2f1da5e5ab235c3001 /common/imx-bbu-nand-fcb.c
parent568e345d5acb380bdd25012f751d7c6eeef27699 (diff)
downloadbarebox-b14ed856c37d81b48edbec3720c510b86f5d556c.tar.gz
barebox-b14ed856c37d81b48edbec3720c510b86f5d556c.tar.xz
mtd: nand: default bitflip-reporting threshold to 75% of correction strength
Based on Kernel commit 240181fd0ffa6 from Brian Norris: The MTD API reports -EUCLEAN only if the maximum number of bitflips found in any ECC block exceeds a certain threshold. This is done to avoid excessive -EUCLEAN reports to MTD users, which may induce additional scrubbing of data, even when the ECC algorithm in use is perfectly capable of handling the bitflips. This threshold can be controlled by user-space (via sysfs), to allow users to determine what they are willing to tolerate in their application. But it still helps to have sane defaults. In recent discussion [1], it was pointed out that our default threshold is equal to the correction strength. That means that we won't actually report any -EUCLEAN (i.e., "bitflips were corrected") errors until there are almost too many to handle. It was determined that 3/4 of the correction strength is probably a better default. [1] http://lists.infradead.org/pipermail/linux-mtd/2015-January/057259.html Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Diffstat (limited to 'common/imx-bbu-nand-fcb.c')
0 files changed, 0 insertions, 0 deletions