diff options
| author | Tom Rini <[email protected]> | 2015-05-24 21:01:30 -0400 |
|---|---|---|
| committer | Tom Rini <[email protected]> | 2015-05-24 21:01:30 -0400 |
| commit | 980267a1445b7b4d8e8d05ef57799d92ba4a2ee3 (patch) | |
| tree | f24b717abe1c7bfedc74507e10d2fde540518ad6 /doc | |
| parent | a84988c76d1dbca2dbe870d6b4f0ad398f287f85 (diff) | |
| parent | 8fca2d8cb84fb039bb41061f5f5fd9f31cd596c9 (diff) | |
Merge git://git.denx.de/u-boot-nand-flash
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/README.nand | 18 |
1 files changed, 0 insertions, 18 deletions
diff --git a/doc/README.nand b/doc/README.nand index 46d7edd179f..0ff56331d5f 100644 --- a/doc/README.nand +++ b/doc/README.nand @@ -188,24 +188,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 ========================= |