Frieder Schrempf bfd15c904a mtd: onenand: Store bad block marker position in chip struct ... The information about where the manufacturer puts the bad block markers inside the bad block and in the OOB data is stored in different places. Let's move this information to the chip struct, as we did it for rawnand. Signed-off-by: Frieder Schrempf <frieder.schrempf@kontron.de> Reviewed-by: Miquel Raynal <miquel.raynal@bootlin.com> Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>		2019-04-18 08:54:07 +02:00
..
onenand	mtd: onenand: Store bad block marker position in chip struct	2019-04-18 08:54:07 +02:00
raw	mtd: rawnand: Always store info about bad block markers in chip struct	2019-04-18 08:54:07 +02:00
spi	mtd: spinand: Implement mtd->_max_bad_blocks	2019-04-08 10:21:10 +02:00
bbt.c	mtd: nand: Fix memory allocation in nanddev_bbt_init()	2018-11-28 15:41:50 +01:00
core.c	mtd: nand: Add max_bad_eraseblocks_per_lun info to memorg	2019-04-08 10:21:08 +02:00
Kconfig	mtd: nand: Remove useless line in Kconfig	2019-04-18 08:54:01 +02:00
Makefile	mtd: nand: Add core infrastructure to support SPI NANDs	2018-07-18 09:24:10 +02:00