Searched refs:badblock (Results 1 - 9 of 9) sorted by relevance

/linux-4.1.27/drivers/mtd/
H A Dmtdoops.c173 badblock: mtdoops_workfunc_erase()
207 goto badblock; mtdoops_workfunc_erase()
/linux-4.1.27/drivers/mtd/nand/
H A Ddocg4.c76 MODULE_PARM_DESC(ignore_badblocks, "no badblock checking performed");
219 * Bytes 0, 1 are used as badblock marker.
1066 int badblock = block + 7 - bitnum; read_factory_bbt() local
1067 nand->bbt[badblock / 4] |= read_factory_bbt()
1068 0x03 << ((badblock % 4) * 2); read_factory_bbt()
1071 badblock); read_factory_bbt()
H A Ddavinci_nand.c493 /* offset 5 holds the badblock marker */
516 /* 2 bytes at offset 0 hold manufacturer badblock markers */
785 * badblock marking data ... and make sure a flash BBT nand_davinci_probe()
/linux-4.1.27/include/uapi/linux/raid/
H A Dmd_p.h292 #define MD_FEATURE_BAD_BLOCKS 8 /* badblock list is not empty */
/linux-4.1.27/drivers/mtd/onenand/
H A Dsamsung.c897 /* Use runtime badblock check */ s3c_onenand_probe()
/linux-4.1.27/fs/jffs2/
H A Dwbuf.c1129 * or badblock list as long as nobody manipulates the flash with
/linux-4.1.27/drivers/md/
H A Dmd.h122 u64 *page; /* badblock list */
H A Draid10.c4637 /* FIXME should record badblock */ end_reshape_write()
H A Dmd.c8778 * Normally only a successful write may clear a badblock badblocks_store()

Completed in 365 milliseconds