From 5519194d4f6ba3c1aeea2f07f444cc936913560a Mon Sep 17 00:00:00 2001 From: Stefan Agner Date: Fri, 8 May 2015 19:07:11 +0200 Subject: mtd: vf610_nfc: add Freescale NFC controller configs to Kconfig This commit allows users to enable/disable the Freescale NFC controller found in systems like Vybrid (VF610), MPC5125, MCF54418 or Kinetis K70 via Kconfig with more detailed help docs. Signed-off-by: Stefan Agner Acked-by: Stefano Babic [scottwood: updated vf610twr_nand_defconfig] Signed-off-by: Scott Wood --- doc/README.nand | 18 ------------------ 1 file changed, 18 deletions(-) (limited to 'doc/README.nand') diff --git a/doc/README.nand b/doc/README.nand index 46d7edd179..0ff56331d5 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 ========================= -- cgit v1.2.3