ARM: kirkwood: fix LEDs names for lsxl boards
[deliverable/linux.git] / arch / frv / Kconfig
1 config FRV
2 bool
3 default y
4 select HAVE_IDE
5 select HAVE_ARCH_TRACEHOOK
6 select HAVE_IRQ_WORK
7 select HAVE_PERF_EVENTS
8 select HAVE_UID16
9 select HAVE_GENERIC_HARDIRQS
10 select GENERIC_IRQ_SHOW
11 select HAVE_DEBUG_BUGVERBOSE
12 select ARCH_HAVE_NMI_SAFE_CMPXCHG
13 select GENERIC_CPU_DEVICES
14 select ARCH_WANT_IPC_PARSE_VERSION
15 select GENERIC_KERNEL_THREAD
16
17 config ZONE_DMA
18 bool
19 default y
20
21 config RWSEM_GENERIC_SPINLOCK
22 bool
23 default y
24
25 config RWSEM_XCHGADD_ALGORITHM
26 bool
27
28 config GENERIC_HWEIGHT
29 bool
30 default y
31
32 config GENERIC_CALIBRATE_DELAY
33 bool
34 default n
35
36 config TIME_LOW_RES
37 bool
38 default y
39
40 config QUICKLIST
41 bool
42 default y
43
44 config ARCH_HAS_ILOG2_U32
45 bool
46 default y
47
48 config ARCH_HAS_ILOG2_U64
49 bool
50 default y
51
52 config HZ
53 int
54 default 1000
55
56 source "init/Kconfig"
57
58 source "kernel/Kconfig.freezer"
59
60
61 menu "Fujitsu FR-V system setup"
62
63 config MMU
64 bool "MMU support"
65 help
66 This options switches on and off support for the FR-V MMU
67 (effectively switching between vmlinux and uClinux). Not all FR-V
68 CPUs support this. Currently only the FR451 has a sufficiently
69 featured MMU.
70
71 config FRV_OUTOFLINE_ATOMIC_OPS
72 bool "Out-of-line the FRV atomic operations"
73 default n
74 help
75 Setting this option causes the FR-V atomic operations to be mostly
76 implemented out-of-line.
77
78 See Documentation/frv/atomic-ops.txt for more information.
79
80 config HIGHMEM
81 bool "High memory support"
82 depends on MMU
83 default y
84 help
85 If you wish to use more than 256MB of memory with your MMU based
86 system, you will need to select this option. The kernel can only see
87 the memory between 0xC0000000 and 0xD0000000 directly... everything
88 else must be kmapped.
89
90 The arch is, however, capable of supporting up to 3GB of SDRAM.
91
92 config HIGHPTE
93 bool "Allocate page tables in highmem"
94 depends on HIGHMEM
95 default y
96 help
97 The VM uses one page of memory for each page table. For systems
98 with a lot of RAM, this can be wasteful of precious low memory.
99 Setting this option will put user-space page tables in high memory.
100
101 source "mm/Kconfig"
102
103 choice
104 prompt "uClinux kernel load address"
105 depends on !MMU
106 default UCPAGE_OFFSET_C0000000
107 help
108 This option sets the base address for the uClinux kernel. The kernel
109 will rearrange the SDRAM layout to start at this address, and move
110 itself to start there. It must be greater than 0, and it must be
111 sufficiently less than 0xE0000000 that the SDRAM does not intersect
112 the I/O region.
113
114 The base address must also be aligned such that the SDRAM controller
115 can decode it. For instance, a 512MB SDRAM bank must be 512MB aligned.
116
117 config UCPAGE_OFFSET_20000000
118 bool "0x20000000"
119
120 config UCPAGE_OFFSET_40000000
121 bool "0x40000000"
122
123 config UCPAGE_OFFSET_60000000
124 bool "0x60000000"
125
126 config UCPAGE_OFFSET_80000000
127 bool "0x80000000"
128
129 config UCPAGE_OFFSET_A0000000
130 bool "0xA0000000"
131
132 config UCPAGE_OFFSET_C0000000
133 bool "0xC0000000 (Recommended)"
134
135 endchoice
136
137 config PAGE_OFFSET
138 hex
139 default 0x20000000 if UCPAGE_OFFSET_20000000
140 default 0x40000000 if UCPAGE_OFFSET_40000000
141 default 0x60000000 if UCPAGE_OFFSET_60000000
142 default 0x80000000 if UCPAGE_OFFSET_80000000
143 default 0xA0000000 if UCPAGE_OFFSET_A0000000
144 default 0xC0000000
145
146 config PROTECT_KERNEL
147 bool "Protect core kernel against userspace"
148 depends on !MMU
149 default y
150 help
151 Selecting this option causes the uClinux kernel to change the
152 permittivity of DAMPR register covering the core kernel image to
153 prevent userspace accessing the underlying memory directly.
154
155 choice
156 prompt "CPU Caching mode"
157 default FRV_DEFL_CACHE_WBACK
158 help
159 This option determines the default caching mode for the kernel.
160
161 Write-Back caching mode involves the all reads and writes causing
162 the affected cacheline to be read into the cache first before being
163 operated upon. Memory is not then updated by a write until the cache
164 is filled and a cacheline needs to be displaced from the cache to
165 make room. Only at that point is it written back.
166
167 Write-Behind caching is similar to Write-Back caching, except that a
168 write won't fetch a cacheline into the cache if there isn't already
169 one there; it will write directly to memory instead.
170
171 Write-Through caching only fetches cachelines from memory on a
172 read. Writes always get written directly to memory. If the affected
173 cacheline is also in cache, it will be updated too.
174
175 The final option is to turn of caching entirely.
176
177 Note that not all CPUs support Write-Behind caching. If the CPU on
178 which the kernel is running doesn't, it'll fall back to Write-Back
179 caching.
180
181 config FRV_DEFL_CACHE_WBACK
182 bool "Write-Back"
183
184 config FRV_DEFL_CACHE_WBEHIND
185 bool "Write-Behind"
186
187 config FRV_DEFL_CACHE_WTHRU
188 bool "Write-Through"
189
190 config FRV_DEFL_CACHE_DISABLED
191 bool "Disabled"
192
193 endchoice
194
195 menu "CPU core support"
196
197 config CPU_FR401
198 bool "Include FR401 core support"
199 depends on !MMU
200 default y
201 help
202 This enables support for the FR401, FR401A and FR403 CPUs
203
204 config CPU_FR405
205 bool "Include FR405 core support"
206 depends on !MMU
207 default y
208 help
209 This enables support for the FR405 CPU
210
211 config CPU_FR451
212 bool "Include FR451 core support"
213 default y
214 help
215 This enables support for the FR451 CPU
216
217 config CPU_FR451_COMPILE
218 bool "Specifically compile for FR451 core"
219 depends on CPU_FR451 && !CPU_FR401 && !CPU_FR405 && !CPU_FR551
220 default y
221 help
222 This causes appropriate flags to be passed to the compiler to
223 optimise for the FR451 CPU
224
225 config CPU_FR551
226 bool "Include FR551 core support"
227 depends on !MMU
228 default y
229 help
230 This enables support for the FR555 CPU
231
232 config CPU_FR551_COMPILE
233 bool "Specifically compile for FR551 core"
234 depends on CPU_FR551 && !CPU_FR401 && !CPU_FR405 && !CPU_FR451
235 default y
236 help
237 This causes appropriate flags to be passed to the compiler to
238 optimise for the FR555 CPU
239
240 config FRV_L1_CACHE_SHIFT
241 int
242 default "5" if CPU_FR401 || CPU_FR405 || CPU_FR451
243 default "6" if CPU_FR551
244
245 endmenu
246
247 choice
248 prompt "System support"
249 default MB93091_VDK
250
251 config MB93091_VDK
252 bool "MB93091 CPU board with or without motherboard"
253
254 config MB93093_PDK
255 bool "MB93093 PDK unit"
256
257 endchoice
258
259 if MB93091_VDK
260 choice
261 prompt "Motherboard support"
262 default MB93090_MB00
263
264 config MB93090_MB00
265 bool "Use the MB93090-MB00 motherboard"
266 help
267 Select this option if the MB93091 CPU board is going to be used with
268 a MB93090-MB00 VDK motherboard
269
270 config MB93091_NO_MB
271 bool "Use standalone"
272 help
273 Select this option if the MB93091 CPU board is going to be used
274 without a motherboard
275
276 endchoice
277 endif
278
279 config FUJITSU_MB93493
280 bool "MB93493 Multimedia chip"
281 help
282 Select this option if the MB93493 multimedia chip is going to be
283 used.
284
285 choice
286 prompt "GP-Relative data support"
287 default GPREL_DATA_8
288 help
289 This option controls what data, if any, should be placed in the GP
290 relative data sections. Using this means that the compiler can
291 generate accesses to the data using GR16-relative addressing which
292 is faster than absolute instructions and saves space (2 instructions
293 per access).
294
295 However, the GPREL region is limited in size because the immediate
296 value used in the load and store instructions is limited to a 12-bit
297 signed number.
298
299 So if the linker starts complaining that accesses to GPREL data are
300 out of range, try changing this option from the default.
301
302 Note that modules will always be compiled with this feature disabled
303 as the module data will not be in range of the GP base address.
304
305 config GPREL_DATA_8
306 bool "Put data objects of up to 8 bytes into GP-REL"
307
308 config GPREL_DATA_4
309 bool "Put data objects of up to 4 bytes into GP-REL"
310
311 config GPREL_DATA_NONE
312 bool "Don't use GP-REL"
313
314 endchoice
315
316 config FRV_ONCPU_SERIAL
317 bool "Use on-CPU serial ports"
318 select SERIAL_8250
319 default y
320
321 config PCI
322 bool "Use PCI"
323 depends on MB93090_MB00
324 default y
325 select GENERIC_PCI_IOMAP
326 help
327 Some FR-V systems (such as the MB93090-MB00 VDK) have PCI
328 onboard. If you have one of these boards and you wish to use the PCI
329 facilities, say Y here.
330
331 config RESERVE_DMA_COHERENT
332 bool "Reserve DMA coherent memory"
333 depends on PCI && !MMU
334 default y
335 help
336 Many PCI drivers require access to uncached memory for DMA device
337 communications (such as is done with some Ethernet buffer rings). If
338 a fully featured MMU is available, this can be done through page
339 table settings, but if not, a region has to be set aside and marked
340 with a special DAMPR register.
341
342 Setting this option causes uClinux to set aside a portion of the
343 available memory for use in this manner. The memory will then be
344 unavailable for normal kernel use.
345
346 source "drivers/pci/Kconfig"
347
348 source "drivers/pcmcia/Kconfig"
349
350 menu "Power management options"
351
352 config ARCH_SUSPEND_POSSIBLE
353 def_bool y
354
355 source kernel/power/Kconfig
356 endmenu
357
358 endmenu
359
360
361 menu "Executable formats"
362
363 source "fs/Kconfig.binfmt"
364
365 endmenu
366
367 source "net/Kconfig"
368
369 source "drivers/Kconfig"
370
371 source "fs/Kconfig"
372
373 source "arch/frv/Kconfig.debug"
374
375 source "security/Kconfig"
376
377 source "crypto/Kconfig"
378
379 source "lib/Kconfig"
This page took 0.038199 seconds and 5 git commands to generate.