3 source "lib/Kconfig.debug"
6 bool "Filter access to /dev/mem"
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.
14 If this option is switched on, the /dev/mem file only allows
15 userspace access to memory mapped peripherals.
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 ;).
25 depends on !THUMB2_KERNEL
26 default y if !ARM_UNWIND || FUNCTION_GRAPH_TRACER
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.
34 bool "Enable stack unwinding support (EXPERIMENTAL)"
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.
46 depends on FUNCTION_TRACER && FRAME_POINTER
50 bool "Verbose user fault messages"
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.
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:
60 1 - undefined instruction events
62 4 - invalid data aborts
66 # These options are only for real kernel hackers who want to get their hands dirty.
68 bool "Kernel low-level debugging functions (read help!)"
69 depends on DEBUG_KERNEL
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.
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.
81 prompt "Kernel low-level debugging port"
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
88 config AT91_DEBUG_LL_DBGU1
89 bool "Kernel low-level debugging on 9263 and 9g45"
90 depends on HAVE_AT91_DBGU1
92 config DEBUG_CLPS711X_UART1
93 bool "Kernel low-level debugging messages via UART1"
94 depends on ARCH_CLPS711X
96 Say Y here if you want the debug print routines to direct
97 their output to the first serial port on these devices.
99 config DEBUG_CLPS711X_UART2
100 bool "Kernel low-level debugging messages via UART2"
101 depends on ARCH_CLPS711X
103 Say Y here if you want the debug print routines to direct
104 their output to the second serial port on these devices.
106 config DEBUG_DAVINCI_DA8XX_UART1
107 bool "Kernel low-level debugging on DaVinci DA8XX using UART1"
108 depends on ARCH_DAVINCI_DA8XX
110 Say Y here if you want the debug print routines to direct
111 their output to UART1 serial port on DaVinci DA8XX devices.
113 config DEBUG_DAVINCI_DA8XX_UART2
114 bool "Kernel low-level debugging on DaVinci DA8XX using UART2"
115 depends on ARCH_DAVINCI_DA8XX
117 Say Y here if you want the debug print routines to direct
118 their output to UART2 serial port on DaVinci DA8XX devices.
120 config DEBUG_DAVINCI_DMx_UART0
121 bool "Kernel low-level debugging on DaVinci DMx using UART0"
122 depends on ARCH_DAVINCI_DMx
124 Say Y here if you want the debug print routines to direct
125 their output to UART0 serial port on DaVinci DMx devices.
127 config DEBUG_DAVINCI_TNETV107X_UART1
128 bool "Kernel low-level debugging on DaVinci TNETV107x using UART1"
129 depends on ARCH_DAVINCI_TNETV107X
131 Say Y here if you want the debug print routines to direct
132 their output to UART1 serial port on DaVinci TNETV107X
135 config DEBUG_ZYNQ_UART0
136 bool "Kernel low-level debugging on Xilinx Zynq using UART0"
139 Say Y here if you want the debug print routines to direct
140 their output to UART0 on the Zynq platform.
142 config DEBUG_ZYNQ_UART1
143 bool "Kernel low-level debugging on Xilinx Zynq using UART1"
146 Say Y here if you want the debug print routines to direct
147 their output to UART1 on the Zynq platform.
149 If you have a ZC702 board and want early boot messages to
150 appear on the USB serial adaptor, select this option.
152 config DEBUG_DC21285_PORT
153 bool "Kernel low-level debugging messages via footbridge serial port"
154 depends on FOOTBRIDGE
156 Say Y here if you want the debug print routines to direct
157 their output to the serial port in the DC21285 (Footbridge).
159 config DEBUG_FOOTBRIDGE_COM1
160 bool "Kernel low-level debugging messages via footbridge 8250 at PCI COM1"
161 depends on FOOTBRIDGE
163 Say Y here if you want the debug print routines to direct
164 their output to the 8250 at PCI COM1.
166 config DEBUG_HIGHBANK_UART
167 bool "Kernel low-level debugging messages via Highbank UART"
168 depends on ARCH_HIGHBANK
170 Say Y here if you want the debug print routines to direct
171 their output to the UART on Highbank based devices.
173 config DEBUG_IMX1_UART
174 bool "i.MX1 Debug UART"
177 Say Y here if you want kernel low-level debugging support
180 config DEBUG_IMX23_UART
181 bool "i.MX23 Debug UART"
184 Say Y here if you want kernel low-level debugging support
187 config DEBUG_IMX25_UART
188 bool "i.MX25 Debug UART"
191 Say Y here if you want kernel low-level debugging support
194 config DEBUG_IMX21_IMX27_UART
195 bool "i.MX21 and i.MX27 Debug UART"
196 depends on SOC_IMX21 || SOC_IMX27
198 Say Y here if you want kernel low-level debugging support
201 config DEBUG_IMX28_UART
202 bool "i.MX28 Debug UART"
205 Say Y here if you want kernel low-level debugging support
208 config DEBUG_IMX31_IMX35_UART
209 bool "i.MX31 and i.MX35 Debug UART"
210 depends on SOC_IMX31 || SOC_IMX35
212 Say Y here if you want kernel low-level debugging support
215 config DEBUG_IMX51_UART
216 bool "i.MX51 Debug UART"
219 Say Y here if you want kernel low-level debugging support
222 config DEBUG_IMX53_UART
223 bool "i.MX53 Debug UART"
226 Say Y here if you want kernel low-level debugging support
229 config DEBUG_IMX6Q_UART
230 bool "i.MX6Q Debug UART"
233 Say Y here if you want kernel low-level debugging support
236 config DEBUG_MMP_UART2
237 bool "Kernel low-level debugging message via MMP UART2"
240 Say Y here if you want kernel low-level debugging support
243 config DEBUG_MMP_UART3
244 bool "Kernel low-level debugging message via MMP UART3"
247 Say Y here if you want kernel low-level debugging support
250 config DEBUG_MSM_UART1
251 bool "Kernel low-level debugging messages via MSM UART1"
252 depends on ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50
254 Say Y here if you want the debug print routines to direct
255 their output to the first serial port on MSM devices.
257 config DEBUG_MSM_UART2
258 bool "Kernel low-level debugging messages via MSM UART2"
259 depends on ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50
261 Say Y here if you want the debug print routines to direct
262 their output to the second serial port on MSM devices.
264 config DEBUG_MSM_UART3
265 bool "Kernel low-level debugging messages via MSM UART3"
266 depends on ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50
268 Say Y here if you want the debug print routines to direct
269 their output to the third serial port on MSM devices.
271 config DEBUG_MSM8660_UART
272 bool "Kernel low-level debugging messages via MSM 8660 UART"
273 depends on ARCH_MSM8X60
274 select MSM_HAS_DEBUG_UART_HS
276 Say Y here if you want the debug print routines to direct
277 their output to the serial port on MSM 8660 devices.
279 config DEBUG_MSM8960_UART
280 bool "Kernel low-level debugging messages via MSM 8960 UART"
281 depends on ARCH_MSM8960
282 select MSM_HAS_DEBUG_UART_HS
284 Say Y here if you want the debug print routines to direct
285 their output to the serial port on MSM 8960 devices.
287 config DEBUG_MVEBU_UART
288 bool "Kernel low-level debugging messages via MVEBU UART"
289 depends on ARCH_MVEBU
291 Say Y here if you want kernel low-level debugging support
292 on MVEBU based platforms.
294 config DEBUG_OMAP2PLUS_UART
295 bool "Kernel low-level debugging messages via OMAP2PLUS UART"
296 depends on ARCH_OMAP2PLUS
298 Say Y here if you want kernel low-level debugging support
299 on OMAP2PLUS based platforms.
301 config DEBUG_PICOXCELL_UART
302 depends on ARCH_PICOXCELL
303 bool "Use PicoXcell UART for low-level debug"
305 Say Y here if you want kernel low-level debugging support
306 on PicoXcell based platforms.
308 config DEBUG_REALVIEW_STD_PORT
309 bool "RealView Default UART"
310 depends on ARCH_REALVIEW
312 Say Y here if you want the debug print routines to direct
313 their output to the serial port on RealView EB, PB11MP, PBA8
316 config DEBUG_REALVIEW_PB1176_PORT
317 bool "RealView PB1176 UART"
318 depends on MACH_REALVIEW_PB1176
320 Say Y here if you want the debug print routines to direct
321 their output to the standard serial port on the RealView
324 config DEBUG_S3C_UART0
325 depends on PLAT_SAMSUNG
326 bool "Use S3C UART 0 for low-level debug"
328 Say Y here if you want the debug print routines to direct
329 their output to UART 0. The port must have been initialised
330 by the boot-loader before use.
332 The uncompressor code port configuration is now handled
333 by CONFIG_S3C_LOWLEVEL_UART_PORT.
335 config DEBUG_S3C_UART1
336 depends on PLAT_SAMSUNG
337 bool "Use S3C UART 1 for low-level debug"
339 Say Y here if you want the debug print routines to direct
340 their output to UART 1. The port must have been initialised
341 by the boot-loader before use.
343 The uncompressor code port configuration is now handled
344 by CONFIG_S3C_LOWLEVEL_UART_PORT.
346 config DEBUG_S3C_UART2
347 depends on PLAT_SAMSUNG
348 bool "Use S3C UART 2 for low-level debug"
350 Say Y here if you want the debug print routines to direct
351 their output to UART 2. The port must have been initialised
352 by the boot-loader before use.
354 The uncompressor code port configuration is now handled
355 by CONFIG_S3C_LOWLEVEL_UART_PORT.
357 config DEBUG_S3C_UART3
358 depends on PLAT_SAMSUNG && ARCH_EXYNOS
359 bool "Use S3C UART 3 for low-level debug"
361 Say Y here if you want the debug print routines to direct
362 their output to UART 3. The port must have been initialised
363 by the boot-loader before use.
365 The uncompressor code port configuration is now handled
366 by CONFIG_S3C_LOWLEVEL_UART_PORT.
368 config DEBUG_SOCFPGA_UART
369 depends on ARCH_SOCFPGA
370 bool "Use SOCFPGA UART for low-level debug"
372 Say Y here if you want kernel low-level debugging support
373 on SOCFPGA based platforms.
375 config DEBUG_SUNXI_UART0
376 bool "Kernel low-level debugging messages via sunXi UART0"
377 depends on ARCH_SUNXI
379 Say Y here if you want kernel low-level debugging support
380 on Allwinner A1X based platforms on the UART0.
382 config DEBUG_SUNXI_UART1
383 bool "Kernel low-level debugging messages via sunXi UART1"
384 depends on ARCH_SUNXI
386 Say Y here if you want kernel low-level debugging support
387 on Allwinner A1X based platforms on the UART1.
389 config DEBUG_TEGRA_UART
390 depends on ARCH_TEGRA
391 bool "Use Tegra UART for low-level debug"
393 Say Y here if you want kernel low-level debugging support
394 on Tegra based platforms.
396 config DEBUG_VEXPRESS_UART0_DETECT
397 bool "Autodetect UART0 on Versatile Express Cortex-A core tiles"
398 depends on ARCH_VEXPRESS && CPU_CP15_MMU
400 This option enables a simple heuristic which tries to determine
401 the motherboard's memory map variant (original or RS1) and then
402 choose the relevant UART0 base address.
404 Note that this will only work with standard A-class core tiles,
405 and may fail with non-standard SMM or custom software models.
407 config DEBUG_VEXPRESS_UART0_CA9
408 bool "Use PL011 UART0 at 0x10009000 (V2P-CA9 core tile)"
409 depends on ARCH_VEXPRESS
411 This option selects UART0 at 0x10009000. Except for custom models,
412 this applies only to the V2P-CA9 tile.
414 config DEBUG_VEXPRESS_UART0_RS1
415 bool "Use PL011 UART0 at 0x1c090000 (RS1 complaint tiles)"
416 depends on ARCH_VEXPRESS
418 This option selects UART0 at 0x1c090000. This applies to most
419 of the tiles using the RS1 memory map, including all new A-class
420 core tiles, FPGA-based SMMs and software models.
422 config DEBUG_VT8500_UART0
423 bool "Use UART0 on VIA/Wondermedia SoCs"
424 depends on ARCH_VT8500
426 This option selects UART0 on VIA/Wondermedia System-on-a-chip
427 devices, including VT8500, WM8505, WM8650 and WM8850.
429 config DEBUG_LL_UART_NONE
430 bool "No low-level debugging UART"
431 depends on !ARCH_MULTIPLATFORM
433 Say Y here if your platform doesn't provide a UART option
434 below. This relies on your platform choosing the right UART
435 definition internally in order for low-level debugging to
439 bool "Kernel low-level debugging via EmbeddedICE DCC channel"
441 Say Y here if you want the debug print routines to direct
442 their output to the EmbeddedICE macrocell's DCC channel using
443 co-processor 14. This is known to work on the ARM9 style ICE
444 channel and on the XScale with the PEEDI.
446 Note that the system will appear to hang during boot if there
447 is nothing connected to read from the DCC.
449 config DEBUG_SEMIHOSTING
450 bool "Kernel low-level debug output via semihosting I/O"
452 Semihosting enables code running on an ARM target to use
453 the I/O facilities on a host debugger/emulator through a
454 simple SVC call. The host debugger or emulator must have
455 semihosting enabled for the special svc call to be trapped
456 otherwise the kernel will crash.
458 This is known to work with OpenOCD, as well as
459 ARM's Fast Models, or any other controlling environment
460 that implements semihosting.
462 For more details about semihosting, please see
463 chapter 8 of DUI0203I_rvct_developer_guide.pdf from ARM Ltd.
467 config DEBUG_IMX6Q_UART_PORT
468 int "i.MX6Q Debug UART Port (1-5)" if DEBUG_IMX6Q_UART
473 Choose UART port on which kernel low-level debug messages
477 prompt "Low-level debug console UART"
478 depends on DEBUG_OMAP2PLUS_UART
480 config DEBUG_OMAP2UART1
481 bool "OMAP2/3/4 UART1 (omap2/3 sdp boards and some omap3 boards)"
483 This covers at least h4, 2430sdp, 3430sdp, 3630sdp,
484 omap3 torpedo and 3530 lv som.
486 config DEBUG_OMAP2UART2
487 bool "OMAP2/3/4 UART2"
489 config DEBUG_OMAP2UART3
490 bool "OMAP2 UART3 (n8x0)"
492 config DEBUG_OMAP3UART3
493 bool "OMAP3 UART3 (most omap3 boards)"
495 This covers at least cm_t3x, beagle, crane, devkit8000,
496 igep00x0, ldp, n900, n9(50), pandora, overo, touchbook,
499 config DEBUG_OMAP4UART3
500 bool "OMAP4/5 UART3 (omap4 blaze, panda, omap5 sevm)"
502 config DEBUG_OMAP3UART4
503 bool "OMAP36XX UART4"
505 config DEBUG_OMAP4UART4
508 config DEBUG_TI81XXUART1
509 bool "TI81XX UART1 (ti8148evm)"
511 config DEBUG_TI81XXUART2
514 config DEBUG_TI81XXUART3
515 bool "TI81XX UART3 (ti8168evm)"
517 config DEBUG_AM33XXUART1
520 config DEBUG_ZOOM_UART
525 prompt "Low-level debug console UART"
526 depends on DEBUG_LL && DEBUG_TEGRA_UART
528 config TEGRA_DEBUG_UART_AUTO_ODMDATA
531 Automatically determines which UART to use for low-level debug based
532 on the ODMDATA value. This value is part of the BCT, and is written
533 to the boot memory device using nvflash, or other flashing tool.
534 When bits 19:18 are 3, then bits 17:15 indicate which UART to use;
535 0/1/2/3/4 are UART A/B/C/D/E.
537 config TEGRA_DEBUG_UARTA
540 config TEGRA_DEBUG_UARTB
543 config TEGRA_DEBUG_UARTC
546 config TEGRA_DEBUG_UARTD
549 config TEGRA_DEBUG_UARTE
554 config DEBUG_LL_INCLUDE
556 default "debug/icedcc.S" if DEBUG_ICEDCC
557 default "debug/imx.S" if DEBUG_IMX1_UART || \
558 DEBUG_IMX25_UART || \
559 DEBUG_IMX21_IMX27_UART || \
560 DEBUG_IMX31_IMX35_UART || \
561 DEBUG_IMX51_UART || \
564 default "debug/highbank.S" if DEBUG_HIGHBANK_UART
565 default "debug/mvebu.S" if DEBUG_MVEBU_UART
566 default "debug/omap2plus.S" if DEBUG_OMAP2PLUS_UART
567 default "debug/picoxcell.S" if DEBUG_PICOXCELL_UART
568 default "debug/socfpga.S" if DEBUG_SOCFPGA_UART
569 default "debug/sunxi.S" if DEBUG_SUNXI_UART0 || DEBUG_SUNXI_UART1
570 default "debug/vexpress.S" if DEBUG_VEXPRESS_UART0_DETECT || \
571 DEBUG_VEXPRESS_UART0_CA9 || DEBUG_VEXPRESS_UART0_RS1
572 default "debug/vt8500.S" if DEBUG_VT8500_UART0
573 default "debug/tegra.S" if DEBUG_TEGRA_UART
574 default "debug/zynq.S" if DEBUG_ZYNQ_UART0 || DEBUG_ZYNQ_UART1
575 default "mach/debug-macro.S"
581 Say Y here if you want to have an early console using the
582 kernel low-level debugging functions. Add earlyprintk to your
583 kernel parameters to enable this console.
586 bool "On-chip ETM and ETB"
589 Enables the on-chip embedded trace macrocell and embedded trace
590 buffer driver that will allow you to collect traces of the
593 config ARM_KPROBES_TEST
594 tristate "Kprobes test module"
595 depends on KPROBES && MODULES
597 Perform tests of kprobes API and instruction set simulation.
599 config PID_IN_CONTEXTIDR
600 bool "Write the current PID to the CONTEXTIDR register"
601 depends on CPU_COPY_V6
603 Enabling this option causes the kernel to write the current PID to
604 the PROCID field of the CONTEXTIDR register, at the expense of some
605 additional instructions during context switch. Say Y here only if you
606 are planning to use hardware trace tools with this kernel.