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/>.
25 Say Y here if you are using the HP IPAQ H1940
27 <http://www.handhelds.org/projects/h1940.html>.
33 Say Y here if you are using the Acer N30
35 <http://zoo.weinigel.se/n30>.
38 bool "SMDK2410/A9M2410"
41 Say Y here if you are using the SMDK2410 or the derived module A9M2410
42 <http://www.fsforth.de>
48 Say Y here if you are using the SMDK2440.
54 Say Y here if you are using the Thorcom VR1000 board.
56 This linux port is currently being maintained by Simtec, on behalf
57 of Thorcom. Any queries, please contact Thorcom first.
63 Say Y here if you are using the HP iPAQ rx3715.
65 See <http://www.handhelds.org/projects/rx3715.html> for more
66 information on this project
69 bool "NexVision OTOM Board"
72 Say Y here if you are using the Nex Vision OTOM board
74 config MACH_NEXCODER_2440
75 bool "NexVision NEXCODER 2440 Light Board"
78 Say Y here if you are using the Nex Vision NEXCODER 2440 Light Board
84 depends on ARCH_S3C2410
86 Support for S3C2410 and S3C2410A family from the S3C24XX line
87 of Samsung Mobile CPUs.
91 depends on ARCH_S3C2410
93 Support for S3C2440 Samsung Mobile CPU based systems.
95 comment "S3C2410 Boot"
97 config S3C2410_BOOT_WATCHDOG
98 bool "S3C2410 Initialisation watchdog"
99 depends on ARCH_S3C2410 && S3C2410_WATCHDOG
101 Say y to enable the watchdog during the kernel decompression
102 stage. If the kernel fails to uncompress, then the watchdog
103 will trigger a reset and the system should restart.
105 Although this uses the same hardware unit as the kernel watchdog
106 driver, it is not a replacement for it. If you use this option,
107 you will have to use the watchdg driver to either stop the timeout
108 or restart it. If you do not, then your kernel will reboot after
111 The driver uses a fixed timeout value, so the exact time till the
112 system resets depends on the value of PCLK. The timeout on an
113 200MHz s3c2410 should be about 30 seconds.
115 comment "S3C2410 Setup"
118 bool "S3C2410 DMA support"
119 depends on ARCH_S3C2410
121 S3C2410 DMA support. This is needed for drivers like sound which
122 use the S3C2410's DMA system to move data to and from the
125 config S3C2410_DMA_DEBUG
126 bool "S3C2410 DMA support debug"
127 depends on ARCH_S3C2410 && S3C2410_DMA
129 Enable debugging output for the DMA code. This option sends info
130 to the kernel log, at priority KERN_DEBUG.
132 Note, it is easy to create and fill the log buffer in a small
133 amount of time, as well as using an significant percentage of
134 the CPU time doing so.
137 config S3C2410_PM_DEBUG
138 bool "S3C2410 PM Suspend debug"
139 depends on ARCH_S3C2410 && PM
141 Say Y here if you want verbose debugging from the PM Suspend and
142 Resume code. See `Documentation/arm/Samsing-S3C24XX/Suspend.txt`
143 for more information.
145 config S3C2410_PM_CHECK
146 bool "S3C2410 PM Suspend Memory CRC"
147 depends on ARCH_S3C2410 && PM && CRC32
149 Enable the PM code's memory area checksum over sleep. This option
150 will generate CRCs of all blocks of memory, and store them before
151 going to sleep. The blocks are then checked on resume for any
154 config S3C2410_PM_CHECK_CHUNKSIZE
155 int "S3C2410 PM Suspend CRC Chunksize (KiB)"
156 depends on ARCH_S3C2410 && PM && S3C2410_PM_CHECK
159 Set the chunksize in Kilobytes of the CRC for checking memory
160 corruption over suspend and resume. A smaller value will mean that
161 the CRC data block will take more memory, but wil identify any
162 faults with better precision.
166 depends on PM && (ARCH_BAST || MACH_VR1000)
169 config S3C2410_LOWLEVEL_UART_PORT
170 int "S3C2410 UART to use for low-level messages"
173 Choice of which UART port to use for the low-level messages,
174 such as the `Uncompressing...` at start time. The value of
175 this configuration should be between zero and two. The port
176 must have been initialised by the boot-loader before use.
178 Note, this does not affect the port used by the debug messages,
179 which is a separate configuration.