aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/mtd/devices
diff options
context:
space:
mode:
authorArtem Bityutskiy <artem.bityutskiy@linux.intel.com>2012-02-03 02:53:28 -0500
committerDavid Woodhouse <David.Woodhouse@intel.com>2012-03-26 19:23:01 -0400
commitfcc44a07dae0af16e84e93425fc8afe642ddc603 (patch)
treeb68fd1dd9a87c8996d511f62b89faf95f7e2414b /drivers/mtd/devices
parent82c4c58d6f1a78e8de875272a19ab9220b8066aa (diff)
mtd: lart: 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 writebufsize to 4 because this drivers writes at max 4 bytes 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>
Diffstat (limited to 'drivers/mtd/devices')
-rw-r--r--drivers/mtd/devices/lart.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/mtd/devices/lart.c b/drivers/mtd/devices/lart.c
index a59584871af5..6d6502c2ec35 100644
--- a/drivers/mtd/devices/lart.c
+++ b/drivers/mtd/devices/lart.c
@@ -630,6 +630,7 @@ static int __init lart_flash_init (void)
630 mtd.name = module_name; 630 mtd.name = module_name;
631 mtd.type = MTD_NORFLASH; 631 mtd.type = MTD_NORFLASH;
632 mtd.writesize = 1; 632 mtd.writesize = 1;
633 mtd.writebufsize = 4;
633 mtd.flags = MTD_CAP_NORFLASH; 634 mtd.flags = MTD_CAP_NORFLASH;
634 mtd.size = FLASH_BLOCKSIZE_PARAM * FLASH_NUMBLOCKS_16m_PARAM + FLASH_BLOCKSIZE_MAIN * FLASH_NUMBLOCKS_16m_MAIN; 635 mtd.size = FLASH_BLOCKSIZE_PARAM * FLASH_NUMBLOCKS_16m_PARAM + FLASH_BLOCKSIZE_MAIN * FLASH_NUMBLOCKS_16m_MAIN;
635 mtd.erasesize = FLASH_BLOCKSIZE_MAIN; 636 mtd.erasesize = FLASH_BLOCKSIZE_MAIN;