xref: /rk3399_rockchip-uboot/drivers/mtd/nand/Kconfig (revision 46c3d471e4068d3d77f85f98c1cb91c009ce56cc)
1
2menuconfig NAND
3	bool "NAND Device Support"
4if NAND
5
6config SYS_NAND_SELF_INIT
7	bool
8	help
9	  This option, if enabled, provides more flexible and linux-like
10	  NAND initialization process.
11
12config NAND_DENALI
13	bool
14	select SYS_NAND_SELF_INIT
15	imply CMD_NAND
16
17config NAND_DENALI_DT
18	bool "Support Denali NAND controller as a DT device"
19	select NAND_DENALI
20	depends on OF_CONTROL && DM
21	help
22	  Enable the driver for NAND flash on platforms using a Denali NAND
23	  controller as a DT device.
24
25config NAND_DENALI_SPARE_AREA_SKIP_BYTES
26	int "Number of bytes skipped in OOB area"
27	depends on NAND_DENALI
28	range 0 63
29	help
30	  This option specifies the number of bytes to skip from the beginning
31	  of OOB area before last ECC sector data starts.  This is potentially
32	  used to preserve the bad block marker in the OOB area.
33
34config NAND_OMAP_GPMC
35	bool "Support OMAP GPMC NAND controller"
36	depends on ARCH_OMAP2PLUS
37	help
38	  Enables omap_gpmc.c driver for OMAPx and AMxxxx platforms.
39	  GPMC controller is used for parallel NAND flash devices, and can
40	  do ECC calculation (not ECC error detection) for HAM1, BCH4, BCH8
41	  and BCH16 ECC algorithms.
42
43config NAND_OMAP_GPMC_PREFETCH
44	bool "Enable GPMC Prefetch"
45	depends on NAND_OMAP_GPMC
46	default y
47	help
48	  On OMAP platforms that use the GPMC controller
49	  (CONFIG_NAND_OMAP_GPMC_PREFETCH), this options enables the code that
50	  uses the prefetch mode to speed up read operations.
51
52config NAND_OMAP_ELM
53	bool "Enable ELM driver for OMAPxx and AMxx platforms."
54	depends on NAND_OMAP_GPMC && !OMAP34XX
55	help
56	  ELM controller is used for ECC error detection (not ECC calculation)
57	  of BCH4, BCH8 and BCH16 ECC algorithms.
58	  Some legacy platforms like OMAP3xx do not have in-built ELM h/w engine,
59	  thus such SoC platforms need to depend on software library for ECC error
60	  detection. However ECC calculation on such plaforms would still be
61	  done by GPMC controller.
62
63config NAND_VF610_NFC
64	bool "Support for Freescale NFC for VF610"
65	select SYS_NAND_SELF_INIT
66	imply CMD_NAND
67	help
68	  Enables support for NAND Flash Controller on some Freescale
69	  processors like the VF610, MCF54418 or Kinetis K70.
70	  The driver supports a maximum 2k page size. The driver
71	  currently does not support hardware ECC.
72
73choice
74	prompt "Hardware ECC strength"
75	depends on NAND_VF610_NFC
76	default SYS_NAND_VF610_NFC_45_ECC_BYTES
77	help
78	  Select the ECC strength used in the hardware BCH ECC block.
79
80config SYS_NAND_VF610_NFC_45_ECC_BYTES
81	bool "24-error correction (45 ECC bytes)"
82
83config SYS_NAND_VF610_NFC_60_ECC_BYTES
84	bool "32-error correction (60 ECC bytes)"
85
86endchoice
87
88config NAND_PXA3XX
89	bool "Support for NAND on PXA3xx and Armada 370/XP/38x"
90	select SYS_NAND_SELF_INIT
91	imply CMD_NAND
92	help
93	  This enables the driver for the NAND flash device found on
94	  PXA3xx processors (NFCv1) and also on Armada 370/XP (NFCv2).
95
96config NAND_ROCKCHIP
97	bool "Support for NAND on Rockchip SoCs"
98	select SYS_NAND_SELF_INIT
99	default n
100	---help---
101	Enable support for Rockchip nand.
102
103config NAND_ROCKCHIP_V9
104	bool "Support for NAND V9 on Rockchip SoCs"
105	select SYS_NAND_SELF_INIT
106	default n
107	---help---
108	Enable support for Rockchip nand v9.
109
110if NAND_ROCKCHIP || NAND_ROCKCHIP_V9
111config NAND_ROCKCHIP_DT
112        bool "Support Rockchip NAND controller as a DT device"
113	default y
114        help
115          Enable the driver for Rockchip NAND flash on platforms
116	  using device tree.
117endif
118
119config NAND_SUNXI
120	bool "Support for NAND on Allwinner SoCs"
121	default ARCH_SUNXI
122	depends on MACH_SUN4I || MACH_SUN5I || MACH_SUN7I || MACH_SUN8I
123	select SYS_NAND_SELF_INIT
124	select SYS_NAND_U_BOOT_LOCATIONS
125	select SPL_NAND_SUPPORT
126	imply CMD_NAND
127	---help---
128	Enable support for NAND. This option enables the standard and
129	SPL drivers.
130	The SPL driver only supports reading from the NAND using DMA
131	transfers.
132
133if NAND_SUNXI
134
135config NAND_SUNXI_SPL_ECC_STRENGTH
136	int "Allwinner NAND SPL ECC Strength"
137	default 64
138
139config NAND_SUNXI_SPL_ECC_SIZE
140	int "Allwinner NAND SPL ECC Step Size"
141	default 1024
142
143config NAND_SUNXI_SPL_USABLE_PAGE_SIZE
144	int "Allwinner NAND SPL Usable Page Size"
145	default 1024
146
147endif
148
149config NAND_ARASAN
150	bool "Configure Arasan Nand"
151	select SYS_NAND_SELF_INIT
152	imply CMD_NAND
153	help
154	  This enables Nand driver support for Arasan nand flash
155	  controller. This uses the hardware ECC for read and
156	  write operations.
157
158config NAND_MXC
159	bool "MXC NAND support"
160	depends on CPU_ARM926EJS || CPU_ARM1136 || MX5
161	imply CMD_NAND
162	help
163	  This enables the NAND driver for the NAND flash controller on the
164	  i.MX27 / i.MX31 / i.MX5 rocessors.
165
166config NAND_MXS
167	bool "MXS NAND support"
168	depends on MX23 || MX28 || MX6 || MX7
169	select SYS_NAND_SELF_INIT
170	imply CMD_NAND
171	select APBH_DMA
172	select APBH_DMA_BURST if ARCH_MX6 || ARCH_MX7
173	select APBH_DMA_BURST8 if ARCH_MX6 || ARCH_MX7
174	help
175	  This enables NAND driver for the NAND flash controller on the
176	  MXS processors.
177
178if NAND_MXS
179
180config NAND_MXS_DT
181	bool "Support MXS NAND controller as a DT device"
182	depends on OF_CONTROL && MTD
183	help
184	  Enable the driver for MXS NAND flash on platforms using
185	  device tree.
186
187config NAND_MXS_USE_MINIMUM_ECC
188	bool "Use minimum ECC strength supported by the controller"
189	default false
190
191endif
192
193config NAND_ZYNQ
194	bool "Support for Zynq Nand controller"
195	select SYS_NAND_SELF_INIT
196	imply CMD_NAND
197	help
198	  This enables Nand driver support for Nand flash controller
199	  found on Zynq SoC.
200
201config NAND_ZYNQ_USE_BOOTLOADER1_TIMINGS
202	bool "Enable use of 1st stage bootloader timing for NAND"
203	depends on NAND_ZYNQ
204	help
205	  This flag prevent U-boot reconfigure NAND flash controller and reuse
206	  the NAND timing from 1st stage bootloader.
207
208comment "Generic NAND options"
209
210config SYS_NAND_BLOCK_SIZE
211	hex "NAND chip eraseblock size"
212	depends on ARCH_SUNXI
213	help
214	  Number of data bytes in one eraseblock for the NAND chip on the
215	  board. This is the multiple of NAND_PAGE_SIZE and the number of
216	  pages.
217
218config SYS_NAND_PAGE_SIZE
219	hex "NAND chip page size"
220	depends on ARCH_SUNXI
221	help
222	  Number of data bytes in one page for the NAND chip on the
223	  board, not including the OOB area.
224
225config SYS_NAND_OOBSIZE
226	hex "NAND chip OOB size"
227	depends on ARCH_SUNXI
228	help
229	  Number of bytes in the Out-Of-Band area for the NAND chip on
230	  the board.
231
232# Enhance depends when converting drivers to Kconfig which use this config
233# option (mxc_nand, ndfc, omap_gpmc).
234config SYS_NAND_BUSWIDTH_16BIT
235	bool "Use 16-bit NAND interface"
236	depends on NAND_VF610_NFC || NAND_OMAP_GPMC || NAND_MXC || ARCH_DAVINCI
237	help
238	  Indicates that NAND device has 16-bit wide data-bus. In absence of this
239	  config, bus-width of NAND device is assumed to be either 8-bit and later
240	  determined by reading ONFI params.
241	  Above config is useful when NAND device's bus-width information cannot
242	  be determined from on-chip ONFI params, like in following scenarios:
243	  - SPL boot does not support reading of ONFI parameters. This is done to
244	    keep SPL code foot-print small.
245	  - In current U-Boot flow using nand_init(), driver initialization
246	    happens in board_nand_init() which is called before any device probe
247	    (nand_scan_ident + nand_scan_tail), thus device's ONFI parameters are
248	    not available while configuring controller. So a static CONFIG_NAND_xx
249	    is needed to know the device's bus-width in advance.
250
251if SPL
252
253config SYS_NAND_U_BOOT_LOCATIONS
254	bool "Define U-boot binaries locations in NAND"
255	help
256	Enable CONFIG_SYS_NAND_U_BOOT_OFFS though Kconfig.
257	This option should not be enabled when compiling U-boot for boards
258	defining CONFIG_SYS_NAND_U_BOOT_OFFS in their include/configs/<board>.h
259	file.
260
261config SYS_NAND_U_BOOT_OFFS
262	hex "Location in NAND to read U-Boot from"
263	default 0x800000 if NAND_SUNXI
264	depends on SYS_NAND_U_BOOT_LOCATIONS
265	help
266	Set the offset from the start of the nand where u-boot should be
267	loaded from.
268
269config SYS_NAND_U_BOOT_OFFS_REDUND
270	hex "Location in NAND to read U-Boot from"
271	default SYS_NAND_U_BOOT_OFFS
272	depends on SYS_NAND_U_BOOT_LOCATIONS
273	help
274	Set the offset from the start of the nand where the redundant u-boot
275	should be loaded from.
276
277config SPL_NAND_AM33XX_BCH
278	bool "Enables SPL-NAND driver which supports ELM based"
279	depends on NAND_OMAP_GPMC && !OMAP34XX
280	default y
281        help
282	  Hardware ECC correction. This is useful for platforms which have ELM
283	  hardware engine and use NAND boot mode.
284	  Some legacy platforms like OMAP3xx do not have in-built ELM h/w engine,
285	  so those platforms should use CONFIG_SPL_NAND_SIMPLE for enabling
286          SPL-NAND driver with software ECC correction support.
287
288config SPL_NAND_DENALI
289	bool "Support Denali NAND controller for SPL"
290	help
291	  This is a small implementation of the Denali NAND controller
292	  for use on SPL.
293
294config SPL_NAND_SIMPLE
295	bool "Use simple SPL NAND driver"
296	depends on !SPL_NAND_AM33XX_BCH
297	help
298	  Support for NAND boot using simple NAND drivers that
299	  expose the cmd_ctrl() interface.
300endif
301
302endif   # if NAND
303