xref: /openbmc/u-boot/drivers/mtd/nand/Kconfig (revision 29b103c7)
1menu "NAND Device Support"
2
3config SYS_NAND_SELF_INIT
4	bool
5	help
6	  This option, if enabled, provides more flexible and linux-like
7	  NAND initialization process.
8
9config NAND_DENALI
10	bool "Support Denali NAND controller"
11	select SYS_NAND_SELF_INIT
12	help
13	  Enable support for the Denali NAND controller.
14
15config 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
26config 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
35config 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
44choice
45	prompt "Hardware ECC strength"
46	depends on NAND_VF610_NFC
47	default SYS_NAND_VF610_NFC_45_ECC_BYTES
48	help
49	  Select the ECC strength used in the hardware BCH ECC block.
50
51config SYS_NAND_VF610_NFC_45_ECC_BYTES
52	bool "24-error correction (45 ECC bytes)"
53
54config SYS_NAND_VF610_NFC_60_ECC_BYTES
55	bool "32-error correction (60 ECC bytes)"
56
57endchoice
58
59comment "Generic NAND options"
60
61# Enhance depends when converting drivers to Kconfig which use this config
62# option (mxc_nand, ndfc, omap_gpmc).
63config SYS_NAND_BUSWIDTH_16BIT
64	bool "Use 16-bit NAND interface"
65	depends on NAND_VF610_NFC
66	help
67	  Indicates that NAND device has 16-bit wide data-bus. In absence of this
68	  config, bus-width of NAND device is assumed to be either 8-bit and later
69	  determined by reading ONFI params.
70	  Above config is useful when NAND device's bus-width information cannot
71	  be determined from on-chip ONFI params, like in following scenarios:
72	  - SPL boot does not support reading of ONFI parameters. This is done to
73	    keep SPL code foot-print small.
74	  - In current U-Boot flow using nand_init(), driver initialization
75	    happens in board_nand_init() which is called before any device probe
76	    (nand_scan_ident + nand_scan_tail), thus device's ONFI parameters are
77	    not available while configuring controller. So a static CONFIG_NAND_xx
78	    is needed to know the device's bus-width in advance.
79
80if SPL
81
82config SPL_NAND_DENALI
83	bool "Support Denali NAND controller for SPL"
84	help
85	  This is a small implementation of the Denali NAND controller
86	  for use on SPL.
87
88endif
89
90endmenu
91