Kconfig 5.1 KB

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