Lines Matching full:bad
422 use bad block tables on FLASH, because the ECC layout is interfering
423 with the bad block marker positions. See bad block table support for
426 Bad block table support
429 Most NAND chips mark the bad blocks at a defined position in the spare
430 area. Those blocks must not be erased under any circumstances as the bad
431 block information would be lost. It is possible to check the bad block
433 the first page in the block. This is time consuming so a bad block table
436 The nand driver supports various types of bad block tables.
440 The bad block table contains all bad block information of the device
445 A bad block table is used per chip and contains the bad block
450 The bad block table is located at a fixed offset in the chip
455 The bad block table is automatically placed and detected either at
460 The bad block table is mirrored on the chip (device) to allow updates
461 of the bad block table without data loss.
464 nand_default_bbt() selects appropriate default bad block table
468 The standard policy is scanning the device for bad blocks and build a
469 ram based bad block table which allows faster access than always
470 checking the bad block information on the flash chip itself.
475 It may be desired or necessary to keep a bad block table in FLASH. For
476 AG-AND chips this is mandatory, as they have no factory marked bad
480 added to the bad blocks. Therefore we scan the chip(s) when we detect
481 them the first time for good blocks and store this information in a bad
485 accidental access by marking them bad in the memory bad block table. The
486 bad block table management functions are allowed to circumvent this
489 The simplest way to activate the FLASH based bad block table support is
492 this done by default. This activates the default FLASH based bad block
493 table functionality of the NAND driver. The default bad block table
496 - Store bad block table per chip
527 Setting the constant NAND_BBT_PERCHIP selects that a bad block
529 set then a per device bad block table is used.
534 page number where the bad block table starts in the field pages. If
535 you have selected bad block tables per chip and you have a multi chip
543 of the chip (device). Set NAND_BBT_LASTBLOCK to place the bad block
544 table at the end of the chip (device). The bad block tables are
546 of the first page in the block which holds the bad block table. Store
550 For mirrored bad block tables different patterns are mandatory.
561 This allows the update of the bad block table(s) in case a block has
562 to be marked bad due to wear. The MTD interface function
563 block_markbad is calling the update function of the bad block table.
573 with write support. It makes sure that the risk of losing the bad
575 about the one worn out block which should be marked bad. The version
578 the bad block table descriptor.
582 In case that the block which holds the bad block table does contain
584 the bad block table is written then the whole block is read the bad
586 written back. If this option is not set only the bad block table is
591 For automatic placement some blocks must be reserved for bad block
593 maxblocks member of the bad block table description structure.
595 This also limits the number of blocks which are scanned for the bad
702 0x05 Bad block marker If any bit in this byte is zero, then this
703 block is bad. This applies only to the first
726 0x05 Bad block marker If any bit in this byte is zero, then this
727 block is bad. This applies only to the first
743 0x00 Bad block marker If any bit in this byte is zero, then this block
744 is bad. This applies only to the first page in a
920 Bad block table related constants
923 These constants describe the options used for bad block table
926 /* Options for the bad block table descriptors */
934 /* The bad block table is in the last good block of the device */