On Wed, Jun 26, 2013 at 01:11:10PM +0530, Sourav Poddar wrote: > From: Mona Anonuevo <manonuevo@xxxxxxxxxx> > > This patch adds support for a generic spinand framework(spinand_mtd.c). > This frameowrk can be used for other spi based flash devices also. The idea > is to have a common model under drivers/mtd, as also present for other no spi > devices(there is a generic framework and device part simply attaches itself to it.) > > The generic frework will be used later by me for a SPI based spansion S25FL256 device. > The patch also contains a micron driver attaching itself to generic framework. > > Signed-off-by: Mona Anonuevo <manonuevo@xxxxxxxxxx> > Signed-off-by: Tuan Nguyen <tqnguyen@xxxxxxxxxx> > Signed-off-by: Sourav Poddar <sourav.poddar@xxxxxx> > ---- > [I picked this as a standalone patch, can split it into generic and device part > based on community feedback.] > > drivers/mtd/Kconfig | 2 + > drivers/mtd/Makefile | 2 + > drivers/mtd/spinand/Kconfig | 24 ++ > drivers/mtd/spinand/Makefile | 10 + > drivers/mtd/spinand/spinand_lld.c | 776 +++++++++++++++++++++++++++++++++++++ > drivers/mtd/spinand/spinand_mtd.c | 690 +++++++++++++++++++++++++++++++++ > include/linux/mtd/spinand.h | 155 ++++++++ > 7 files changed, 1659 insertions(+), 0 deletions(-) > create mode 100644 drivers/mtd/spinand/Kconfig > create mode 100644 drivers/mtd/spinand/Makefile > create mode 100644 drivers/mtd/spinand/spinand_lld.c > create mode 100644 drivers/mtd/spinand/spinand_mtd.c > create mode 100644 include/linux/mtd/spinand.h > I am working on Micron SPINAND(Micron MT29F1G01ZACH). I tried this patch, but it's not working. It is throwing following error message while mounting: [ 260.232000] jffs2: cannot read OOB for EB at 00000000, requested 8 bytes, read 0 bytes, error -22 mount: mounting /dev/mtdblock5 on /mnt/ failed: Input/output error I am working on it to fix into the driver, will send an updated patch with the fix. Thanks, Kamlakant Patel -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
