Home Explore Help
Register Sign In
phyus
/
linux-vybrid_public
8
0
Fork 0
Files Issues 0 Pull Requests 0 Wiki
Tree: ab1363a892
Branches Tags
linux-vybrid_pu...
/
drivers
/
mtd
/
onenand
/
Kconfig

Kconfig 2.3 KB
History Raw

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374 
  1. #
    2. 

  2. # linux/drivers/mtd/onenand/Kconfig
    3. 

  3. #
    4. 

  4. 

  5. menuconfig MTD_ONENAND
    6. 

  6. 	tristate "OneNAND Device Support"
    7. 

  7. 	depends on MTD
    8. 

  8. 	help
    9. 

  9. 	  This enables support for accessing all type of OneNAND flash
    10. 

  10. 	  devices. For further information see
    11. 

  11. 	  <http://www.samsung.com/Products/Semiconductor/OneNAND/index.htm>
    12. 

  12. 

  13. if MTD_ONENAND
    14. 

  14. 

  15. config MTD_ONENAND_VERIFY_WRITE
    16. 

  16. 	bool "Verify OneNAND page writes"
    17. 

  17. 	help
    18. 

  18. 	  This adds an extra check when data is written to the flash. The
    19. 

  19. 	  OneNAND flash device internally checks only bits transitioning
    20. 

  20. 	  from 1 to 0. There is a rare possibility that even though the
    21. 

  21. 	  device thinks the write was successful, a bit could have been
    22. 

  22. 	  flipped accidentally due to device wear or something else.
    23. 

  23. 

  24. config MTD_ONENAND_GENERIC
    25. 

  25. 	tristate "OneNAND Flash device via platform device driver"
    26. 

  26. 	depends on ARM
    27. 

  27. 	help
    28. 

  28. 	  Support for OneNAND flash via platform device driver.
    29. 

  29. 

  30. config MTD_ONENAND_OMAP2
    31. 

  31. 	tristate "OneNAND on OMAP2/OMAP3 support"
    32. 

  32. 	depends on MTD_ONENAND && (ARCH_OMAP2 || ARCH_OMAP3)
    33. 

  33. 	help
    34. 

  34. 	  Support for a OneNAND flash device connected to an OMAP2/OMAP3 CPU
    35. 

  35. 	  via the GPMC memory controller.
    36. 

  36. 

  37. config MTD_ONENAND_OTP
    38. 

  38. 	bool "OneNAND OTP Support"
    39. 

  39. 	select HAVE_MTD_OTP
    40. 

  40. 	help
    41. 

  41. 	  One Block of the NAND Flash Array memory is reserved as
    42. 

  42. 	  a One-Time Programmable Block memory area.
    43. 

  43. 	  Also, 1st Block of NAND Flash Array can be used as OTP.
    44. 

  44. 

  45. 	  The OTP block can be read, programmed and locked using the same
    46. 

  46. 	  operations as any other NAND Flash Array memory block.
    47. 

  47. 	  OTP block cannot be erased.
    48. 

  48. 

  49. 	  OTP block is fully-guaranteed to be a valid block.
    50. 

  50. 

  51. config MTD_ONENAND_2X_PROGRAM
    52. 

  52. 	bool "OneNAND 2X program support"
    53. 

  53. 	help
    54. 

  54. 	  The 2X Program is an extension of Program Operation.
    55. 

  55. 	  Since the device is equipped with two DataRAMs, and two-plane NAND
    56. 

  56. 	  Flash memory array, these two component enables simultaneous program
    57. 

  57. 	  of 4KiB. Plane1 has only even blocks such as block0, block2, block4
    58. 

  58. 	  while Plane2 has only odd blocks such as block1, block3, block5.
    59. 

  59. 	  So MTD regards it as 4KiB page size and 256KiB block size
    60. 

  60. 

  61. 	  Now the following chips support it. (KFXXX16Q2M)
    62. 

  62. 	    Demux: KFG2G16Q2M, KFH4G16Q2M, KFW8G16Q2M,
    63. 

  63. 	    Mux:   KFM2G16Q2M, KFN4G16Q2M,
    64. 

  64. 

  65. 	  And more recent chips
    66. 

  66. 

  67. config MTD_ONENAND_SIM
    68. 

  68. 	tristate "OneNAND simulator support"
    69. 

  69. 	depends on MTD_PARTITIONS
    70. 

  70. 	help
    71. 

  71. 	  The simulator may simulate various OneNAND flash chips for the
    72. 

  72. 	  OneNAND MTD layer.
    73. 

  73. 

  74. endif # MTD_ONENAND
    75.