Kyungmin Park | cd5f634 | 2005-07-11 11:41:53 +0100 | [diff] [blame] | 1 | # |
| 2 | # linux/drivers/mtd/onenand/Kconfig |
| 3 | # |
| 4 | |
Jan Engelhardt | ec98c68 | 2007-04-19 16:21:41 -0500 | [diff] [blame] | 5 | menuconfig MTD_ONENAND |
Kyungmin Park | cd5f634 | 2005-07-11 11:41:53 +0100 | [diff] [blame] | 6 | tristate "OneNAND Device Support" |
| 7 | depends on MTD |
| 8 | help |
| 9 | This enables support for accessing all type of OneNAND flash |
| 10 | devices. For further information see |
Kyungmin Park | c19df27 | 2007-04-25 11:05:48 +0100 | [diff] [blame] | 11 | <http://www.samsung.com/Products/Semiconductor/OneNAND/index.htm> |
Kyungmin Park | cd5f634 | 2005-07-11 11:41:53 +0100 | [diff] [blame] | 12 | |
Jan Engelhardt | ec98c68 | 2007-04-19 16:21:41 -0500 | [diff] [blame] | 13 | if MTD_ONENAND |
| 14 | |
Kyungmin Park | cd5f634 | 2005-07-11 11:41:53 +0100 | [diff] [blame] | 15 | config MTD_ONENAND_VERIFY_WRITE |
| 16 | bool "Verify OneNAND page writes" |
Kyungmin Park | cd5f634 | 2005-07-11 11:41:53 +0100 | [diff] [blame] | 17 | help |
| 18 | This adds an extra check when data is written to the flash. The |
| 19 | OneNAND flash device internally checks only bits transitioning |
| 20 | from 1 to 0. There is a rare possibility that even though the |
| 21 | device thinks the write was successful, a bit could have been |
Matt LaPlante | 0950960 | 2006-10-03 22:31:37 +0200 | [diff] [blame] | 22 | flipped accidentally due to device wear or something else. |
Kyungmin Park | cd5f634 | 2005-07-11 11:41:53 +0100 | [diff] [blame] | 23 | |
Kyungmin Park | 68ee4b1 | 2005-09-09 07:39:50 +0100 | [diff] [blame] | 24 | config MTD_ONENAND_GENERIC |
Thomas Gleixner | 46d0d0f | 2005-11-07 01:14:05 +0100 | [diff] [blame] | 25 | tristate "OneNAND Flash device via platform device driver" |
Jan Engelhardt | ec98c68 | 2007-04-19 16:21:41 -0500 | [diff] [blame] | 26 | depends on ARM |
Kyungmin Park | 68ee4b1 | 2005-09-09 07:39:50 +0100 | [diff] [blame] | 27 | help |
Thomas Gleixner | 46d0d0f | 2005-11-07 01:14:05 +0100 | [diff] [blame] | 28 | Support for OneNAND flash via platform device driver. |
Kyungmin Park | 68ee4b1 | 2005-09-09 07:39:50 +0100 | [diff] [blame] | 29 | |
Kyungmin Park | 493c646 | 2006-05-12 17:03:07 +0300 | [diff] [blame] | 30 | config MTD_ONENAND_OTP |
| 31 | bool "OneNAND OTP Support" |
Kyungmin Park | 493c646 | 2006-05-12 17:03:07 +0300 | [diff] [blame] | 32 | help |
| 33 | One Block of the NAND Flash Array memory is reserved as |
| 34 | a One-Time Programmable Block memory area. |
| 35 | Also, 1st Block of NAND Flash Array can be used as OTP. |
| 36 | |
| 37 | The OTP block can be read, programmed and locked using the same |
| 38 | operations as any other NAND Flash Array memory block. |
| 39 | OTP block cannot be erased. |
| 40 | |
| 41 | OTP block is fully-guaranteed to be a valid block. |
| 42 | |
Kyungmin Park | ee9745f | 2007-06-30 13:57:49 +0900 | [diff] [blame] | 43 | config MTD_ONENAND_2X_PROGRAM |
| 44 | bool "OneNAND 2X program support" |
| 45 | help |
| 46 | The 2X Program is an extension of Program Operation. |
| 47 | Since the device is equipped with two DataRAMs, and two-plane NAND |
| 48 | Flash memory array, these two component enables simultaneous program |
| 49 | of 4KiB. Plane1 has only even blocks such as block0, block2, block4 |
| 50 | while Plane2 has only odd blocks such as block1, block3, block5. |
| 51 | So MTD regards it as 4KiB page size and 256KiB block size |
| 52 | |
| 53 | Now the following chips support it. (KFXXX16Q2M) |
| 54 | Demux: KFG2G16Q2M, KFH4G16Q2M, KFW8G16Q2M, |
| 55 | Mux: KFM2G16Q2M, KFN4G16Q2M, |
| 56 | |
| 57 | And more recent chips |
| 58 | |
Kyungmin Park | 8dab169 | 2007-06-30 14:14:43 +0900 | [diff] [blame] | 59 | config MTD_ONENAND_SIM |
| 60 | tristate "OneNAND simulator support" |
| 61 | depends on MTD_PARTITIONS |
| 62 | help |
| 63 | The simulator may simulate various OneNAND flash chips for the |
| 64 | OneNAND MTD layer. |
| 65 | |
Jan Engelhardt | ec98c68 | 2007-04-19 16:21:41 -0500 | [diff] [blame] | 66 | endif # MTD_ONENAND |