blob: 3a094d1bf8cce60e5c3a65835e1b35854412bf1b [file] [log] [blame]
Kyungmin Parkcd5f6342005-07-11 11:41:53 +01001#
2# linux/drivers/mtd/onenand/Kconfig
3#
4
Jan Engelhardtec98c682007-04-19 16:21:41 -05005menuconfig MTD_ONENAND
Kyungmin Parkcd5f6342005-07-11 11:41:53 +01006 tristate "OneNAND Device Support"
7 depends on MTD
Paul Mundt0acfe532009-08-07 12:34:48 +09008 select MTD_PARTITIONS
Kyungmin Parkcd5f6342005-07-11 11:41:53 +01009 help
10 This enables support for accessing all type of OneNAND flash
11 devices. For further information see
Kyungmin Parkc19df272007-04-25 11:05:48 +010012 <http://www.samsung.com/Products/Semiconductor/OneNAND/index.htm>
Kyungmin Parkcd5f6342005-07-11 11:41:53 +010013
Jan Engelhardtec98c682007-04-19 16:21:41 -050014if MTD_ONENAND
15
Kyungmin Parkcd5f6342005-07-11 11:41:53 +010016config MTD_ONENAND_VERIFY_WRITE
17 bool "Verify OneNAND page writes"
Kyungmin Parkcd5f6342005-07-11 11:41:53 +010018 help
19 This adds an extra check when data is written to the flash. The
20 OneNAND flash device internally checks only bits transitioning
21 from 1 to 0. There is a rare possibility that even though the
22 device thinks the write was successful, a bit could have been
Matt LaPlante09509602006-10-03 22:31:37 +020023 flipped accidentally due to device wear or something else.
Kyungmin Parkcd5f6342005-07-11 11:41:53 +010024
Kyungmin Park68ee4b12005-09-09 07:39:50 +010025config MTD_ONENAND_GENERIC
Thomas Gleixner46d0d0f2005-11-07 01:14:05 +010026 tristate "OneNAND Flash device via platform device driver"
Jan Engelhardtec98c682007-04-19 16:21:41 -050027 depends on ARM
Kyungmin Park68ee4b12005-09-09 07:39:50 +010028 help
Thomas Gleixner46d0d0f2005-11-07 01:14:05 +010029 Support for OneNAND flash via platform device driver.
Kyungmin Park68ee4b12005-09-09 07:39:50 +010030
Adrian Hunter36cd4fb2008-08-06 10:08:46 +030031config MTD_ONENAND_OMAP2
32 tristate "OneNAND on OMAP2/OMAP3 support"
33 depends on MTD_ONENAND && (ARCH_OMAP2 || ARCH_OMAP3)
34 help
35 Support for a OneNAND flash device connected to an OMAP2/OMAP3 CPU
36 via the GPMC memory controller.
37
Kyungmin Park493c6462006-05-12 17:03:07 +030038config MTD_ONENAND_OTP
39 bool "OneNAND OTP Support"
David Brownell34a82442008-07-30 12:35:05 -070040 select HAVE_MTD_OTP
Kyungmin Park493c6462006-05-12 17:03:07 +030041 help
42 One Block of the NAND Flash Array memory is reserved as
43 a One-Time Programmable Block memory area.
44 Also, 1st Block of NAND Flash Array can be used as OTP.
45
46 The OTP block can be read, programmed and locked using the same
47 operations as any other NAND Flash Array memory block.
48 OTP block cannot be erased.
49
50 OTP block is fully-guaranteed to be a valid block.
51
Kyungmin Parkee9745f2007-06-30 13:57:49 +090052config MTD_ONENAND_2X_PROGRAM
53 bool "OneNAND 2X program support"
54 help
55 The 2X Program is an extension of Program Operation.
56 Since the device is equipped with two DataRAMs, and two-plane NAND
57 Flash memory array, these two component enables simultaneous program
58 of 4KiB. Plane1 has only even blocks such as block0, block2, block4
59 while Plane2 has only odd blocks such as block1, block3, block5.
60 So MTD regards it as 4KiB page size and 256KiB block size
61
62 Now the following chips support it. (KFXXX16Q2M)
63 Demux: KFG2G16Q2M, KFH4G16Q2M, KFW8G16Q2M,
64 Mux: KFM2G16Q2M, KFN4G16Q2M,
65
66 And more recent chips
67
Kyungmin Park8dab1692007-06-30 14:14:43 +090068config MTD_ONENAND_SIM
69 tristate "OneNAND simulator support"
Kyungmin Park8dab1692007-06-30 14:14:43 +090070 help
71 The simulator may simulate various OneNAND flash chips for the
72 OneNAND MTD layer.
73
Jan Engelhardtec98c682007-04-19 16:21:41 -050074endif # MTD_ONENAND