Merge branch 'master' of git://git.denx.de/u-boot-uniphier

[u-boot] / doc / README.nand

diff --git a/doc/README.nand b/doc/README.nand
index 46d7edd179f139bb9688bfe1557bd5cbbcc53daf..96ffc489408853729292bb1818e4af2c355c9df5 100644 (file)
--- a/doc/README.nand
+++ b/doc/README.nand
@@ -94,7 +94,7 @@ Configuration Options:
        address of u-boot MTD partition in NAND.
 
    CONFIG_CMD_NAND
-      Enables NAND support and commmands.
+      Enables NAND support and commands.
 
    CONFIG_CMD_NAND_TORTURE
       Enables the torture command (see description of this command below).
@@ -136,15 +136,8 @@ Configuration Options:
       Example of new init to be added to the end of an existing driver
       init:
 
-       /*
-        * devnum is the device number to be used in nand commands
-        * and in mtd->name.  Must be less than
-        * CONFIG_SYS_NAND_MAX_DEVICE.
-        */
-       mtd = &nand_info[devnum];
-
        /* chip is struct nand_chip, and is now provided by the driver. */
-       mtd->priv = &chip;
+       mtd = &chip.mtd;
 
        /*
         * Fill in appropriate values if this driver uses these fields,
@@ -165,7 +158,11 @@ Configuration Options:
        if (nand_scan_tail(mtd))
                error out
 
-       if (nand_register(devnum))
+       /*
+        * devnum is the device number to be used in nand commands
+        * and in mtd->name.  Must be less than CONFIG_SYS_NAND_MAX_DEVICE.
+        */
+       if (nand_register(devnum, mtd))
                error out
 
       In addition to providing more flexibility to the driver, it reduces
@@ -188,24 +185,6 @@ Configuration Options:
        This is used by SoC platforms which do not have built-in ELM
        hardware engine required for BCH ECC correction.
 
-   CONFIG_SYS_NAND_BUSWIDTH_16BIT
-       Indicates that NAND device has 16-bit wide data-bus. In absence of this
-       config, bus-width of NAND device is assumed to be either 8-bit and later
-       determined by reading ONFI params.
-       Above config is useful when NAND device's bus-width information cannot
-       be determined from on-chip ONFI params, like in following scenarios:
-       - SPL boot does not support reading of ONFI parameters. This is done to
-         keep SPL code foot-print small.
-       - In current U-Boot flow using nand_init(), driver initialization
-         happens in board_nand_init() which is called before any device probe
-         (nand_scan_ident + nand_scan_tail), thus device's ONFI parameters are
-         not available while configuring controller. So a static CONFIG_NAND_xx
-         is needed to know the device's bus-width in advance.
-       Some drivers using above config are:
-       drivers/mtd/nand/mxc_nand.c
-       drivers/mtd/nand/ndfc.c
-       drivers/mtd/nand/omap_gpmc.c
-
 
 Platform specific options
 =========================