3 menu "S3C24XX Implementations"
6 bool "AML M5900 Series"
9 Say Y here if you are using the American Microsystems M5900 Series
10 <http://www.amltd.com>
13 bool "Simtec Electronics ANUBIS"
16 Say Y gere if you are using the Simtec Electronics ANUBIS
20 bool "Simtec IM2440D20 (OSIRIS) module"
23 Say Y here if you are using the Simtec IM2440D20 module, also
27 bool "Simtec Electronics BAST (EB2410ITX)"
31 Say Y here if you are using the Simtec Electronics EB2410ITX
32 development board (also known as BAST)
34 Product page: <http://www.simtec.co.uk/products/EB2410ITX/>.
37 bool "BAST PC104 IRQ support"
41 Say Y here to enable the PC104 IRQ routing on the
42 Simtec BAST (EB2410ITX)
48 Say Y here if you are using the HP IPAQ H1940
50 <http://www.handhelds.org/projects/h1940.html>.
56 Say Y here if you are using the Acer N30
58 <http://zoo.weinigel.se/n30>.
63 Common machine code for SMDK2410 and SMDK2440
66 bool "SMDK2410/A9M2410"
70 Say Y here if you are using the SMDK2410 or the derived module A9M2410
71 <http://www.fsforth.de>
78 Say Y here if you are using the SMDK2440.
80 config SMDK2440_CPU2440
81 bool "SMDK2440 with S3C2440 CPU module"
82 depends on ARCH_S3C2440
83 default y if ARCH_S3C2440
86 config SMDK2440_CPU2442
87 bool "SMDM2440 with S3C2442 CPU module"
88 depends on ARCH_S3C2440
94 Internal node for S3C2413 verison of SMDK2413, so that
95 machine_is_s3c2413() will work when MACH_SMDK2413 is
104 Say Y here if you are using an SMDK2413
107 bool "Thorcom VR1000"
110 Say Y here if you are using the Thorcom VR1000 board.
112 This linux port is currently being maintained by Simtec, on behalf
113 of Thorcom. Any queries, please contact Thorcom first.
116 bool "HP iPAQ rx3715"
119 Say Y here if you are using the HP iPAQ rx3715.
121 See <http://www.handhelds.org/projects/rx3715.html> for more
122 information on this project
125 bool "NexVision OTOM Board"
128 Say Y here if you are using the Nex Vision OTOM board
130 config MACH_NEXCODER_2440
131 bool "NexVision NEXCODER 2440 Light Board"
134 Say Y here if you are using the Nex Vision NEXCODER 2440 Light Board
140 Say Y here if you are using an VSTMS board
147 Clock code for the S3C2410, and similar processors
153 Power Management code common to S3C2410 and better
155 config CPU_S3C2410_DMA
157 depends on S3C2410_DMA && (CPU_S3C2410 || CPU_S3C2442)
158 default y if CPU_S3C2410 || CPU_S3C2442
160 DMA device selection for S3C2410 and compatible CPUs
164 depends on ARCH_S3C2410
168 Support for S3C2410 and S3C2410A family from the S3C24XX line
169 of Samsung Mobile CPUs.
171 # internal node to signify if we are only dealing with an S3C2412
173 config CPU_S3C2412_ONLY
175 depends on ARCH_S3C2410 && !CPU_S3C2400 && !CPU_S3C2410 && \
176 !CPU_S3C2440 && !CPU_S3C2442 && CPU_S3C2412
177 default y if CPU_S3C2412
181 depends on ARCH_S3C2410
183 Support for the S3C2412 and S3C2413 SoCs from the S3C24XX line
187 depends on ARCH_S3C2410 && (CPU_S3C2440 || CPU_S3C2442)
189 Support for S3C2440 and S3C2442 Samsung Mobile CPU based systems.
193 depends on ARCH_S3C2410
198 Support for S3C2440 Samsung Mobile CPU based systems.
202 depends on ARCH_S3C2420
207 Support for S3C2442 Samsung Mobile CPU based systems.
209 comment "S3C2410 Boot"
211 config S3C2410_BOOT_WATCHDOG
212 bool "S3C2410 Initialisation watchdog"
213 depends on ARCH_S3C2410 && S3C2410_WATCHDOG
215 Say y to enable the watchdog during the kernel decompression
216 stage. If the kernel fails to uncompress, then the watchdog
217 will trigger a reset and the system should restart.
219 Although this uses the same hardware unit as the kernel watchdog
220 driver, it is not a replacement for it. If you use this option,
221 you will have to use the watchdg driver to either stop the timeout
222 or restart it. If you do not, then your kernel will reboot after
225 The driver uses a fixed timeout value, so the exact time till the
226 system resets depends on the value of PCLK. The timeout on an
227 200MHz s3c2410 should be about 30 seconds.
229 config S3C2410_BOOT_ERROR_RESET
230 bool "S3C2410 Reboot on decompression error"
231 depends on ARCH_S3C2410
233 Say y here to use the watchdog to reset the system if the
234 kernel decompressor detects an error during decompression.
237 comment "S3C2410 Setup"
240 bool "S3C2410 DMA support"
241 depends on ARCH_S3C2410
243 S3C2410 DMA support. This is needed for drivers like sound which
244 use the S3C2410's DMA system to move data to and from the
247 config S3C2410_DMA_DEBUG
248 bool "S3C2410 DMA support debug"
249 depends on ARCH_S3C2410 && S3C2410_DMA
251 Enable debugging output for the DMA code. This option sends info
252 to the kernel log, at priority KERN_DEBUG.
254 Note, it is easy to create and fill the log buffer in a small
255 amount of time, as well as using an significant percentage of
256 the CPU time doing so.
259 config S3C2410_PM_DEBUG
260 bool "S3C2410 PM Suspend debug"
261 depends on ARCH_S3C2410 && PM
263 Say Y here if you want verbose debugging from the PM Suspend and
264 Resume code. See <file:Documentation/arm/Samsung-S3C24XX/Suspend.txt>
265 for more information.
267 config S3C2410_PM_CHECK
268 bool "S3C2410 PM Suspend Memory CRC"
269 depends on ARCH_S3C2410 && PM && CRC32
271 Enable the PM code's memory area checksum over sleep. This option
272 will generate CRCs of all blocks of memory, and store them before
273 going to sleep. The blocks are then checked on resume for any
276 config S3C2410_PM_CHECK_CHUNKSIZE
277 int "S3C2410 PM Suspend CRC Chunksize (KiB)"
278 depends on ARCH_S3C2410 && PM && S3C2410_PM_CHECK
281 Set the chunksize in Kilobytes of the CRC for checking memory
282 corruption over suspend and resume. A smaller value will mean that
283 the CRC data block will take more memory, but wil identify any
284 faults with better precision.
288 depends on PM && (ARCH_BAST || MACH_VR1000)
291 config S3C2410_LOWLEVEL_UART_PORT
292 int "S3C2410 UART to use for low-level messages"
295 Choice of which UART port to use for the low-level messages,
296 such as the `Uncompressing...` at start time. The value of
297 this configuration should be between zero and two. The port
298 must have been initialised by the boot-loader before use.
300 Note, this does not affect the port used by the debug messages,
301 which is a separate configuration.