Lines Matching full:table

425 with the bad block marker positions. See bad block table support for
428 Bad block table support
435 the first page in the block. This is time consuming so a bad block table
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
471 ram based bad block table which allows faster access than always
477 It may be desired or necessary to keep a bad block table in FLASH. For
484 block table before erasing any of the blocks.
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
495 table functionality of the NAND driver. The default bad block table
498 -  Store bad block table per chip
513 bbt_td before calling nand_scan(). If a mirror table is necessary a
516 is set to NULL then only the main table is used and no scan for the
517 mirrored table is performed.
520 options field. The options define most of the table properties. Use the
527 -  Table per chip
530    table is managed for each chip in a chip array. If this option is not
531    set then a per device bad block table is used.
533 -  Table location is absolute
536    page number where the bad block table starts in the field pages. If
539    array. Note: there is no scan for a table ident pattern performed, so
542 -  Table location is automatically detected
544    The table can either be located in the first or the last good blocks
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
554 -  Table creation
556    Set the option NAND_BBT_CREATE to enable the table creation if no
557    table can be found during the scan. Usually this is done only once if
560 -  Table write support
562    Set the option NAND_BBT_WRITE to enable the table write support.
563    This allows the update of the bad block table(s) in case a block has
565    block_markbad is calling the update function of the bad block table.
566    If the write support is enabled then the table is updated on FLASH.
571 -  Table version control
573    Set the option NAND_BBT_VERSION to enable the table version
576    block table information is reduced to the loss of the information
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
587    block table is updated and the block is erased and everything is
588    written back. If this option is not set only the bad block table is
594    table storage. The number of reserved blocks is defined in the
595    maxblocks member of the bad block table description structure.
598    block table ident pattern.
845 Constants for chip id table
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 */