| Masahiro Yamada | c343b38 | 2014-10-03 19:21:03 +0900 | [diff] [blame] | 1 | menu "NAND Device Support" |
| 2 | |
| Masahiro Yamada | da0763d | 2014-11-13 20:31:50 +0900 | [diff] [blame] | 3 | config SYS_NAND_SELF_INIT |
| 4 | bool |
| 5 | help |
| 6 | This option, if enabled, provides more flexible and linux-like |
| 7 | NAND initialization process. |
| 8 | |
| Masahiro Yamada | c343b38 | 2014-10-03 19:21:03 +0900 | [diff] [blame] | 9 | config NAND_DENALI |
| 10 | bool "Support Denali NAND controller" |
| Masahiro Yamada | da0763d | 2014-11-13 20:31:50 +0900 | [diff] [blame] | 11 | select SYS_NAND_SELF_INIT |
| Masahiro Yamada | c343b38 | 2014-10-03 19:21:03 +0900 | [diff] [blame] | 12 | help |
| 13 | Enable support for the Denali NAND controller. |
| 14 | |
| 15 | config SYS_NAND_DENALI_64BIT |
| 16 | bool "Use 64-bit variant of Denali NAND controller" |
| 17 | depends on NAND_DENALI |
| 18 | help |
| 19 | The Denali NAND controller IP has some variations in terms of |
| 20 | the bus interface. The DMA setup sequence is completely differenct |
| 21 | between 32bit / 64bit AXI bus variants. |
| 22 | |
| 23 | If your Denali NAND controller is the 64-bit variant, say Y. |
| 24 | Otherwise (32 bit), say N. |
| 25 | |
| 26 | config NAND_DENALI_SPARE_AREA_SKIP_BYTES |
| 27 | int "Number of bytes skipped in OOB area" |
| 28 | depends on NAND_DENALI |
| 29 | range 0 63 |
| 30 | help |
| 31 | This option specifies the number of bytes to skip from the beginning |
| 32 | of OOB area before last ECC sector data starts. This is potentially |
| 33 | used to preserve the bad block marker in the OOB area. |
| 34 | |
| Stefan Agner | 6120f75 | 2015-05-08 19:07:11 +0200 | [diff] [blame^] | 35 | config NAND_VF610_NFC |
| 36 | bool "Support for Freescale NFC for VF610/MPC5125" |
| 37 | select SYS_NAND_SELF_INIT |
| 38 | help |
| 39 | Enables support for NAND Flash Controller on some Freescale |
| 40 | processors like the VF610, MPC5125, MCF54418 or Kinetis K70. |
| 41 | The driver supports a maximum 2k page size. The driver |
| 42 | currently does not support hardware ECC. |
| 43 | |
| 44 | comment "Generic NAND options" |
| 45 | |
| 46 | # Enhance depends when converting drivers to Kconfig which use this config |
| 47 | # option (mxc_nand, ndfc, omap_gpmc). |
| 48 | config SYS_NAND_BUSWIDTH_16BIT |
| 49 | bool "Use 16-bit NAND interface" |
| 50 | depends on NAND_VF610_NFC |
| 51 | help |
| 52 | Indicates that NAND device has 16-bit wide data-bus. In absence of this |
| 53 | config, bus-width of NAND device is assumed to be either 8-bit and later |
| 54 | determined by reading ONFI params. |
| 55 | Above config is useful when NAND device's bus-width information cannot |
| 56 | be determined from on-chip ONFI params, like in following scenarios: |
| 57 | - SPL boot does not support reading of ONFI parameters. This is done to |
| 58 | keep SPL code foot-print small. |
| 59 | - In current U-Boot flow using nand_init(), driver initialization |
| 60 | happens in board_nand_init() which is called before any device probe |
| 61 | (nand_scan_ident + nand_scan_tail), thus device's ONFI parameters are |
| 62 | not available while configuring controller. So a static CONFIG_NAND_xx |
| 63 | is needed to know the device's bus-width in advance. |
| 64 | |
| Masahiro Yamada | 72fb32b | 2015-02-24 22:26:20 +0900 | [diff] [blame] | 65 | if SPL |
| Masahiro Yamada | d182d54 | 2014-10-03 19:21:04 +0900 | [diff] [blame] | 66 | |
| 67 | config SPL_NAND_DENALI |
| 68 | bool "Support Denali NAND controller for SPL" |
| 69 | help |
| 70 | This is a small implementation of the Denali NAND controller |
| 71 | for use on SPL. |
| 72 | |
| 73 | endif |
| 74 | |
| Masahiro Yamada | c343b38 | 2014-10-03 19:21:03 +0900 | [diff] [blame] | 75 | endmenu |