Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1 | # drivers/mtd/nand/Kconfig |
Pete Popov | ef6f0d1 | 2005-09-23 02:44:58 +0100 | [diff] [blame^] | 2 | # $Id: Kconfig,v 1.34 2005/09/23 01:44:55 ppopov Exp $ |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 3 | |
| 4 | menu "NAND Flash Device Drivers" |
| 5 | depends on MTD!=n |
| 6 | |
| 7 | config MTD_NAND |
| 8 | tristate "NAND Device Support" |
| 9 | depends on MTD |
| 10 | select MTD_NAND_IDS |
| 11 | help |
| 12 | This enables support for accessing all type of NAND flash |
| 13 | devices. For further information see |
| 14 | <http://www.linux-mtd.infradead.org/tech/nand.html>. |
| 15 | |
| 16 | config MTD_NAND_VERIFY_WRITE |
| 17 | bool "Verify NAND page writes" |
| 18 | depends on MTD_NAND |
| 19 | help |
| 20 | This adds an extra check when data is written to the flash. The |
| 21 | NAND flash device internally checks only bits transitioning |
| 22 | from 1 to 0. There is a rare possibility that even though the |
| 23 | device thinks the write was successful, a bit could have been |
| 24 | flipped accidentaly due to device wear or something else. |
| 25 | |
| 26 | config MTD_NAND_AUTCPU12 |
| 27 | tristate "SmartMediaCard on autronix autcpu12 board" |
| 28 | depends on ARM && MTD_NAND && ARCH_AUTCPU12 |
| 29 | help |
| 30 | This enables the driver for the autronix autcpu12 board to |
| 31 | access the SmartMediaCard. |
| 32 | |
| 33 | config MTD_NAND_EDB7312 |
| 34 | tristate "Support for Cirrus Logic EBD7312 evaluation board" |
| 35 | depends on ARM && MTD_NAND && ARCH_EDB7312 |
| 36 | help |
| 37 | This enables the driver for the Cirrus Logic EBD7312 evaluation |
| 38 | board to access the onboard NAND Flash. |
| 39 | |
| 40 | config MTD_NAND_H1900 |
| 41 | tristate "iPAQ H1900 flash" |
| 42 | depends on ARM && MTD_NAND && ARCH_PXA && MTD_PARTITIONS |
| 43 | help |
| 44 | This enables the driver for the iPAQ h1900 flash. |
| 45 | |
| 46 | config MTD_NAND_SPIA |
| 47 | tristate "NAND Flash device on SPIA board" |
| 48 | depends on ARM && ARCH_P720T && MTD_NAND |
| 49 | help |
| 50 | If you had to ask, you don't have one. Say 'N'. |
| 51 | |
| 52 | config MTD_NAND_TOTO |
| 53 | tristate "NAND Flash device on TOTO board" |
| 54 | depends on ARM && ARCH_OMAP && MTD_NAND |
| 55 | help |
| 56 | Support for NAND flash on Texas Instruments Toto platform. |
| 57 | |
| 58 | config MTD_NAND_IDS |
| 59 | tristate |
| 60 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 61 | config MTD_NAND_AU1550 |
Pete Popov | ef6f0d1 | 2005-09-23 02:44:58 +0100 | [diff] [blame^] | 62 | tristate "Au1550/1200 NAND support" |
| 63 | depends on (SOC_AU1200 || SOC_AU1550) && MTD_NAND |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 64 | help |
| 65 | This enables the driver for the NAND flash controller on the |
| 66 | AMD/Alchemy 1550 SOC. |
| 67 | |
| 68 | config MTD_NAND_RTC_FROM4 |
| 69 | tristate "Renesas Flash ROM 4-slot interface board (FROM_BOARD4)" |
| 70 | depends on MTD_NAND && SH_SOLUTION_ENGINE |
| 71 | select REED_SOLOMON |
| 72 | select REED_SOLOMON_DEC8 |
| 73 | help |
| 74 | This enables the driver for the Renesas Technology AG-AND |
| 75 | flash interface board (FROM_BOARD4) |
| 76 | |
| 77 | config MTD_NAND_PPCHAMELEONEVB |
| 78 | tristate "NAND Flash device on PPChameleonEVB board" |
| 79 | depends on PPCHAMELEONEVB && MTD_NAND |
| 80 | help |
| 81 | This enables the NAND flash driver on the PPChameleon EVB Board. |
| 82 | |
| 83 | config MTD_NAND_S3C2410 |
Ben Dooks | a4f957f | 2005-06-20 12:48:25 +0100 | [diff] [blame] | 84 | tristate "NAND Flash support for S3C2410/S3C2440 SoC" |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 85 | depends on ARCH_S3C2410 && MTD_NAND |
| 86 | help |
Ben Dooks | a4f957f | 2005-06-20 12:48:25 +0100 | [diff] [blame] | 87 | This enables the NAND flash controller on the S3C2410 and S3C2440 |
| 88 | SoCs |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 89 | |
| 90 | No board specfic support is done by this driver, each board |
| 91 | must advertise a platform_device for the driver to attach. |
| 92 | |
| 93 | config MTD_NAND_S3C2410_DEBUG |
| 94 | bool "S3C2410 NAND driver debug" |
| 95 | depends on MTD_NAND_S3C2410 |
| 96 | help |
| 97 | Enable debugging of the S3C2410 NAND driver |
| 98 | |
| 99 | config MTD_NAND_S3C2410_HWECC |
| 100 | bool "S3C2410 NAND Hardware ECC" |
| 101 | depends on MTD_NAND_S3C2410 |
| 102 | help |
| 103 | Enable the use of the S3C2410's internal ECC generator when |
| 104 | using NAND. Early versions of the chip have had problems with |
| 105 | incorrect ECC generation, and if using these, the default of |
| 106 | software ECC is preferable. |
| 107 | |
| 108 | If you lay down a device with the hardware ECC, then you will |
| 109 | currently not be able to switch to software, as there is no |
| 110 | implementation for ECC method used by the S3C2410 |
| 111 | |
| 112 | config MTD_NAND_DISKONCHIP |
| 113 | tristate "DiskOnChip 2000, Millennium and Millennium Plus (NAND reimplementation) (EXPERIMENTAL)" |
| 114 | depends on MTD_NAND && EXPERIMENTAL |
| 115 | select REED_SOLOMON |
| 116 | select REED_SOLOMON_DEC16 |
| 117 | help |
| 118 | This is a reimplementation of M-Systems DiskOnChip 2000, |
| 119 | Millennium and Millennium Plus as a standard NAND device driver, |
| 120 | as opposed to the earlier self-contained MTD device drivers. |
| 121 | This should enable, among other things, proper JFFS2 operation on |
| 122 | these devices. |
| 123 | |
| 124 | config MTD_NAND_DISKONCHIP_PROBE_ADVANCED |
| 125 | bool "Advanced detection options for DiskOnChip" |
| 126 | depends on MTD_NAND_DISKONCHIP |
| 127 | help |
| 128 | This option allows you to specify nonstandard address at which to |
| 129 | probe for a DiskOnChip, or to change the detection options. You |
| 130 | are unlikely to need any of this unless you are using LinuxBIOS. |
| 131 | Say 'N'. |
| 132 | |
| 133 | config MTD_NAND_DISKONCHIP_PROBE_ADDRESS |
| 134 | hex "Physical address of DiskOnChip" if MTD_NAND_DISKONCHIP_PROBE_ADVANCED |
| 135 | depends on MTD_NAND_DISKONCHIP |
| 136 | default "0" |
| 137 | ---help--- |
| 138 | By default, the probe for DiskOnChip devices will look for a |
| 139 | DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000. |
| 140 | This option allows you to specify a single address at which to probe |
| 141 | for the device, which is useful if you have other devices in that |
| 142 | range which get upset when they are probed. |
| 143 | |
| 144 | (Note that on PowerPC, the normal probe will only check at |
| 145 | 0xE4000000.) |
| 146 | |
| 147 | Normally, you should leave this set to zero, to allow the probe at |
| 148 | the normal addresses. |
| 149 | |
| 150 | config MTD_NAND_DISKONCHIP_PROBE_HIGH |
| 151 | bool "Probe high addresses" |
| 152 | depends on MTD_NAND_DISKONCHIP_PROBE_ADVANCED |
| 153 | help |
| 154 | By default, the probe for DiskOnChip devices will look for a |
| 155 | DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000. |
| 156 | This option changes to make it probe between 0xFFFC8000 and |
| 157 | 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be |
| 158 | useful to you. Say 'N'. |
| 159 | |
| 160 | config MTD_NAND_DISKONCHIP_BBTWRITE |
| 161 | bool "Allow BBT writes on DiskOnChip Millennium and 2000TSOP" |
| 162 | depends on MTD_NAND_DISKONCHIP |
| 163 | help |
| 164 | On DiskOnChip devices shipped with the INFTL filesystem (Millennium |
| 165 | and 2000 TSOP/Alon), Linux reserves some space at the end of the |
| 166 | device for the Bad Block Table (BBT). If you have existing INFTL |
| 167 | data on your device (created by non-Linux tools such as M-Systems' |
| 168 | DOS drivers), your data might overlap the area Linux wants to use for |
| 169 | the BBT. If this is a concern for you, leave this option disabled and |
| 170 | Linux will not write BBT data into this area. |
| 171 | The downside of leaving this option disabled is that if bad blocks |
| 172 | are detected by Linux, they will not be recorded in the BBT, which |
| 173 | could cause future problems. |
| 174 | Once you enable this option, new filesystems (INFTL or others, created |
| 175 | in Linux or other operating systems) will not use the reserved area. |
| 176 | The only reason not to enable this option is to prevent damage to |
| 177 | preexisting filesystems. |
| 178 | Even if you leave this disabled, you can enable BBT writes at module |
| 179 | load time (assuming you build diskonchip as a module) with the module |
| 180 | parameter "inftl_bbt_write=1". |
| 181 | |
| 182 | config MTD_NAND_SHARPSL |
| 183 | bool "Support for NAND Flash on Sharp SL Series (C7xx + others)" |
| 184 | depends on MTD_NAND && ARCH_PXA |
| 185 | |
| 186 | config MTD_NAND_NANDSIM |
| 187 | bool "Support for NAND Flash Simulator" |
| 188 | depends on MTD_NAND && MTD_PARTITIONS |
| 189 | |
| 190 | help |
| 191 | The simulator may simulate verious NAND flash chips for the |
| 192 | MTD nand layer. |
| 193 | |
| 194 | endmenu |