Lines Matching +full:per +full:- +full:board
10 The generic NAND driver supports almost all NAND and AG-AND based chips
15 board drivers or filesystem drivers suitable for NAND devices.
31 --------------------------
37 - [MTD Interface]
43 - [NAND Interface]
48 - [GENERIC]
53 - [DEFAULT]
57 replaced by the board driver if necessary. Those functions are called
58 via pointers in the NAND chip description structure. The board driver
59 can set the functions which should be replaced by board dependent
65 -------------------------------
71 - [INTERN]
77 - [REPLACEABLE]
80 provided by the board driver. The board driver can set the functions
81 which should be replaced by board dependent functions before calling
86 - [BOARDSPECIFIC]
88 Board specific members hold hardware related information which must
89 be provided by the board driver. The board driver must set the
92 - [OPTIONAL]
94 Optional members can hold information relevant for the board driver.
97 Basic board driver
101 functions and fill out some really board dependent members in the nand
105 -------------
131 -----------------
134 partitioning scheme suitable to your board.
150 -------------------------
183 case NAND_CTL_SETCLE: this->IO_ADDR_W |= CLE_ADRR_BIT; break;
184 case NAND_CTL_CLRCLE: this->IO_ADDR_W &= ~CLE_ADRR_BIT; break;
185 case NAND_CTL_SETALE: this->IO_ADDR_W |= ALE_ADRR_BIT; break;
186 case NAND_CTL_CLRALE: this->IO_ADDR_W &= ~ALE_ADRR_BIT; break;
192 ---------------------
200 and the function pointer this->dev_ready is set to NULL.
203 -------------
205 The init function allocates memory and sets up all the board specific
223 err = -ENOMEM;
233 err = -EIO;
238 this->IO_ADDR_R = baseaddr;
239 this->IO_ADDR_W = baseaddr;
241 this->hwcontrol = board_hwcontrol;
243 this->chip_delay = CHIP_DEPENDEND_COMMAND_DELAY;
245 this->dev_ready = board_dev_ready;
246 this->eccmode = NAND_ECC_SOFT;
250 err = -ENXIO;
268 -------------
292 Advanced board driver functions
296 For a list of functions which can be overridden by the board driver see
300 ---------------------
302 The nand driver can control chip arrays. Therefore the board driver must
339 this->IO_ADDR_R &= ~BOARD_NAND_ADDR_MASK;
340 this->IO_ADDR_W &= ~BOARD_NAND_ADDR_MASK;
343 this->IO_ADDR_R |= BOARD_NAND_ADDR_CHIP0;
344 this->IO_ADDR_W |= BOARD_NAND_ADDR_CHIP0;
348 this->IO_ADDR_R |= BOARD_NAND_ADDR_CHIPn;
349 this->IO_ADDR_W |= BOARD_NAND_ADDR_CHIPn;
356 --------------------
363 - NAND_ECC_HW3_256
365 Hardware ECC generator providing 3 bytes ECC per 256 byte.
367 - NAND_ECC_HW3_512
369 Hardware ECC generator providing 3 bytes ECC per 512 byte.
371 - NAND_ECC_HW6_512
373 Hardware ECC generator providing 6 bytes ECC per 512 byte.
375 - NAND_ECC_HW8_512
377 Hardware ECC generator providing 8 bytes ECC per 512 byte.
382 The board driver must provide following functions:
384 - enable_hwecc
391 - calculate_ecc
398 - correct_data
402 corrected. If the error is not correctable return -1. If your
410 Many hardware ECC implementations provide Reed-Solomon codes and
412 standard Reed-Solomon syndrome before calling the error correction code
413 in the generic Reed-Solomon library.
420 code. Provide a matching oob-layout in this case. See rts_from4.c and
427 -----------------------
438 - Per device
443 - Per chip
445 A bad block table is used per chip and contains the bad block
448 - Fixed offset
453 - Automatic placed
458 - Mirrored tables
476 AG-AND chips this is mandatory, as they have no factory marked bad
491 nand chip structure before calling nand_scan(). For AG-AND chips is
496 - Store bad block table per chip
498 - Use 2 bits per block
500 - Automatic placement at the end of the chip
502 - Use mirrored tables with version numbers
504 - Reserve 4 blocks at the end of the chip
521 - Number of bits per block
525 - Table per chip
529 set then a per device bad block table is used.
531 - Table location is absolute
535 you have selected bad block tables per chip and you have a multi chip
540 - Table location is automatically detected
552 - Table creation
558 - Table write support
569 - Table version control
580 - Save block contents on write
589 - Number of reserved blocks
599 --------------------------
604 - Placement defined by fs driver
606 - Automatic placement
611 the board driver can provide a own placement scheme.
628 - useecc
631 file include/mtd/mtd-abi.h contains constants to select ecc and
637 - eccbytes
639 The eccbytes member defines the number of ecc bytes per page.
641 - eccpos
646 - oobfree
661 is (number of pages) \* ((size of spare area) + (number of ecc steps per
682 size per page is determined by the oobfree array in the nand_oobinfo
689 ----------------------------------------
734 0x08 - 0x0F Autoplace 0 - 7
748 0x02-0x27 Autoplace 0 - 37
808 it again, are restricted to 1-3 writes, depending on the manufacturers
824 - flasherase, flasheraseall: Erase and format FLASH partitions
826 - nandwrite: write filesystem images to NAND FLASH
828 - nanddump: dump the contents of a NAND FLASH partitions
841 ---------------------
846 These constants are defined in rawnand.h. They are OR-ed together to
868 These constants are defined in rawnand.h. They are OR-ed together to
873 * data bytes. Applies for DOC and AG-AND Renesas HW Reed Solomon generators */
878 -----------------------
884 /* Software ECC 3 byte ECC per 256 Byte data */
886 /* Hardware ECC 3 byte ECC per 256 Byte data */
888 /* Hardware ECC 3 byte ECC per 512 Byte data */
890 /* Hardware ECC 6 byte ECC per 512 Byte data */
892 /* Hardware ECC 8 byte ECC per 512 Byte data */
897 ----------------------------------
921 ---------------------------------
928 /* The number of bits used per block in the bbt on the device */
938 /* bbt is stored per chip on multichip devices */
959 .. kernel-doc:: include/linux/mtd/rawnand.h
970 .. kernel-doc:: drivers/mtd/nand/raw/nand_base.c
973 .. kernel-doc:: drivers/mtd/nand/raw/nand_ecc.c
983 relevant for a board driver developer.
985 .. kernel-doc:: drivers/mtd/nand/raw/nand_base.c
988 .. kernel-doc:: drivers/mtd/nand/raw/nand_bbt.c