Merge tag 'xtensa-next-20130508' of git://github.com/czankel/xtensa-linux
[GitHub/mt8127/android_kernel_alcatel_ttab.git] / arch / arm / Kconfig.debug
1 menu "Kernel hacking"
2
3 source "lib/Kconfig.debug"
4
5 config STRICT_DEVMEM
6 bool "Filter access to /dev/mem"
7 depends on MMU
8 ---help---
9 If this option is disabled, you allow userspace (root) access to all
10 of memory, including kernel and userspace memory. Accidental
11 access to this is obviously disastrous, but specific access can
12 be used by people debugging the kernel.
13
14 If this option is switched on, the /dev/mem file only allows
15 userspace access to memory mapped peripherals.
16
17 If in doubt, say Y.
18
19 # RMK wants arm kernels compiled with frame pointers or stack unwinding.
20 # If you know what you are doing and are willing to live without stack
21 # traces, you can get a slightly smaller kernel by setting this option to
22 # n, but then RMK will have to kill you ;).
23 config FRAME_POINTER
24 bool
25 depends on !THUMB2_KERNEL
26 default y if !ARM_UNWIND || FUNCTION_GRAPH_TRACER
27 help
28 If you say N here, the resulting kernel will be slightly smaller and
29 faster. However, if neither FRAME_POINTER nor ARM_UNWIND are enabled,
30 when a problem occurs with the kernel, the information that is
31 reported is severely limited.
32
33 config ARM_UNWIND
34 bool "Enable stack unwinding support (EXPERIMENTAL)"
35 depends on AEABI
36 default y
37 help
38 This option enables stack unwinding support in the kernel
39 using the information automatically generated by the
40 compiler. The resulting kernel image is slightly bigger but
41 the performance is not affected. Currently, this feature
42 only works with EABI compilers. If unsure say Y.
43
44 config OLD_MCOUNT
45 bool
46 depends on FUNCTION_TRACER && FRAME_POINTER
47 default y
48
49 config DEBUG_USER
50 bool "Verbose user fault messages"
51 help
52 When a user program crashes due to an exception, the kernel can
53 print a brief message explaining what the problem was. This is
54 sometimes helpful for debugging but serves no purpose on a
55 production system. Most people should say N here.
56
57 In addition, you need to pass user_debug=N on the kernel command
58 line to enable this feature. N consists of the sum of:
59
60 1 - undefined instruction events
61 2 - system calls
62 4 - invalid data aborts
63 8 - SIGSEGV faults
64 16 - SIGBUS faults
65
66 # These options are only for real kernel hackers who want to get their hands dirty.
67 config DEBUG_LL
68 bool "Kernel low-level debugging functions (read help!)"
69 depends on DEBUG_KERNEL
70 help
71 Say Y here to include definitions of printascii, printch, printhex
72 in the kernel. This is helpful if you are debugging code that
73 executes before the console is initialized.
74
75 Note that selecting this option will limit the kernel to a single
76 UART definition, as specified below. Attempting to boot the kernel
77 image on a different platform *will not work*, so this option should
78 not be enabled for kernels that are intended to be portable.
79
80 choice
81 prompt "Kernel low-level debugging port"
82 depends on DEBUG_LL
83
84 config AT91_DEBUG_LL_DBGU0
85 bool "Kernel low-level debugging on rm9200, 9260/9g20, 9261/9g10 and 9rl"
86 depends on HAVE_AT91_DBGU0
87
88 config AT91_DEBUG_LL_DBGU1
89 bool "Kernel low-level debugging on 9263 and 9g45"
90 depends on HAVE_AT91_DBGU1
91
92 config DEBUG_BCM2835
93 bool "Kernel low-level debugging on BCM2835 PL011 UART"
94 depends on ARCH_BCM2835
95
96 config DEBUG_CLPS711X_UART1
97 bool "Kernel low-level debugging messages via UART1"
98 depends on ARCH_CLPS711X
99 help
100 Say Y here if you want the debug print routines to direct
101 their output to the first serial port on these devices.
102
103 config DEBUG_CLPS711X_UART2
104 bool "Kernel low-level debugging messages via UART2"
105 depends on ARCH_CLPS711X
106 help
107 Say Y here if you want the debug print routines to direct
108 their output to the second serial port on these devices.
109
110 config DEBUG_CNS3XXX
111 bool "Kernel Kernel low-level debugging on Cavium Networks CNS3xxx"
112 depends on ARCH_CNS3XXX
113 help
114 Say Y here if you want the debug print routines to direct
115 their output to the CNS3xxx UART0.
116
117 config DEBUG_DAVINCI_DA8XX_UART1
118 bool "Kernel low-level debugging on DaVinci DA8XX using UART1"
119 depends on ARCH_DAVINCI_DA8XX
120 help
121 Say Y here if you want the debug print routines to direct
122 their output to UART1 serial port on DaVinci DA8XX devices.
123
124 config DEBUG_DAVINCI_DA8XX_UART2
125 bool "Kernel low-level debugging on DaVinci DA8XX using UART2"
126 depends on ARCH_DAVINCI_DA8XX
127 help
128 Say Y here if you want the debug print routines to direct
129 their output to UART2 serial port on DaVinci DA8XX devices.
130
131 config DEBUG_DAVINCI_DMx_UART0
132 bool "Kernel low-level debugging on DaVinci DMx using UART0"
133 depends on ARCH_DAVINCI_DMx
134 help
135 Say Y here if you want the debug print routines to direct
136 their output to UART0 serial port on DaVinci DMx devices.
137
138 config DEBUG_DAVINCI_TNETV107X_UART1
139 bool "Kernel low-level debugging on DaVinci TNETV107x using UART1"
140 depends on ARCH_DAVINCI_TNETV107X
141 help
142 Say Y here if you want the debug print routines to direct
143 their output to UART1 serial port on DaVinci TNETV107X
144 devices.
145
146 config DEBUG_ZYNQ_UART0
147 bool "Kernel low-level debugging on Xilinx Zynq using UART0"
148 depends on ARCH_ZYNQ
149 help
150 Say Y here if you want the debug print routines to direct
151 their output to UART0 on the Zynq platform.
152
153 config DEBUG_ZYNQ_UART1
154 bool "Kernel low-level debugging on Xilinx Zynq using UART1"
155 depends on ARCH_ZYNQ
156 help
157 Say Y here if you want the debug print routines to direct
158 their output to UART1 on the Zynq platform.
159
160 If you have a ZC702 board and want early boot messages to
161 appear on the USB serial adaptor, select this option.
162
163 config DEBUG_DC21285_PORT
164 bool "Kernel low-level debugging messages via footbridge serial port"
165 depends on FOOTBRIDGE
166 help
167 Say Y here if you want the debug print routines to direct
168 their output to the serial port in the DC21285 (Footbridge).
169
170 config DEBUG_FOOTBRIDGE_COM1
171 bool "Kernel low-level debugging messages via footbridge 8250 at PCI COM1"
172 depends on FOOTBRIDGE
173 help
174 Say Y here if you want the debug print routines to direct
175 their output to the 8250 at PCI COM1.
176
177 config DEBUG_HIGHBANK_UART
178 bool "Kernel low-level debugging messages via Highbank UART"
179 depends on ARCH_HIGHBANK
180 help
181 Say Y here if you want the debug print routines to direct
182 their output to the UART on Highbank based devices.
183
184 config DEBUG_IMX1_UART
185 bool "i.MX1 Debug UART"
186 depends on SOC_IMX1
187 help
188 Say Y here if you want kernel low-level debugging support
189 on i.MX1.
190
191 config DEBUG_IMX23_UART
192 bool "i.MX23 Debug UART"
193 depends on SOC_IMX23
194 help
195 Say Y here if you want kernel low-level debugging support
196 on i.MX23.
197
198 config DEBUG_IMX25_UART
199 bool "i.MX25 Debug UART"
200 depends on SOC_IMX25
201 help
202 Say Y here if you want kernel low-level debugging support
203 on i.MX25.
204
205 config DEBUG_IMX21_IMX27_UART
206 bool "i.MX21 and i.MX27 Debug UART"
207 depends on SOC_IMX21 || SOC_IMX27
208 help
209 Say Y here if you want kernel low-level debugging support
210 on i.MX21 or i.MX27.
211
212 config DEBUG_IMX28_UART
213 bool "i.MX28 Debug UART"
214 depends on SOC_IMX28
215 help
216 Say Y here if you want kernel low-level debugging support
217 on i.MX28.
218
219 config DEBUG_IMX31_UART
220 bool "i.MX31 Debug UART"
221 depends on SOC_IMX31
222 help
223 Say Y here if you want kernel low-level debugging support
224 on i.MX31.
225
226 config DEBUG_IMX35_UART
227 bool "i.MX35 Debug UART"
228 depends on SOC_IMX35
229 help
230 Say Y here if you want kernel low-level debugging support
231 on i.MX35.
232
233 config DEBUG_IMX51_UART
234 bool "i.MX51 Debug UART"
235 depends on SOC_IMX51
236 help
237 Say Y here if you want kernel low-level debugging support
238 on i.MX51.
239
240 config DEBUG_IMX53_UART
241 bool "i.MX53 Debug UART"
242 depends on SOC_IMX53
243 help
244 Say Y here if you want kernel low-level debugging support
245 on i.MX53.
246
247 config DEBUG_IMX6Q_UART
248 bool "i.MX6Q/DL Debug UART"
249 depends on SOC_IMX6Q
250 help
251 Say Y here if you want kernel low-level debugging support
252 on i.MX6Q/DL.
253
254 config DEBUG_MMP_UART2
255 bool "Kernel low-level debugging message via MMP UART2"
256 depends on ARCH_MMP
257 help
258 Say Y here if you want kernel low-level debugging support
259 on MMP UART2.
260
261 config DEBUG_MMP_UART3
262 bool "Kernel low-level debugging message via MMP UART3"
263 depends on ARCH_MMP
264 help
265 Say Y here if you want kernel low-level debugging support
266 on MMP UART3.
267
268 config DEBUG_MSM_UART1
269 bool "Kernel low-level debugging messages via MSM UART1"
270 depends on ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50
271 help
272 Say Y here if you want the debug print routines to direct
273 their output to the first serial port on MSM devices.
274
275 config DEBUG_MSM_UART2
276 bool "Kernel low-level debugging messages via MSM UART2"
277 depends on ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50
278 help
279 Say Y here if you want the debug print routines to direct
280 their output to the second serial port on MSM devices.
281
282 config DEBUG_MSM_UART3
283 bool "Kernel low-level debugging messages via MSM UART3"
284 depends on ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50
285 help
286 Say Y here if you want the debug print routines to direct
287 their output to the third serial port on MSM devices.
288
289 config DEBUG_MSM8660_UART
290 bool "Kernel low-level debugging messages via MSM 8660 UART"
291 depends on ARCH_MSM8X60
292 select MSM_HAS_DEBUG_UART_HS
293 help
294 Say Y here if you want the debug print routines to direct
295 their output to the serial port on MSM 8660 devices.
296
297 config DEBUG_MSM8960_UART
298 bool "Kernel low-level debugging messages via MSM 8960 UART"
299 depends on ARCH_MSM8960
300 select MSM_HAS_DEBUG_UART_HS
301 help
302 Say Y here if you want the debug print routines to direct
303 their output to the serial port on MSM 8960 devices.
304
305 config DEBUG_MVEBU_UART
306 bool "Kernel low-level debugging messages via MVEBU UART"
307 depends on ARCH_MVEBU
308 help
309 Say Y here if you want kernel low-level debugging support
310 on MVEBU based platforms.
311
312 config DEBUG_NOMADIK_UART
313 bool "Kernel low-level debugging messages via NOMADIK UART"
314 depends on ARCH_NOMADIK
315 help
316 Say Y here if you want kernel low-level debugging support
317 on NOMADIK based platforms.
318
319 config DEBUG_OMAP2PLUS_UART
320 bool "Kernel low-level debugging messages via OMAP2PLUS UART"
321 depends on ARCH_OMAP2PLUS
322 help
323 Say Y here if you want kernel low-level debugging support
324 on OMAP2PLUS based platforms.
325
326 config DEBUG_PICOXCELL_UART
327 depends on ARCH_PICOXCELL
328 bool "Use PicoXcell UART for low-level debug"
329 help
330 Say Y here if you want kernel low-level debugging support
331 on PicoXcell based platforms.
332
333 config DEBUG_PXA_UART1
334 depends on ARCH_PXA
335 bool "Use PXA UART1 for low-level debug"
336 help
337 Say Y here if you want kernel low-level debugging support
338 on PXA UART1.
339
340 config DEBUG_REALVIEW_STD_PORT
341 bool "RealView Default UART"
342 depends on ARCH_REALVIEW
343 help
344 Say Y here if you want the debug print routines to direct
345 their output to the serial port on RealView EB, PB11MP, PBA8
346 and PBX platforms.
347
348 config DEBUG_REALVIEW_PB1176_PORT
349 bool "RealView PB1176 UART"
350 depends on MACH_REALVIEW_PB1176
351 help
352 Say Y here if you want the debug print routines to direct
353 their output to the standard serial port on the RealView
354 PB1176 platform.
355
356 config DEBUG_S3C_UART0
357 depends on PLAT_SAMSUNG
358 select DEBUG_EXYNOS_UART if ARCH_EXYNOS
359 bool "Use S3C UART 0 for low-level debug"
360 help
361 Say Y here if you want the debug print routines to direct
362 their output to UART 0. The port must have been initialised
363 by the boot-loader before use.
364
365 The uncompressor code port configuration is now handled
366 by CONFIG_S3C_LOWLEVEL_UART_PORT.
367
368 config DEBUG_S3C_UART1
369 depends on PLAT_SAMSUNG
370 select DEBUG_EXYNOS_UART if ARCH_EXYNOS
371 bool "Use S3C UART 1 for low-level debug"
372 help
373 Say Y here if you want the debug print routines to direct
374 their output to UART 1. The port must have been initialised
375 by the boot-loader before use.
376
377 The uncompressor code port configuration is now handled
378 by CONFIG_S3C_LOWLEVEL_UART_PORT.
379
380 config DEBUG_S3C_UART2
381 depends on PLAT_SAMSUNG
382 select DEBUG_EXYNOS_UART if ARCH_EXYNOS
383 bool "Use S3C UART 2 for low-level debug"
384 help
385 Say Y here if you want the debug print routines to direct
386 their output to UART 2. The port must have been initialised
387 by the boot-loader before use.
388
389 The uncompressor code port configuration is now handled
390 by CONFIG_S3C_LOWLEVEL_UART_PORT.
391
392 config DEBUG_S3C_UART3
393 depends on PLAT_SAMSUNG && ARCH_EXYNOS
394 select DEBUG_EXYNOS_UART
395 bool "Use S3C UART 3 for low-level debug"
396 help
397 Say Y here if you want the debug print routines to direct
398 their output to UART 3. The port must have been initialised
399 by the boot-loader before use.
400
401 The uncompressor code port configuration is now handled
402 by CONFIG_S3C_LOWLEVEL_UART_PORT.
403
404 config DEBUG_SOCFPGA_UART
405 depends on ARCH_SOCFPGA
406 bool "Use SOCFPGA UART for low-level debug"
407 help
408 Say Y here if you want kernel low-level debugging support
409 on SOCFPGA based platforms.
410
411 config DEBUG_SUNXI_UART0
412 bool "Kernel low-level debugging messages via sunXi UART0"
413 depends on ARCH_SUNXI
414 help
415 Say Y here if you want kernel low-level debugging support
416 on Allwinner A1X based platforms on the UART0.
417
418 config DEBUG_SUNXI_UART1
419 bool "Kernel low-level debugging messages via sunXi UART1"
420 depends on ARCH_SUNXI
421 help
422 Say Y here if you want kernel low-level debugging support
423 on Allwinner A1X based platforms on the UART1.
424
425 config DEBUG_TEGRA_UART
426 depends on ARCH_TEGRA
427 bool "Use Tegra UART for low-level debug"
428 help
429 Say Y here if you want kernel low-level debugging support
430 on Tegra based platforms.
431
432 config DEBUG_SIRFPRIMA2_UART1
433 bool "Kernel low-level debugging messages via SiRFprimaII UART1"
434 depends on ARCH_PRIMA2
435 help
436 Say Y here if you want the debug print routines to direct
437 their output to the uart1 port on SiRFprimaII devices.
438
439 config DEBUG_SIRFMARCO_UART1
440 bool "Kernel low-level debugging messages via SiRFmarco UART1"
441 depends on ARCH_MARCO
442 help
443 Say Y here if you want the debug print routines to direct
444 their output to the uart1 port on SiRFmarco devices.
445
446 config DEBUG_UX500_UART
447 depends on ARCH_U8500
448 bool "Use Ux500 UART for low-level debug"
449 help
450 Say Y here if you want kernel low-level debugging support
451 on Ux500 based platforms.
452
453 config DEBUG_VEXPRESS_UART0_DETECT
454 bool "Autodetect UART0 on Versatile Express Cortex-A core tiles"
455 depends on ARCH_VEXPRESS && CPU_CP15_MMU
456 help
457 This option enables a simple heuristic which tries to determine
458 the motherboard's memory map variant (original or RS1) and then
459 choose the relevant UART0 base address.
460
461 Note that this will only work with standard A-class core tiles,
462 and may fail with non-standard SMM or custom software models.
463
464 config DEBUG_VEXPRESS_UART0_CA9
465 bool "Use PL011 UART0 at 0x10009000 (V2P-CA9 core tile)"
466 depends on ARCH_VEXPRESS
467 help
468 This option selects UART0 at 0x10009000. Except for custom models,
469 this applies only to the V2P-CA9 tile.
470
471 config DEBUG_VEXPRESS_UART0_RS1
472 bool "Use PL011 UART0 at 0x1c090000 (RS1 complaint tiles)"
473 depends on ARCH_VEXPRESS
474 help
475 This option selects UART0 at 0x1c090000. This applies to most
476 of the tiles using the RS1 memory map, including all new A-class
477 core tiles, FPGA-based SMMs and software models.
478
479 config DEBUG_VT8500_UART0
480 bool "Use UART0 on VIA/Wondermedia SoCs"
481 depends on ARCH_VT8500
482 help
483 This option selects UART0 on VIA/Wondermedia System-on-a-chip
484 devices, including VT8500, WM8505, WM8650 and WM8850.
485
486 config DEBUG_LL_UART_NONE
487 bool "No low-level debugging UART"
488 depends on !ARCH_MULTIPLATFORM
489 help
490 Say Y here if your platform doesn't provide a UART option
491 below. This relies on your platform choosing the right UART
492 definition internally in order for low-level debugging to
493 work.
494
495 config DEBUG_ICEDCC
496 bool "Kernel low-level debugging via EmbeddedICE DCC channel"
497 help
498 Say Y here if you want the debug print routines to direct
499 their output to the EmbeddedICE macrocell's DCC channel using
500 co-processor 14. This is known to work on the ARM9 style ICE
501 channel and on the XScale with the PEEDI.
502
503 Note that the system will appear to hang during boot if there
504 is nothing connected to read from the DCC.
505
506 config DEBUG_SEMIHOSTING
507 bool "Kernel low-level debug output via semihosting I/O"
508 help
509 Semihosting enables code running on an ARM target to use
510 the I/O facilities on a host debugger/emulator through a
511 simple SVC call. The host debugger or emulator must have
512 semihosting enabled for the special svc call to be trapped
513 otherwise the kernel will crash.
514
515 This is known to work with OpenOCD, as well as
516 ARM's Fast Models, or any other controlling environment
517 that implements semihosting.
518
519 For more details about semihosting, please see
520 chapter 8 of DUI0203I_rvct_developer_guide.pdf from ARM Ltd.
521
522 endchoice
523
524 config DEBUG_EXYNOS_UART
525 bool
526
527 config DEBUG_IMX_UART_PORT
528 int "i.MX Debug UART Port Selection" if DEBUG_IMX1_UART || \
529 DEBUG_IMX25_UART || \
530 DEBUG_IMX21_IMX27_UART || \
531 DEBUG_IMX31_UART || \
532 DEBUG_IMX35_UART || \
533 DEBUG_IMX51_UART || \
534 DEBUG_IMX53_UART || \
535 DEBUG_IMX6Q_UART
536 default 1
537 depends on ARCH_MXC
538 help
539 Choose UART port on which kernel low-level debug messages
540 should be output.
541
542 choice
543 prompt "Low-level debug console UART"
544 depends on DEBUG_OMAP2PLUS_UART
545
546 config DEBUG_OMAP2UART1
547 bool "OMAP2/3/4 UART1 (omap2/3 sdp boards and some omap3 boards)"
548 help
549 This covers at least h4, 2430sdp, 3430sdp, 3630sdp,
550 omap3 torpedo and 3530 lv som.
551
552 config DEBUG_OMAP2UART2
553 bool "OMAP2/3/4 UART2"
554
555 config DEBUG_OMAP2UART3
556 bool "OMAP2 UART3 (n8x0)"
557
558 config DEBUG_OMAP3UART3
559 bool "OMAP3 UART3 (most omap3 boards)"
560 help
561 This covers at least cm_t3x, beagle, crane, devkit8000,
562 igep00x0, ldp, n900, n9(50), pandora, overo, touchbook,
563 and 3517evm.
564
565 config DEBUG_OMAP4UART3
566 bool "OMAP4/5 UART3 (omap4 blaze, panda, omap5 sevm)"
567
568 config DEBUG_OMAP3UART4
569 bool "OMAP36XX UART4"
570
571 config DEBUG_OMAP4UART4
572 bool "OMAP4/5 UART4"
573
574 config DEBUG_TI81XXUART1
575 bool "TI81XX UART1 (ti8148evm)"
576
577 config DEBUG_TI81XXUART2
578 bool "TI81XX UART2"
579
580 config DEBUG_TI81XXUART3
581 bool "TI81XX UART3 (ti8168evm)"
582
583 config DEBUG_AM33XXUART1
584 bool "AM33XX UART1"
585
586 config DEBUG_ZOOM_UART
587 bool "Zoom2/3 UART"
588 endchoice
589
590 choice
591 prompt "Low-level debug console UART"
592 depends on DEBUG_LL && DEBUG_TEGRA_UART
593
594 config TEGRA_DEBUG_UART_AUTO_ODMDATA
595 bool "Via ODMDATA"
596 help
597 Automatically determines which UART to use for low-level debug based
598 on the ODMDATA value. This value is part of the BCT, and is written
599 to the boot memory device using nvflash, or other flashing tool.
600 When bits 19:18 are 3, then bits 17:15 indicate which UART to use;
601 0/1/2/3/4 are UART A/B/C/D/E.
602
603 config TEGRA_DEBUG_UARTA
604 bool "UART A"
605
606 config TEGRA_DEBUG_UARTB
607 bool "UART B"
608
609 config TEGRA_DEBUG_UARTC
610 bool "UART C"
611
612 config TEGRA_DEBUG_UARTD
613 bool "UART D"
614
615 config TEGRA_DEBUG_UARTE
616 bool "UART E"
617
618 endchoice
619
620 config DEBUG_LL_INCLUDE
621 string
622 default "debug/bcm2835.S" if DEBUG_BCM2835
623 default "debug/cns3xxx.S" if DEBUG_CNS3XXX
624 default "debug/exynos.S" if DEBUG_EXYNOS_UART
625 default "debug/highbank.S" if DEBUG_HIGHBANK_UART
626 default "debug/icedcc.S" if DEBUG_ICEDCC
627 default "debug/imx.S" if DEBUG_IMX1_UART || \
628 DEBUG_IMX25_UART || \
629 DEBUG_IMX21_IMX27_UART || \
630 DEBUG_IMX31_UART || \
631 DEBUG_IMX35_UART || \
632 DEBUG_IMX51_UART || \
633 DEBUG_IMX53_UART ||\
634 DEBUG_IMX6Q_UART
635 default "debug/mvebu.S" if DEBUG_MVEBU_UART
636 default "debug/mxs.S" if DEBUG_IMX23_UART || DEBUG_IMX28_UART
637 default "debug/nomadik.S" if DEBUG_NOMADIK_UART
638 default "debug/omap2plus.S" if DEBUG_OMAP2PLUS_UART
639 default "debug/picoxcell.S" if DEBUG_PICOXCELL_UART
640 default "debug/pxa.S" if DEBUG_PXA_UART1 || DEBUG_MMP_UART2 || \
641 DEBUG_MMP_UART3
642 default "debug/sirf.S" if DEBUG_SIRFPRIMA2_UART1 || DEBUG_SIRFMARCO_UART1
643 default "debug/socfpga.S" if DEBUG_SOCFPGA_UART
644 default "debug/sunxi.S" if DEBUG_SUNXI_UART0 || DEBUG_SUNXI_UART1
645 default "debug/tegra.S" if DEBUG_TEGRA_UART
646 default "debug/ux500.S" if DEBUG_UX500_UART
647 default "debug/vexpress.S" if DEBUG_VEXPRESS_UART0_DETECT || \
648 DEBUG_VEXPRESS_UART0_CA9 || DEBUG_VEXPRESS_UART0_RS1
649 default "debug/vt8500.S" if DEBUG_VT8500_UART0
650 default "debug/zynq.S" if DEBUG_ZYNQ_UART0 || DEBUG_ZYNQ_UART1
651 default "mach/debug-macro.S"
652
653 config DEBUG_UNCOMPRESS
654 bool
655 default y if ARCH_MULTIPLATFORM && DEBUG_LL && \
656 !DEBUG_OMAP2PLUS_UART && \
657 !DEBUG_TEGRA_UART
658
659 config UNCOMPRESS_INCLUDE
660 string
661 default "debug/uncompress.h" if ARCH_MULTIPLATFORM
662 default "mach/uncompress.h"
663
664 config EARLY_PRINTK
665 bool "Early printk"
666 depends on DEBUG_LL
667 help
668 Say Y here if you want to have an early console using the
669 kernel low-level debugging functions. Add earlyprintk to your
670 kernel parameters to enable this console.
671
672 config OC_ETM
673 bool "On-chip ETM and ETB"
674 depends on ARM_AMBA
675 help
676 Enables the on-chip embedded trace macrocell and embedded trace
677 buffer driver that will allow you to collect traces of the
678 kernel code.
679
680 config ARM_KPROBES_TEST
681 tristate "Kprobes test module"
682 depends on KPROBES && MODULES
683 help
684 Perform tests of kprobes API and instruction set simulation.
685
686 config PID_IN_CONTEXTIDR
687 bool "Write the current PID to the CONTEXTIDR register"
688 depends on CPU_COPY_V6
689 help
690 Enabling this option causes the kernel to write the current PID to
691 the PROCID field of the CONTEXTIDR register, at the expense of some
692 additional instructions during context switch. Say Y here only if you
693 are planning to use hardware trace tools with this kernel.
694
695 endmenu