2007-04-20 04:21:41 +07:00
|
|
|
menuconfig MTD_ONENAND
|
2005-07-11 17:41:53 +07:00
|
|
|
tristate "OneNAND Device Support"
|
|
|
|
|
depends on MTD
|
2012-02-07 07:22:50 +07:00
|
|
|
depends on HAS_IOMEM
|
2005-07-11 17:41:53 +07:00
|
|
|
help
|
|
|
|
|
This enables support for accessing all type of OneNAND flash
|
|
|
|
|
devices. For further information see
|
2007-04-25 17:05:48 +07:00
|
|
|
<http://www.samsung.com/Products/Semiconductor/OneNAND/index.htm>
|
2005-07-11 17:41:53 +07:00
|
|
|
|
2007-04-20 04:21:41 +07:00
|
|
|
if MTD_ONENAND
|
|
|
|
|
|
2005-07-11 17:41:53 +07:00
|
|
|
config MTD_ONENAND_VERIFY_WRITE
|
|
|
|
|
bool "Verify OneNAND page writes"
|
|
|
|
|
help
|
|
|
|
|
This adds an extra check when data is written to the flash. The
|
|
|
|
|
OneNAND flash device internally checks only bits transitioning
|
|
|
|
|
from 1 to 0. There is a rare possibility that even though the
|
|
|
|
|
device thinks the write was successful, a bit could have been
|
2006-10-04 03:31:37 +07:00
|
|
|
flipped accidentally due to device wear or something else.
|
2005-07-11 17:41:53 +07:00
|
|
|
|
2005-09-09 13:39:50 +07:00
|
|
|
config MTD_ONENAND_GENERIC
|
2005-11-07 07:14:05 +07:00
|
|
|
tristate "OneNAND Flash device via platform device driver"
|
2005-09-09 13:39:50 +07:00
|
|
|
help
|
2005-11-07 07:14:05 +07:00
|
|
|
Support for OneNAND flash via platform device driver.
|
2005-09-09 13:39:50 +07:00
|
|
|
|
2008-08-06 14:08:46 +07:00
|
|
|
config MTD_ONENAND_OMAP2
|
|
|
|
|
tristate "OneNAND on OMAP2/OMAP3 support"
|
2010-06-08 20:48:22 +07:00
|
|
|
depends on ARCH_OMAP2 || ARCH_OMAP3
|
2008-08-06 14:08:46 +07:00
|
|
|
help
|
|
|
|
|
Support for a OneNAND flash device connected to an OMAP2/OMAP3 CPU
|
|
|
|
|
via the GPMC memory controller.
|
|
|
|
|
|
2010-04-28 22:46:49 +07:00
|
|
|
config MTD_ONENAND_SAMSUNG
|
|
|
|
|
tristate "OneNAND on Samsung SOC controller support"
|
2014-07-02 05:53:06 +07:00
|
|
|
depends on ARCH_S3C64XX || ARCH_S5PV210 || ARCH_EXYNOS4
|
2010-04-28 22:46:49 +07:00
|
|
|
help
|
2010-09-29 12:32:05 +07:00
|
|
|
Support for a OneNAND flash device connected to an Samsung SOC.
|
2014-07-02 05:53:06 +07:00
|
|
|
S3C64XX uses command mapping method.
|
2010-09-29 12:32:05 +07:00
|
|
|
S5PC110/S5PC210 use generic OneNAND method.
|
2010-04-28 22:46:49 +07:00
|
|
|
|
2006-05-12 21:03:07 +07:00
|
|
|
config MTD_ONENAND_OTP
|
|
|
|
|
bool "OneNAND OTP Support"
|
|
|
|
|
help
|
|
|
|
|
One Block of the NAND Flash Array memory is reserved as
|
|
|
|
|
a One-Time Programmable Block memory area.
|
|
|
|
|
Also, 1st Block of NAND Flash Array can be used as OTP.
|
|
|
|
|
|
|
|
|
|
The OTP block can be read, programmed and locked using the same
|
|
|
|
|
operations as any other NAND Flash Array memory block.
|
|
|
|
|
OTP block cannot be erased.
|
|
|
|
|
|
|
|
|
|
OTP block is fully-guaranteed to be a valid block.
|
|
|
|
|
|
[MTD] [OneNAND] 2X program support
The 2X Program is an extension of Program Operation.
Since the device is equipped with two DataRAMs, and two-plane NAND Flash
memory array, these two component enables simultaneous program of 4KiB.
Plane1 has only even blocks such as block0, block2, block4 while Plane2
has only odd blocks such as block1, block3, block5.
So MTD regards it as 4KiB page size and 256KiB block size
Now the following chips support it. (KFXXX16Q2M)
Demux: KFG2G16Q2M, KFH4G16Q2M, KFW8G16Q2M,
Mux: KFM2G16Q2M, KFN4G16Q2M,
And more recent chips
Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2007-06-30 11:57:49 +07:00
|
|
|
config MTD_ONENAND_2X_PROGRAM
|
|
|
|
|
bool "OneNAND 2X program support"
|
|
|
|
|
help
|
|
|
|
|
The 2X Program is an extension of Program Operation.
|
|
|
|
|
Since the device is equipped with two DataRAMs, and two-plane NAND
|
|
|
|
|
Flash memory array, these two component enables simultaneous program
|
|
|
|
|
of 4KiB. Plane1 has only even blocks such as block0, block2, block4
|
|
|
|
|
while Plane2 has only odd blocks such as block1, block3, block5.
|
|
|
|
|
So MTD regards it as 4KiB page size and 256KiB block size
|
|
|
|
|
|
|
|
|
|
Now the following chips support it. (KFXXX16Q2M)
|
|
|
|
|
Demux: KFG2G16Q2M, KFH4G16Q2M, KFW8G16Q2M,
|
|
|
|
|
Mux: KFM2G16Q2M, KFN4G16Q2M,
|
|
|
|
|
|
|
|
|
|
And more recent chips
|
|
|
|
|
|
2007-04-20 04:21:41 +07:00
|
|
|
endif # MTD_ONENAND
|
