git://bbs.cooldavid.org / net-next-2.6.git / blame
| Commit | Line | Data |
|---|---|---|
| cd5f6346 KP |
1 | # |
| 2 | # linux/drivers/mtd/onenand/Kconfig | |
| 3 | # | |
| 4 | ||
| 5 | menu "OneNAND Flash Device Drivers (EXPERIMENTAL)" | |
| 6 | depends on MTD != n && EXPERIMENTAL | |
| 7 | ||
| 8 | config MTD_ONENAND | |
| 9 | tristate "OneNAND Device Support" | |
| 10 | depends on MTD | |
| 11 | help | |
| 12 | This enables support for accessing all type of OneNAND flash | |
| 13 | devices. For further information see | |
| 14 | <http://www.samsung.com/Products/Semiconductor/Flash/OneNAND_TM/index.htm>. | |
| 15 | ||
| 16 | config MTD_ONENAND_VERIFY_WRITE | |
| 17 | bool "Verify OneNAND page writes" | |
| 18 | depends on MTD_ONENAND | |
| 19 | help | |
| 20 | This adds an extra check when data is written to the flash. The | |
| 21 | OneNAND 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_ONENAND_OMAP | |
| 27 | tristate "OneNAND Flash device on OMAP board" | |
| 28 | depends on ARCH_OMAP && MTD_ONENAND | |
| 29 | help | |
| 30 | Support for OneNAND flash on TI OMAP board. | |
| 31 | ||
| 52b0eea7 KP |
32 | config MTD_ONENAND_SYNC_READ |
| 33 | bool "OneNAND Sync. Burst Read Support" | |
| 34 | depends on ARCH_OMAP | |
| 35 | help | |
| 36 | This enables support for Sync. Burst Read. | |
| 37 | ||
| 405c829f KP |
38 | config MTD_ONENAND_SIM |
| 39 | tristate "Support for OneNAND flash simulator" | |
| 40 | depends on MTD_ONENAND | |
| 41 | help | |
| 42 | The simulator may simulate verious OneNAND flash chips for the | |
| 43 | MTD onenand layer. | |
| 44 | ||
| cd5f6346 | 45 | endmenu |