summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorArtem Bityutskiy <artem.bityutskiy@linux.intel.com>2012-02-03 09:43:14 +0200
committerDavid Woodhouse <David.Woodhouse@intel.com>2012-03-27 00:22:51 +0100
commit71f60fbebf0f18dd4e855335a009efda251b1697 (patch)
tree79b75244fb752132d78fd08bb35d3907adbbb28f
parentcca84b569ebe3372b28949e00b0a3a17f87e2970 (diff)
downloadop-kernel-dev-71f60fbebf0f18dd4e855335a009efda251b1697.zip
op-kernel-dev-71f60fbebf0f18dd4e855335a009efda251b1697.tar.gz
mtd: doc2001plus: initialize writebufsize
The writebufsize concept was introduce by commit "0e4ca7e mtd: add writebufsize field to mtd_info struct" and it represents the maximum amount of data the device writes to the media at a time. This is an important parameter for UBIFS which is used during recovery and which basically defines how big a corruption caused by a power cut can be. Set it to be equivalent to mtd->writesize because this is the maximum amount of data the driver writes at a time. Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com> Cc: stable@kernel.org [2.6.38+] Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
-rw-r--r--drivers/mtd/devices/doc2001plus.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/mtd/devices/doc2001plus.c b/drivers/mtd/devices/doc2001plus.c
index 409fa31..c9fbadd 100644
--- a/drivers/mtd/devices/doc2001plus.c
+++ b/drivers/mtd/devices/doc2001plus.c
@@ -467,7 +467,7 @@ void DoCMilPlus_init(struct mtd_info *mtd)
mtd->type = MTD_NANDFLASH;
mtd->flags = MTD_CAP_NANDFLASH;
- mtd->writesize = 512;
+ mtd->writebufsize = mtd->writesize = 512;
mtd->oobsize = 16;
mtd->owner = THIS_MODULE;
mtd->_erase = doc_erase;
OpenPOWER on IntegriCloud