Lines Matching full:bad
424 use bad block tables on FLASH, because the ECC layout is interfering
425 with the bad block marker positions. See bad block table support for
428 Bad block table support
431 Most NAND chips mark the bad blocks at a defined position in the spare
432 area. Those blocks must not be erased under any circumstances as the bad
433 block information would be lost. It is possible to check the bad block
435 the first page in the block. This is time consuming so a bad block table
438 The nand driver supports various types of bad block tables.
442 The bad block table contains all bad block information of the device
447 A bad block table is used per chip and contains the bad block
452 The bad block table is located at a fixed offset in the chip
457 The bad block table is automatically placed and detected either at
462 The bad block table is mirrored on the chip (device) to allow updates
463 of the bad block table without data loss.
466 nand_default_bbt() selects appropriate default bad block table
470 The standard policy is scanning the device for bad blocks and build a
471 ram based bad block table which allows faster access than always
472 checking the bad block information on the flash chip itself.
477 It may be desired or necessary to keep a bad block table in FLASH. For
478 AG-AND chips this is mandatory, as they have no factory marked bad
482 added to the bad blocks. Therefore we scan the chip(s) when we detect
483 them the first time for good blocks and store this information in a bad
487 accidental access by marking them bad in the memory bad block table. The
488 bad block table management functions are allowed to circumvent this
491 The simplest way to activate the FLASH based bad block table support is
494 this done by default. This activates the default FLASH based bad block
495 table functionality of the NAND driver. The default bad block table
498 - Store bad block table per chip
529 Setting the constant NAND_BBT_PERCHIP selects that a bad block
531 set then a per device bad block table is used.
536 page number where the bad block table starts in the field pages. If
537 you have selected bad block tables per chip and you have a multi chip
545 of the chip (device). Set NAND_BBT_LASTBLOCK to place the bad block
546 table at the end of the chip (device). The bad block tables are
548 of the first page in the block which holds the bad block table. Store
552 For mirrored bad block tables different patterns are mandatory.
563 This allows the update of the bad block table(s) in case a block has
564 to be marked bad due to wear. The MTD interface function
565 block_markbad is calling the update function of the bad block table.
575 with write support. It makes sure that the risk of losing the bad
577 about the one worn out block which should be marked bad. The version
580 the bad block table descriptor.
584 In case that the block which holds the bad block table does contain
586 the bad block table is written then the whole block is read the bad
588 written back. If this option is not set only the bad block table is
593 For automatic placement some blocks must be reserved for bad block
595 maxblocks member of the bad block table description structure.
597 This also limits the number of blocks which are scanned for the bad
704 0x05 Bad block marker If any bit in this byte is zero, then this
705 block is bad. This applies only to the first
728 0x05 Bad block marker If any bit in this byte is zero, then this
729 block is bad. This applies only to the first
745 0x00 Bad block marker If any bit in this byte is zero, then this block
746 is bad. This applies only to the first page in a
922 Bad block table related constants
925 These constants describe the options used for bad block table
928 /* Options for the bad block table descriptors */
936 /* The bad block table is in the last good block of the device */