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 here 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 Internal node for H1940 and related PM
55 Say Y here if you are using the HP IPAQ H1940
57 <http://www.handhelds.org/projects/h1940.html>.
63 Say Y here if you are using the Acer N30
65 <http://zoo.weinigel.se/n30>.
70 Common machine code for SMDK2410 and SMDK2440
73 bool "SMDK2410/A9M2410"
77 Say Y here if you are using the SMDK2410 or the derived module A9M2410
78 <http://www.fsforth.de>
85 Say Y here if you are using the SMDK2440.
87 config SMDK2440_CPU2440
88 bool "SMDK2440 with S3C2440 CPU module"
89 depends on ARCH_S3C2440
90 default y if ARCH_S3C2440
93 config SMDK2440_CPU2442
94 bool "SMDM2440 with S3C2442 CPU module"
95 depends on ARCH_S3C2440
101 Internal node for S3C2413 version of SMDK2413, so that
102 machine_is_s3c2413() will work when MACH_SMDK2413 is
111 Say Y here if you are using an SMDK2413
114 bool "Thorcom VR1000"
117 Say Y here if you are using the Thorcom VR1000 board.
119 This linux port is currently being maintained by Simtec, on behalf
120 of Thorcom. Any queries, please contact Thorcom first.
123 bool "HP iPAQ rx3715"
127 Say Y here if you are using the HP iPAQ rx3715.
129 See <http://www.handhelds.org/projects/rx3715.html> for more
130 information on this project
133 bool "NexVision OTOM Board"
136 Say Y here if you are using the Nex Vision OTOM board
138 config MACH_NEXCODER_2440
139 bool "NexVision NEXCODER 2440 Light Board"
142 Say Y here if you are using the Nex Vision NEXCODER 2440 Light Board
148 Say Y here if you are using an VSTMS board
155 Clock code for the S3C2410, and similar processors
161 Power Management code common to S3C2410 and better
163 config CPU_S3C2410_DMA
165 depends on S3C2410_DMA && (CPU_S3C2410 || CPU_S3C2442)
166 default y if CPU_S3C2410 || CPU_S3C2442
168 DMA device selection for S3C2410 and compatible CPUs
172 depends on ARCH_S3C2410
176 Support for S3C2410 and S3C2410A family from the S3C24XX line
177 of Samsung Mobile CPUs.
179 # internal node to signify if we are only dealing with an S3C2412
181 config CPU_S3C2412_ONLY
183 depends on ARCH_S3C2410 && !CPU_S3C2400 && !CPU_S3C2410 && \
184 !CPU_S3C2440 && !CPU_S3C2442 && CPU_S3C2412
185 default y if CPU_S3C2412
190 depends on CPU_S3C2412
192 Internal config node to apply S3C2412 power management
196 depends on ARCH_S3C2410
198 Support for the S3C2412 and S3C2413 SoCs from the S3C24XX line
202 depends on ARCH_S3C2410 && (CPU_S3C2440 || CPU_S3C2442)
204 Support for S3C2440 and S3C2442 Samsung Mobile CPU based systems.
208 depends on ARCH_S3C2410
213 Support for S3C2440 Samsung Mobile CPU based systems.
217 depends on ARCH_S3C2420
222 Support for S3C2442 Samsung Mobile CPU based systems.
224 comment "S3C2410 Boot"
226 config S3C2410_BOOT_WATCHDOG
227 bool "S3C2410 Initialisation watchdog"
228 depends on ARCH_S3C2410 && S3C2410_WATCHDOG
230 Say y to enable the watchdog during the kernel decompression
231 stage. If the kernel fails to uncompress, then the watchdog
232 will trigger a reset and the system should restart.
234 Although this uses the same hardware unit as the kernel watchdog
235 driver, it is not a replacement for it. If you use this option,
236 you will have to use the watchdg driver to either stop the timeout
237 or restart it. If you do not, then your kernel will reboot after
240 The driver uses a fixed timeout value, so the exact time till the
241 system resets depends on the value of PCLK. The timeout on an
242 200MHz s3c2410 should be about 30 seconds.
244 config S3C2410_BOOT_ERROR_RESET
245 bool "S3C2410 Reboot on decompression error"
246 depends on ARCH_S3C2410
248 Say y here to use the watchdog to reset the system if the
249 kernel decompressor detects an error during decompression.
252 comment "S3C2410 Setup"
255 bool "S3C2410 DMA support"
256 depends on ARCH_S3C2410
258 S3C2410 DMA support. This is needed for drivers like sound which
259 use the S3C2410's DMA system to move data to and from the
262 config S3C2410_DMA_DEBUG
263 bool "S3C2410 DMA support debug"
264 depends on ARCH_S3C2410 && S3C2410_DMA
266 Enable debugging output for the DMA code. This option sends info
267 to the kernel log, at priority KERN_DEBUG.
269 Note, it is easy to create and fill the log buffer in a small
270 amount of time, as well as using an significant percentage of
271 the CPU time doing so.
274 config S3C2410_PM_DEBUG
275 bool "S3C2410 PM Suspend debug"
276 depends on ARCH_S3C2410 && PM
278 Say Y here if you want verbose debugging from the PM Suspend and
279 Resume code. See <file:Documentation/arm/Samsung-S3C24XX/Suspend.txt>
280 for more information.
282 config S3C2410_PM_CHECK
283 bool "S3C2410 PM Suspend Memory CRC"
284 depends on ARCH_S3C2410 && PM && CRC32
286 Enable the PM code's memory area checksum over sleep. This option
287 will generate CRCs of all blocks of memory, and store them before
288 going to sleep. The blocks are then checked on resume for any
291 config S3C2410_PM_CHECK_CHUNKSIZE
292 int "S3C2410 PM Suspend CRC Chunksize (KiB)"
293 depends on ARCH_S3C2410 && PM && S3C2410_PM_CHECK
296 Set the chunksize in Kilobytes of the CRC for checking memory
297 corruption over suspend and resume. A smaller value will mean that
298 the CRC data block will take more memory, but wil identify any
299 faults with better precision.
303 depends on PM && (ARCH_BAST || MACH_VR1000 || MACH_AML_M5900)
306 config S3C2410_LOWLEVEL_UART_PORT
307 int "S3C2410 UART to use for low-level messages"
310 Choice of which UART port to use for the low-level messages,
311 such as the `Uncompressing...` at start time. The value of
312 this configuration should be between zero and two. The port
313 must have been initialised by the boot-loader before use.
315 Note, this does not affect the port used by the debug messages,
316 which is a separate configuration.