On 09:08 Mon 15 Oct , Sascha Hauer wrote: > On Sun, Oct 14, 2012 at 10:49:23PM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote: > > from linux 3.6 > > > > Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@xxxxxxxxxxxx> > > --- > > drivers/mtd/devices/Kconfig | 18 + > > drivers/mtd/devices/Makefile | 1 + > > drivers/mtd/devices/mtd_dataflash.c | 882 +++++++++++++++++++++++++++++++++++ > > include/spi/flash.h | 2 +- > > 4 files changed, 902 insertions(+), 1 deletion(-) > > create mode 100644 drivers/mtd/devices/mtd_dataflash.c > > > > diff --git a/drivers/mtd/devices/Kconfig b/drivers/mtd/devices/Kconfig > > index e6d747c..e956921 100644 > > --- a/drivers/mtd/devices/Kconfig > > +++ b/drivers/mtd/devices/Kconfig > > @@ -1,6 +1,24 @@ > > menu "Self contained MTD devices" > > depends on MTD!=n > > > > +config MTD_DATAFLASH > > + tristate "Support for AT45xxx DataFlash" > > + depends on SPI > > + help > > + This enables access to AT45xxx DataFlash chips, using SPI. > > + Sometimes DataFlash chips are packaged inside MMC-format > > + cards; at this writing, the MMC stack won't handle those. > > + > > +config MTD_DATAFLASH_WRITE_VERIFY > > + bool "Verify DataFlash page writes" > > + depends on MTD_DATAFLASH > > + help > > + This adds an extra check when data is written to the flash. > > + It may help if you are verifying chip setup (timings etc) on > > + your board. There is a rare possibility that even though the > > + device thinks the write was successful, a bit could have been > > + flipped accidentally due to device wear or something else. > > + > > What about MTD_DATAFLASH_OTP? the DATAFLASH_OTP need the MTD to have the OTP support which we do not have yet do I did not add it Best Regards, J. _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
