3 menu "S3C24XX Implementations"
6 bool "Simtec Electronics ANUBIS"
9 Say Y gere if you are using the Simtec Electronics ANUBIS
13 bool "Simtec Electronics BAST (EB2410ITX)"
16 Say Y here if you are using the Simtec Electronics EB2410ITX
17 development board (also known as BAST)
19 Product page: <http://www.simtec.co.uk/products/EB2410ITX/>.
22 bool "BAST PC104 IRQ support"
26 Say Y here to enable the PC104 IRQ routing on the
27 Simtec BAST (EB2410ITX)
33 Say Y here if you are using the HP IPAQ H1940
35 <http://www.handhelds.org/projects/h1940.html>.
41 Say Y here if you are using the Acer N30
43 <http://zoo.weinigel.se/n30>.
46 bool "SMDK2410/A9M2410"
49 Say Y here if you are using the SMDK2410 or the derived module A9M2410
50 <http://www.fsforth.de>
56 Say Y here if you are using the SMDK2440.
62 Say Y here if you are using the Thorcom VR1000 board.
64 This linux port is currently being maintained by Simtec, on behalf
65 of Thorcom. Any queries, please contact Thorcom first.
71 Say Y here if you are using the HP iPAQ rx3715.
73 See <http://www.handhelds.org/projects/rx3715.html> for more
74 information on this project
77 bool "NexVision OTOM Board"
80 Say Y here if you are using the Nex Vision OTOM board
82 config MACH_NEXCODER_2440
83 bool "NexVision NEXCODER 2440 Light Board"
86 Say Y here if you are using the Nex Vision NEXCODER 2440 Light Board
92 depends on ARCH_S3C2410
94 Support for S3C2410 and S3C2410A family from the S3C24XX line
95 of Samsung Mobile CPUs.
99 depends on ARCH_S3C2410
101 Support for S3C2440 Samsung Mobile CPU based systems.
103 comment "S3C2410 Boot"
105 config S3C2410_BOOT_WATCHDOG
106 bool "S3C2410 Initialisation watchdog"
107 depends on ARCH_S3C2410 && S3C2410_WATCHDOG
109 Say y to enable the watchdog during the kernel decompression
110 stage. If the kernel fails to uncompress, then the watchdog
111 will trigger a reset and the system should restart.
113 Although this uses the same hardware unit as the kernel watchdog
114 driver, it is not a replacement for it. If you use this option,
115 you will have to use the watchdg driver to either stop the timeout
116 or restart it. If you do not, then your kernel will reboot after
119 The driver uses a fixed timeout value, so the exact time till the
120 system resets depends on the value of PCLK. The timeout on an
121 200MHz s3c2410 should be about 30 seconds.
123 comment "S3C2410 Setup"
126 bool "S3C2410 DMA support"
127 depends on ARCH_S3C2410
129 S3C2410 DMA support. This is needed for drivers like sound which
130 use the S3C2410's DMA system to move data to and from the
133 config S3C2410_DMA_DEBUG
134 bool "S3C2410 DMA support debug"
135 depends on ARCH_S3C2410 && S3C2410_DMA
137 Enable debugging output for the DMA code. This option sends info
138 to the kernel log, at priority KERN_DEBUG.
140 Note, it is easy to create and fill the log buffer in a small
141 amount of time, as well as using an significant percentage of
142 the CPU time doing so.
145 config S3C2410_PM_DEBUG
146 bool "S3C2410 PM Suspend debug"
147 depends on ARCH_S3C2410 && PM
149 Say Y here if you want verbose debugging from the PM Suspend and
150 Resume code. See `Documentation/arm/Samsing-S3C24XX/Suspend.txt`
151 for more information.
153 config S3C2410_PM_CHECK
154 bool "S3C2410 PM Suspend Memory CRC"
155 depends on ARCH_S3C2410 && PM && CRC32
157 Enable the PM code's memory area checksum over sleep. This option
158 will generate CRCs of all blocks of memory, and store them before
159 going to sleep. The blocks are then checked on resume for any
162 config S3C2410_PM_CHECK_CHUNKSIZE
163 int "S3C2410 PM Suspend CRC Chunksize (KiB)"
164 depends on ARCH_S3C2410 && PM && S3C2410_PM_CHECK
167 Set the chunksize in Kilobytes of the CRC for checking memory
168 corruption over suspend and resume. A smaller value will mean that
169 the CRC data block will take more memory, but wil identify any
170 faults with better precision.
174 depends on PM && (ARCH_BAST || MACH_VR1000)
177 config S3C2410_LOWLEVEL_UART_PORT
178 int "S3C2410 UART to use for low-level messages"
181 Choice of which UART port to use for the low-level messages,
182 such as the `Uncompressing...` at start time. The value of
183 this configuration should be between zero and two. The port
184 must have been initialised by the boot-loader before use.
186 Note, this does not affect the port used by the debug messages,
187 which is a separate configuration.