Kconfig 4.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174
  1. if ARCH_S3C2410
  2. menu "S3C24XX Implementations"
  3. config ARCH_BAST
  4. bool "Simtec Electronics BAST (EB2410ITX)"
  5. select CPU_S3C2410
  6. help
  7. Say Y here if you are using the Simtec Electronics EB2410ITX
  8. development board (also known as BAST)
  9. Product page: <http://www.simtec.co.uk/products/EB2410ITX/>.
  10. config ARCH_H1940
  11. bool "IPAQ H1940"
  12. select CPU_S3C2410
  13. help
  14. Say Y here if you are using the HP IPAQ H1940
  15. <http://www.handhelds.org/projects/h1940.html>.
  16. config MACH_N30
  17. bool "Acer N30"
  18. select CPU_S3C2410
  19. help
  20. Say Y here if you are using the Acer N30
  21. <http://zoo.weinigel.se/n30>.
  22. config ARCH_SMDK2410
  23. bool "SMDK2410/A9M2410"
  24. select CPU_S3C2410
  25. help
  26. Say Y here if you are using the SMDK2410 or the derived module A9M2410
  27. <http://www.fsforth.de>
  28. config ARCH_S3C2440
  29. bool "SMDK2440"
  30. select CPU_S3C2440
  31. help
  32. Say Y here if you are using the SMDK2440.
  33. config MACH_VR1000
  34. bool "Thorcom VR1000"
  35. select CPU_S3C2410
  36. help
  37. Say Y here if you are using the Thorcom VR1000 board.
  38. This linux port is currently being maintained by Simtec, on behalf
  39. of Thorcom. Any queries, please contact Thorcom first.
  40. config MACH_RX3715
  41. bool "HP iPAQ rx3715"
  42. select CPU_S3C2440
  43. help
  44. Say Y here if you are using the HP iPAQ rx3715.
  45. See <http://www.handhelds.org/projects/rx3715.html> for more
  46. information on this project
  47. config MACH_OTOM
  48. bool "NexVision OTOM Board"
  49. select CPU_S3C2410
  50. help
  51. Say Y here if you are using the Nex Vision OTOM board
  52. config MACH_NEXCODER_2440
  53. bool "NexVision NEXCODER 2440 Light Board"
  54. select CPU_S3C2440
  55. help
  56. Say Y here if you are using the Nex Vision NEXCODER 2440 Light Board
  57. endmenu
  58. config CPU_S3C2410
  59. bool
  60. depends on ARCH_S3C2410
  61. help
  62. Support for S3C2410 and S3C2410A family from the S3C24XX line
  63. of Samsung Mobile CPUs.
  64. config CPU_S3C2440
  65. bool
  66. depends on ARCH_S3C2410
  67. help
  68. Support for S3C2440 Samsung Mobile CPU based systems.
  69. comment "S3C2410 Boot"
  70. config S3C2410_BOOT_WATCHDOG
  71. bool "S3C2410 Initialisation watchdog"
  72. depends on ARCH_S3C2410 && S3C2410_WATCHDOG
  73. help
  74. Say y to enable the watchdog during the kernel decompression
  75. stage. If the kernel fails to uncompress, then the watchdog
  76. will trigger a reset and the system should restart.
  77. Although this uses the same hardware unit as the kernel watchdog
  78. driver, it is not a replacement for it. If you use this option,
  79. you will have to use the watchdg driver to either stop the timeout
  80. or restart it. If you do not, then your kernel will reboot after
  81. startup.
  82. The driver uses a fixed timeout value, so the exact time till the
  83. system resets depends on the value of PCLK. The timeout on an
  84. 200MHz s3c2410 should be about 30 seconds.
  85. comment "S3C2410 Setup"
  86. config S3C2410_DMA
  87. bool "S3C2410 DMA support"
  88. depends on ARCH_S3C2410
  89. help
  90. S3C2410 DMA support. This is needed for drivers like sound which
  91. use the S3C2410's DMA system to move data to and from the
  92. peripheral blocks.
  93. config S3C2410_DMA_DEBUG
  94. bool "S3C2410 DMA support debug"
  95. depends on ARCH_S3C2410 && S3C2410_DMA
  96. help
  97. Enable debugging output for the DMA code. This option sends info
  98. to the kernel log, at priority KERN_DEBUG.
  99. Note, it is easy to create and fill the log buffer in a small
  100. amount of time, as well as using an significant percentage of
  101. the CPU time doing so.
  102. config S3C2410_PM_DEBUG
  103. bool "S3C2410 PM Suspend debug"
  104. depends on ARCH_S3C2410 && PM
  105. help
  106. Say Y here if you want verbose debugging from the PM Suspend and
  107. Resume code. See `Documentation/arm/Samsing-S3C24XX/Suspend.txt`
  108. for more information.
  109. config S3C2410_PM_CHECK
  110. bool "S3C2410 PM Suspend Memory CRC"
  111. depends on ARCH_S3C2410 && PM && CRC32
  112. help
  113. Enable the PM code's memory area checksum over sleep. This option
  114. will generate CRCs of all blocks of memory, and store them before
  115. going to sleep. The blocks are then checked on resume for any
  116. errors.
  117. config S3C2410_PM_CHECK_CHUNKSIZE
  118. int "S3C2410 PM Suspend CRC Chunksize (KiB)"
  119. depends on ARCH_S3C2410 && PM && S3C2410_PM_CHECK
  120. default 64
  121. help
  122. Set the chunksize in Kilobytes of the CRC for checking memory
  123. corruption over suspend and resume. A smaller value will mean that
  124. the CRC data block will take more memory, but wil identify any
  125. faults with better precision.
  126. config PM_SIMTEC
  127. bool
  128. depends on PM && (ARCH_BAST || MACH_VR1000)
  129. default y
  130. config S3C2410_LOWLEVEL_UART_PORT
  131. int "S3C2410 UART to use for low-level messages"
  132. default 0
  133. help
  134. Choice of which UART port to use for the low-level messages,
  135. such as the `Uncompressing...` at start time. The value of
  136. this configuration should be between zero and two. The port
  137. must have been initialised by the boot-loader before use.
  138. Note, this does not affect the port used by the debug messages,
  139. which is a separate configuration.
  140. endif