linux/mtd/bbm.h

1 /* SPDX-License-Identifier: GPL-2.0-or-later */
3  *  NAND family Bad Block Management (BBM) header file
4  *    - Bad Block Table (BBT) implementation
9  *  Copyright © 2000-2005
15 /* The maximum number of NAND chips in an array */
19  * struct nand_bbt_descr - bad block table descriptor
21  * @pages:	the page(s) where we find the bbt, used with option BBT_ABSPAGE
22  *		when bbt is searched, then we store the found bbts pages here.
25  * @veroffs:	offset of the bbt version counter in the oob are of the page
26  * @version:	version read from the bbt page during scan
28  * @maxblocks:	maximum number of blocks to search for a bbt. This number of
31  * @reserved_block_code: if non-0, this pattern denotes a reserved (rather than
32  *              bad) block in the stored bbt
55 /* The number of bits used per block in the bbt on the device */
63 /* The bbt is at the given page, else we must scan for the bbt */
65 /* bbt is stored per chip on multichip devices */
67 /* bbt has a version counter at offset veroffs */
69 /* Create a bbt if none exists */
72  * Create an empty BBT with no vendor information. Vendor's information may be
73  * unavailable, for example, if the NAND controller has a different data and OOB
78 /* Write bbt if neccecary */
80 /* Read and write back block contents when writing bbt */
84  * Use a flash based bad block table. By default, OOB identifier is saved in
89  * Do not store flash based bad block table marker in the OOB area; store it
90  * in-band.
106 /* The maximum number of blocks to scan for a bbt */
117  * struct bbm_info - [GENERIC] Bad Block Table data structure
118  * @bbt_erase_shift:	[INTERN] number of address bits in a bbt entry
120  * @bbt:		[INTERN] bad block table pointer
130 	uint8_t *bbt;  member
134 	/* TODO Add more NAND specific fileds */
140 /* OneNAND BBT interface */