summaryrefslogtreecommitdiff
path: root/drivers
diff options
context:
space:
mode:
authorArtem Bityutskiy <artem.bityutskiy@linux.intel.com>2012-02-03 10:14:12 +0200
committerDavid Woodhouse <David.Woodhouse@intel.com>2012-03-27 00:23:13 +0100
commit81fefdf2efa599df9e8b362bb04d5fe5a83bc353 (patch)
treed43699f05336dc5c5c0ef2e5b60c074fba32e76d /drivers
parentfcc44a07dae0af16e84e93425fc8afe642ddc603 (diff)
downloadlinux-3.10-81fefdf2efa599df9e8b362bb04d5fe5a83bc353.tar.gz
linux-3.10-81fefdf2efa599df9e8b362bb04d5fe5a83bc353.tar.bz2
linux-3.10-81fefdf2efa599df9e8b362bb04d5fe5a83bc353.zip
mtd: spear_smi: 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 the flash page size because it is the maximum amount of data it writes at a time. Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com> Acked-by: Stefan Roese <sr@denx.de> Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
Diffstat (limited to 'drivers')
-rw-r--r--drivers/mtd/devices/spear_smi.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/mtd/devices/spear_smi.c b/drivers/mtd/devices/spear_smi.c
index 5f425425464..b80cb5b5ebb 100644
--- a/drivers/mtd/devices/spear_smi.c
+++ b/drivers/mtd/devices/spear_smi.c
@@ -845,6 +845,7 @@ static int spear_smi_setup_banks(struct platform_device *pdev, u32 bank)
flash->mtd.size = flash_info->size;
flash->mtd.erasesize = flash_devices[flash_index].sectorsize;
flash->page_size = flash_devices[flash_index].pagesize;
+ flash->mtd.writebufsize = flash->page_size;
flash->erase_cmd = flash_devices[flash_index].erase_cmd;
flash->mtd._erase = spear_mtd_erase;
flash->mtd._read = spear_mtd_read;