]> git.ipfire.org Git - people/ms/u-boot.git/blob - drivers/mtd/nand/Kconfig
sunxi_nand_spl: Auto detect nand configuration parameters
[people/ms/u-boot.git] / drivers / mtd / nand / Kconfig
1 menu "NAND Device Support"
2
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
9 config 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
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
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 choice
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
51 config SYS_NAND_VF610_NFC_45_ECC_BYTES
52 bool "24-error correction (45 ECC bytes)"
53
54 config SYS_NAND_VF610_NFC_60_ECC_BYTES
55 bool "32-error correction (60 ECC bytes)"
56
57 endchoice
58
59 config NAND_PXA3XX
60 bool "Support for NAND on PXA3xx and Armada 370/XP/38x"
61 select SYS_NAND_SELF_INIT
62 help
63 This enables the driver for the NAND flash device found on
64 PXA3xx processors (NFCv1) and also on Armada 370/XP (NFCv2).
65
66 comment "Generic NAND options"
67
68 # Enhance depends when converting drivers to Kconfig which use this config
69 # option (mxc_nand, ndfc, omap_gpmc).
70 config SYS_NAND_BUSWIDTH_16BIT
71 bool "Use 16-bit NAND interface"
72 depends on NAND_VF610_NFC
73 help
74 Indicates that NAND device has 16-bit wide data-bus. In absence of this
75 config, bus-width of NAND device is assumed to be either 8-bit and later
76 determined by reading ONFI params.
77 Above config is useful when NAND device's bus-width information cannot
78 be determined from on-chip ONFI params, like in following scenarios:
79 - SPL boot does not support reading of ONFI parameters. This is done to
80 keep SPL code foot-print small.
81 - In current U-Boot flow using nand_init(), driver initialization
82 happens in board_nand_init() which is called before any device probe
83 (nand_scan_ident + nand_scan_tail), thus device's ONFI parameters are
84 not available while configuring controller. So a static CONFIG_NAND_xx
85 is needed to know the device's bus-width in advance.
86
87 if SPL
88
89 config SPL_NAND_DENALI
90 bool "Support Denali NAND controller for SPL"
91 help
92 This is a small implementation of the Denali NAND controller
93 for use on SPL.
94
95 config SPL_NAND_SUNXI
96 bool "Support for NAND on Allwinner SoCs in SPL"
97 depends on MACH_SUN4I || MACH_SUN5I || MACH_SUN7I
98 select SYS_NAND_SELF_INIT
99 ---help---
100 Enable support for NAND. This option allows SPL to read from
101 sunxi NAND using DMA transfers.
102
103 config NAND_SUNXI_SPL_SYNDROME_PARTITIONS_END
104 hex "Size of syndrome partitions in sunxi NAND"
105 default 0x400000
106 depends on SPL_NAND_SUNXI
107 ---help---
108 End address for boot partitions on NAND. Those partitions have a
109 different random seed that has to match the sunxi BROM setting.
110
111 endif
112
113 endmenu