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 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 version 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
182 depends on CPU_S3C2412
184 Internal config node to apply S3C2412 power management
188 depends on ARCH_S3C2410
190 Support for the S3C2412 and S3C2413 SoCs from the S3C24XX line
194 depends on ARCH_S3C2410 && (CPU_S3C2440 || CPU_S3C2442)
196 Support for S3C2440 and S3C2442 Samsung Mobile CPU based systems.
200 depends on ARCH_S3C2410
205 Support for S3C2440 Samsung Mobile CPU based systems.
209 depends on ARCH_S3C2420
214 Support for S3C2442 Samsung Mobile CPU based systems.
216 comment "S3C2410 Boot"
218 config S3C2410_BOOT_WATCHDOG
219 bool "S3C2410 Initialisation watchdog"
220 depends on ARCH_S3C2410 && S3C2410_WATCHDOG
222 Say y to enable the watchdog during the kernel decompression
223 stage. If the kernel fails to uncompress, then the watchdog
224 will trigger a reset and the system should restart.
226 Although this uses the same hardware unit as the kernel watchdog
227 driver, it is not a replacement for it. If you use this option,
228 you will have to use the watchdg driver to either stop the timeout
229 or restart it. If you do not, then your kernel will reboot after
232 The driver uses a fixed timeout value, so the exact time till the
233 system resets depends on the value of PCLK. The timeout on an
234 200MHz s3c2410 should be about 30 seconds.
236 config S3C2410_BOOT_ERROR_RESET
237 bool "S3C2410 Reboot on decompression error"
238 depends on ARCH_S3C2410
240 Say y here to use the watchdog to reset the system if the
241 kernel decompressor detects an error during decompression.
244 comment "S3C2410 Setup"
247 bool "S3C2410 DMA support"
248 depends on ARCH_S3C2410
250 S3C2410 DMA support. This is needed for drivers like sound which
251 use the S3C2410's DMA system to move data to and from the
254 config S3C2410_DMA_DEBUG
255 bool "S3C2410 DMA support debug"
256 depends on ARCH_S3C2410 && S3C2410_DMA
258 Enable debugging output for the DMA code. This option sends info
259 to the kernel log, at priority KERN_DEBUG.
261 Note, it is easy to create and fill the log buffer in a small
262 amount of time, as well as using an significant percentage of
263 the CPU time doing so.
266 config S3C2410_PM_DEBUG
267 bool "S3C2410 PM Suspend debug"
268 depends on ARCH_S3C2410 && PM
270 Say Y here if you want verbose debugging from the PM Suspend and
271 Resume code. See <file:Documentation/arm/Samsung-S3C24XX/Suspend.txt>
272 for more information.
274 config S3C2410_PM_CHECK
275 bool "S3C2410 PM Suspend Memory CRC"
276 depends on ARCH_S3C2410 && PM && CRC32
278 Enable the PM code's memory area checksum over sleep. This option
279 will generate CRCs of all blocks of memory, and store them before
280 going to sleep. The blocks are then checked on resume for any
283 config S3C2410_PM_CHECK_CHUNKSIZE
284 int "S3C2410 PM Suspend CRC Chunksize (KiB)"
285 depends on ARCH_S3C2410 && PM && S3C2410_PM_CHECK
288 Set the chunksize in Kilobytes of the CRC for checking memory
289 corruption over suspend and resume. A smaller value will mean that
290 the CRC data block will take more memory, but wil identify any
291 faults with better precision.
295 depends on PM && (ARCH_BAST || MACH_VR1000 || MACH_AML_M5900)
298 config S3C2410_LOWLEVEL_UART_PORT
299 int "S3C2410 UART to use for low-level messages"
302 Choice of which UART port to use for the low-level messages,
303 such as the `Uncompressing...` at start time. The value of
304 this configuration should be between zero and two. The port
305 must have been initialised by the boot-loader before use.
307 Note, this does not affect the port used by the debug messages,
308 which is a separate configuration.