blob: 0b9d7ca49ec1ff9f9520cc02c845c0c8990c30b1 [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001if ARCH_S3C2410
2
3menu "S3C24XX Implementations"
4
Ben Dooks7efb8332005-09-07 11:49:23 +01005config MACH_ANUBIS
6 bool "Simtec Electronics ANUBIS"
7 select CPU_S3C2440
8 help
9 Say Y gere if you are using the Simtec Electronics ANUBIS
10 development system
11
Linus Torvalds1da177e2005-04-16 15:20:36 -070012config ARCH_BAST
13 bool "Simtec Electronics BAST (EB2410ITX)"
14 select CPU_S3C2410
Ben Dooks50688ea2005-10-13 22:04:36 +010015 select ISA
Linus Torvalds1da177e2005-04-16 15:20:36 -070016 help
17 Say Y here if you are using the Simtec Electronics EB2410ITX
18 development board (also known as BAST)
19
20 Product page: <http://www.simtec.co.uk/products/EB2410ITX/>.
21
Ben Dooksbafa49c2005-09-07 17:24:48 +010022config BAST_PC104_IRQ
23 bool "BAST PC104 IRQ support"
24 depends on ARCH_BAST
25 default y
26 help
27 Say Y here to enable the PC104 IRQ routing on the
28 Simtec BAST (EB2410ITX)
29
Linus Torvalds1da177e2005-04-16 15:20:36 -070030config ARCH_H1940
31 bool "IPAQ H1940"
32 select CPU_S3C2410
33 help
34 Say Y here if you are using the HP IPAQ H1940
35
36 <http://www.handhelds.org/projects/h1940.html>.
37
38config MACH_N30
39 bool "Acer N30"
40 select CPU_S3C2410
41 help
42 Say Y here if you are using the Acer N30
43
44 <http://zoo.weinigel.se/n30>.
45
46config ARCH_SMDK2410
47 bool "SMDK2410/A9M2410"
48 select CPU_S3C2410
49 help
50 Say Y here if you are using the SMDK2410 or the derived module A9M2410
51 <http://www.fsforth.de>
52
53config ARCH_S3C2440
54 bool "SMDK2440"
55 select CPU_S3C2440
56 help
57 Say Y here if you are using the SMDK2440.
58
59config MACH_VR1000
60 bool "Thorcom VR1000"
61 select CPU_S3C2410
62 help
63 Say Y here if you are using the Thorcom VR1000 board.
64
65 This linux port is currently being maintained by Simtec, on behalf
66 of Thorcom. Any queries, please contact Thorcom first.
67
68config MACH_RX3715
69 bool "HP iPAQ rx3715"
70 select CPU_S3C2440
71 help
72 Say Y here if you are using the HP iPAQ rx3715.
73
74 See <http://www.handhelds.org/projects/rx3715.html> for more
75 information on this project
76
77config MACH_OTOM
78 bool "NexVision OTOM Board"
79 select CPU_S3C2410
80 help
81 Say Y here if you are using the Nex Vision OTOM board
82
83config MACH_NEXCODER_2440
84 bool "NexVision NEXCODER 2440 Light Board"
85 select CPU_S3C2440
86 help
87 Say Y here if you are using the Nex Vision NEXCODER 2440 Light Board
88
89endmenu
90
91config CPU_S3C2410
92 bool
93 depends on ARCH_S3C2410
94 help
95 Support for S3C2410 and S3C2410A family from the S3C24XX line
96 of Samsung Mobile CPUs.
97
98config CPU_S3C2440
99 bool
100 depends on ARCH_S3C2410
101 help
102 Support for S3C2440 Samsung Mobile CPU based systems.
103
104comment "S3C2410 Boot"
105
106config S3C2410_BOOT_WATCHDOG
107 bool "S3C2410 Initialisation watchdog"
108 depends on ARCH_S3C2410 && S3C2410_WATCHDOG
109 help
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.
113
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
118 startup.
119
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.
123
Ben Dooksf8c905d2005-11-08 22:43:05 +0000124config S3C2410_BOOT_ERROR_RESET
125 bool "S3C2410 Reboot on decompression error"
126 depends on ARCH_S3C2410
127 help
128 Say y here to use the watchdog to reset the system if the
129 kernel decompressor detects an error during decompression.
130
131
Linus Torvalds1da177e2005-04-16 15:20:36 -0700132comment "S3C2410 Setup"
133
134config S3C2410_DMA
135 bool "S3C2410 DMA support"
136 depends on ARCH_S3C2410
137 help
138 S3C2410 DMA support. This is needed for drivers like sound which
139 use the S3C2410's DMA system to move data to and from the
140 peripheral blocks.
141
142config S3C2410_DMA_DEBUG
143 bool "S3C2410 DMA support debug"
144 depends on ARCH_S3C2410 && S3C2410_DMA
145 help
146 Enable debugging output for the DMA code. This option sends info
147 to the kernel log, at priority KERN_DEBUG.
148
149 Note, it is easy to create and fill the log buffer in a small
150 amount of time, as well as using an significant percentage of
151 the CPU time doing so.
152
153
154config S3C2410_PM_DEBUG
155 bool "S3C2410 PM Suspend debug"
156 depends on ARCH_S3C2410 && PM
157 help
158 Say Y here if you want verbose debugging from the PM Suspend and
159 Resume code. See `Documentation/arm/Samsing-S3C24XX/Suspend.txt`
160 for more information.
161
162config S3C2410_PM_CHECK
163 bool "S3C2410 PM Suspend Memory CRC"
164 depends on ARCH_S3C2410 && PM && CRC32
165 help
166 Enable the PM code's memory area checksum over sleep. This option
167 will generate CRCs of all blocks of memory, and store them before
168 going to sleep. The blocks are then checked on resume for any
169 errors.
170
171config S3C2410_PM_CHECK_CHUNKSIZE
172 int "S3C2410 PM Suspend CRC Chunksize (KiB)"
173 depends on ARCH_S3C2410 && PM && S3C2410_PM_CHECK
174 default 64
175 help
176 Set the chunksize in Kilobytes of the CRC for checking memory
177 corruption over suspend and resume. A smaller value will mean that
178 the CRC data block will take more memory, but wil identify any
179 faults with better precision.
180
Ben Dooksf705b1a2005-06-29 11:09:15 +0100181config PM_SIMTEC
182 bool
183 depends on PM && (ARCH_BAST || MACH_VR1000)
184 default y
185
Linus Torvalds1da177e2005-04-16 15:20:36 -0700186config S3C2410_LOWLEVEL_UART_PORT
187 int "S3C2410 UART to use for low-level messages"
188 default 0
189 help
190 Choice of which UART port to use for the low-level messages,
191 such as the `Uncompressing...` at start time. The value of
192 this configuration should be between zero and two. The port
193 must have been initialised by the boot-loader before use.
194
195 Note, this does not affect the port used by the debug messages,
196 which is a separate configuration.
197
198endif