nand/raw/nand_base.c

311  * nand_block_bad - [DEFAULT] Read bad block marker from the chip
315  * Check, if the block is bad.
321 	u16 bad;
332 			bad = cpu_to_le16(chip->read_word(mtd));
334 				bad >>= 8;
336 				bad &= 0xFF;
340 			bad = chip->read_byte(mtd);
344 			res = bad != 0xFF;
346 			res = hweight8(bad) < chip->badblockbits;
356  * nand_default_block_markbad - [DEFAULT] mark a block bad via bad block marker
361  * specific driver. It provides the details for writing a bad block marker to a
398  * nand_block_markbad_lowlevel - mark a block bad
402  * This function performs the generic NAND bad block marking steps (i.e., bad
404  * specify how to write bad block markers to OOB (chip->block_markbad).
408  *  (2) write bad block marker to OOB area of affected block (unless flag
432 		/* Write bad block marker to OOB */
439 	/* Mark block bad in BBT */
500  * nand_block_checkbad - [GENERIC] Check if a block is marked bad
505  * Check, if the block is bad. Either by reading the bad block table or
2068  * the data area, by overwriting the NAND manufacturer bad block markings.
3541 		/* Check if we have a bad block, we do not erase bad blocks! */
3544 			pr_warn("%s: attempt to erase a bad block at page 0x%08x\n",
3614  * nand_block_isbad - [MTD Interface] Check if block at offset is bad
3637  * nand_block_markbad - [MTD Interface] Mark block at the given offset as bad
3647 		/* If it was bad already, return success and do nothing */
4199  * Set the bad block marker/indicator (BBM/BBI) patterns according to some
4206 	/* Set the bad block position */
4905  * bad block table if appropriate.
4914 	/* New bad blocks should be marked in OOB, flash-based BBT, or both */