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)"
17 Say Y here if you are using the Simtec Electronics EB2410ITX
18 development board (also known as BAST)
20 Product page: <http://www.simtec.co.uk/products/EB2410ITX/>.
23 bool "BAST PC104 IRQ support"
27 Say Y here to enable the PC104 IRQ routing on the
28 Simtec BAST (EB2410ITX)
34 Say Y here if you are using the HP IPAQ H1940
36 <http://www.handhelds.org/projects/h1940.html>.
42 Say Y here if you are using the Acer N30
44 <http://zoo.weinigel.se/n30>.
47 bool "SMDK2410/A9M2410"
50 Say Y here if you are using the SMDK2410 or the derived module A9M2410
51 <http://www.fsforth.de>
57 Say Y here if you are using the SMDK2440.
63 Say Y here if you are using the Thorcom VR1000 board.
65 This linux port is currently being maintained by Simtec, on behalf
66 of Thorcom. Any queries, please contact Thorcom first.
72 Say Y here if you are using the HP iPAQ rx3715.
74 See <http://www.handhelds.org/projects/rx3715.html> for more
75 information on this project
78 bool "NexVision OTOM Board"
81 Say Y here if you are using the Nex Vision OTOM board
83 config MACH_NEXCODER_2440
84 bool "NexVision NEXCODER 2440 Light Board"
87 Say Y here if you are using the Nex Vision NEXCODER 2440 Light Board
93 depends on ARCH_S3C2410
95 Support for S3C2410 and S3C2410A family from the S3C24XX line
96 of Samsung Mobile CPUs.
100 depends on ARCH_S3C2410
102 Support for S3C2440 Samsung Mobile CPU based systems.
104 comment "S3C2410 Boot"
106 config S3C2410_BOOT_WATCHDOG
107 bool "S3C2410 Initialisation watchdog"
108 depends on ARCH_S3C2410 && S3C2410_WATCHDOG
110 Say y to enable the watchdog during the kernel decompression
111 stage. If the kernel fails to uncompress, then the watchdog
112 will trigger a reset and the system should restart.
114 Although this uses the same hardware unit as the kernel watchdog
115 driver, it is not a replacement for it. If you use this option,
116 you will have to use the watchdg driver to either stop the timeout
117 or restart it. If you do not, then your kernel will reboot after
120 The driver uses a fixed timeout value, so the exact time till the
121 system resets depends on the value of PCLK. The timeout on an
122 200MHz s3c2410 should be about 30 seconds.
124 comment "S3C2410 Setup"
127 bool "S3C2410 DMA support"
128 depends on ARCH_S3C2410
130 S3C2410 DMA support. This is needed for drivers like sound which
131 use the S3C2410's DMA system to move data to and from the
134 config S3C2410_DMA_DEBUG
135 bool "S3C2410 DMA support debug"
136 depends on ARCH_S3C2410 && S3C2410_DMA
138 Enable debugging output for the DMA code. This option sends info
139 to the kernel log, at priority KERN_DEBUG.
141 Note, it is easy to create and fill the log buffer in a small
142 amount of time, as well as using an significant percentage of
143 the CPU time doing so.
146 config S3C2410_PM_DEBUG
147 bool "S3C2410 PM Suspend debug"
148 depends on ARCH_S3C2410 && PM
150 Say Y here if you want verbose debugging from the PM Suspend and
151 Resume code. See `Documentation/arm/Samsing-S3C24XX/Suspend.txt`
152 for more information.
154 config S3C2410_PM_CHECK
155 bool "S3C2410 PM Suspend Memory CRC"
156 depends on ARCH_S3C2410 && PM && CRC32
158 Enable the PM code's memory area checksum over sleep. This option
159 will generate CRCs of all blocks of memory, and store them before
160 going to sleep. The blocks are then checked on resume for any
163 config S3C2410_PM_CHECK_CHUNKSIZE
164 int "S3C2410 PM Suspend CRC Chunksize (KiB)"
165 depends on ARCH_S3C2410 && PM && S3C2410_PM_CHECK
168 Set the chunksize in Kilobytes of the CRC for checking memory
169 corruption over suspend and resume. A smaller value will mean that
170 the CRC data block will take more memory, but wil identify any
171 faults with better precision.
175 depends on PM && (ARCH_BAST || MACH_VR1000)
178 config S3C2410_LOWLEVEL_UART_PORT
179 int "S3C2410 UART to use for low-level messages"
182 Choice of which UART port to use for the low-level messages,
183 such as the `Uncompressing...` at start time. The value of
184 this configuration should be between zero and two. The port
185 must have been initialised by the boot-loader before use.
187 Note, this does not affect the port used by the debug messages,
188 which is a separate configuration.