[GitHub/mt8127/android_kernel_alcatel_ttab.git] / arch / arm / Kconfig.debug

menu "Kernel hacking"

source "lib/Kconfig.debug"

config STRICT_DEVMEM
	bool "Filter access to /dev/mem"
	depends on MMU
	---help---
	  If this option is disabled, you allow userspace (root) access to all
	  of memory, including kernel and userspace memory. Accidental
	  access to this is obviously disastrous, but specific access can
	  be used by people debugging the kernel.

	  If this option is switched on, the /dev/mem file only allows
	  userspace access to memory mapped peripherals.

          If in doubt, say Y.

# RMK wants arm kernels compiled with frame pointers or stack unwinding.
# If you know what you are doing and are willing to live without stack
# traces, you can get a slightly smaller kernel by setting this option to
# n, but then RMK will have to kill you ;).
config FRAME_POINTER
	bool
	depends on !THUMB2_KERNEL
	default y if !ARM_UNWIND || FUNCTION_GRAPH_TRACER
	help
	  If you say N here, the resulting kernel will be slightly smaller and
	  faster. However, if neither FRAME_POINTER nor ARM_UNWIND are enabled,
	  when a problem occurs with the kernel, the information that is
	  reported is severely limited.

config ARM_UNWIND
	bool "Enable stack unwinding support (EXPERIMENTAL)"
	depends on AEABI && EXPERIMENTAL
	default y
	help
	  This option enables stack unwinding support in the kernel
	  using the information automatically generated by the
	  compiler. The resulting kernel image is slightly bigger but
	  the performance is not affected. Currently, this feature
	  only works with EABI compilers. If unsure say Y.

config OLD_MCOUNT
	bool
	depends on FUNCTION_TRACER && FRAME_POINTER
	default y

config DEBUG_USER
	bool "Verbose user fault messages"
	help
	  When a user program crashes due to an exception, the kernel can
	  print a brief message explaining what the problem was. This is
	  sometimes helpful for debugging but serves no purpose on a
	  production system. Most people should say N here.

	  In addition, you need to pass user_debug=N on the kernel command
	  line to enable this feature.  N consists of the sum of:

	      1 - undefined instruction events
	      2 - system calls
	      4 - invalid data aborts
	      8 - SIGSEGV faults
	     16 - SIGBUS faults

# These options are only for real kernel hackers who want to get their hands dirty.
config DEBUG_LL
	bool "Kernel low-level debugging functions (read help!)"
	depends on DEBUG_KERNEL
	help
	  Say Y here to include definitions of printascii, printch, printhex
	  in the kernel.  This is helpful if you are debugging code that
	  executes before the console is initialized.

	  Note that selecting this option will limit the kernel to a single
	  UART definition, as specified below. Attempting to boot the kernel
	  image on a different platform *will not work*, so this option should
	  not be enabled for kernels that are intended to be portable.

choice
	prompt "Kernel low-level debugging port"
	depends on DEBUG_LL

	config AT91_DEBUG_LL_DBGU0
		bool "Kernel low-level debugging on rm9200, 9260/9g20, 9261/9g10 and 9rl"
		depends on HAVE_AT91_DBGU0

	config AT91_DEBUG_LL_DBGU1
		bool "Kernel low-level debugging on 9263 and 9g45"
		depends on HAVE_AT91_DBGU1

	config DEBUG_CLPS711X_UART1
		bool "Kernel low-level debugging messages via UART1"
		depends on ARCH_CLPS711X
		help
		  Say Y here if you want the debug print routines to direct
		  their output to the first serial port on these devices.

	config DEBUG_CLPS711X_UART2
		bool "Kernel low-level debugging messages via UART2"
		depends on ARCH_CLPS711X
		help
		  Say Y here if you want the debug print routines to direct
		  their output to the second serial port on these devices.

	config DEBUG_DAVINCI_DA8XX_UART1
		bool "Kernel low-level debugging on DaVinci DA8XX using UART1"
		depends on ARCH_DAVINCI_DA8XX
		help
		  Say Y here if you want the debug print routines to direct
		  their output to UART1 serial port on DaVinci DA8XX devices.

	config DEBUG_DAVINCI_DA8XX_UART2
		bool "Kernel low-level debugging on DaVinci DA8XX using UART2"
		depends on ARCH_DAVINCI_DA8XX
		help
		  Say Y here if you want the debug print routines to direct
		  their output to UART2 serial port on DaVinci DA8XX devices.

	config DEBUG_DAVINCI_DMx_UART0
		bool "Kernel low-level debugging on DaVinci DMx using UART0"
		depends on ARCH_DAVINCI_DMx
		help
		  Say Y here if you want the debug print routines to direct
		  their output to UART0 serial port on DaVinci DMx devices.

	config DEBUG_DAVINCI_TNETV107X_UART1
		bool "Kernel low-level debugging on DaVinci TNETV107x using UART1"
		depends on ARCH_DAVINCI_TNETV107X
		help
		  Say Y here if you want the debug print routines to direct
		  their output to UART1 serial port on DaVinci TNETV107X
		  devices.

	config DEBUG_ZYNQ_UART0
		bool "Kernel low-level debugging on Xilinx Zynq using UART0"
		depends on ARCH_ZYNQ
		help
		  Say Y here if you want the debug print routines to direct
		  their output to UART0 on the Zynq platform.

	config DEBUG_ZYNQ_UART1
		bool "Kernel low-level debugging on Xilinx Zynq using UART1"
		depends on ARCH_ZYNQ
		help
		  Say Y here if you want the debug print routines to direct
		  their output to UART1 on the Zynq platform.

		  If you have a ZC702 board and want early boot messages to
		  appear on the USB serial adaptor, select this option.

	config DEBUG_DC21285_PORT
		bool "Kernel low-level debugging messages via footbridge serial port"
		depends on FOOTBRIDGE
		help
		  Say Y here if you want the debug print routines to direct
		  their output to the serial port in the DC21285 (Footbridge).

	config DEBUG_FOOTBRIDGE_COM1
		bool "Kernel low-level debugging messages via footbridge 8250 at PCI COM1"
		depends on FOOTBRIDGE
		help
		  Say Y here if you want the debug print routines to direct
		  their output to the 8250 at PCI COM1.

	config DEBUG_HIGHBANK_UART
		bool "Kernel low-level debugging messages via Highbank UART"
		depends on ARCH_HIGHBANK
		help
		  Say Y here if you want the debug print routines to direct
		  their output to the UART on Highbank based devices.

	config DEBUG_IMX1_UART
		bool "i.MX1 Debug UART"
		depends on SOC_IMX1
		help
		  Say Y here if you want kernel low-level debugging support
		  on i.MX1.

	config DEBUG_IMX23_UART
		bool "i.MX23 Debug UART"
		depends on SOC_IMX23
		help
		  Say Y here if you want kernel low-level debugging support
		  on i.MX23.

	config DEBUG_IMX25_UART
		bool "i.MX25 Debug UART"
		depends on SOC_IMX25
		help
		  Say Y here if you want kernel low-level debugging support
		  on i.MX25.

	config DEBUG_IMX21_IMX27_UART
		bool "i.MX21 and i.MX27 Debug UART"
		depends on SOC_IMX21 || SOC_IMX27
		help
		  Say Y here if you want kernel low-level debugging support
		  on i.MX21 or i.MX27.

	config DEBUG_IMX28_UART
		bool "i.MX28 Debug UART"
		depends on SOC_IMX28
		help
		  Say Y here if you want kernel low-level debugging support
		  on i.MX28.

	config DEBUG_IMX31_IMX35_UART
		bool "i.MX31 and i.MX35 Debug UART"
		depends on SOC_IMX31 || SOC_IMX35
		help
		  Say Y here if you want kernel low-level debugging support
		  on i.MX31 or i.MX35.

	config DEBUG_IMX51_UART
		bool "i.MX51 Debug UART"
		depends on SOC_IMX51
		help
		  Say Y here if you want kernel low-level debugging support
		  on i.MX51.

	config DEBUG_IMX50_IMX53_UART
		bool "i.MX50 and i.MX53 Debug UART"
		depends on SOC_IMX50 || SOC_IMX53
		help
		  Say Y here if you want kernel low-level debugging support
		  on i.MX50 or i.MX53.

	config DEBUG_IMX6Q_UART2
		bool "i.MX6Q Debug UART2"
		depends on SOC_IMX6Q
		help
		  Say Y here if you want kernel low-level debugging support
		  on i.MX6Q UART2. This is correct for e.g. the SabreLite
                  board.

	config DEBUG_IMX6Q_UART4
		bool "i.MX6Q Debug UART4"
		depends on SOC_IMX6Q
		help
		  Say Y here if you want kernel low-level debugging support
		  on i.MX6Q UART4.

	config DEBUG_MMP_UART2
		bool "Kernel low-level debugging message via MMP UART2"
		depends on ARCH_MMP
		help
		  Say Y here if you want kernel low-level debugging support
		  on MMP UART2.

	config DEBUG_MMP_UART3
		bool "Kernel low-level debugging message via MMP UART3"
		depends on ARCH_MMP
		help
		  Say Y here if you want kernel low-level debugging support
		  on MMP UART3.

	config DEBUG_MSM_UART1
		bool "Kernel low-level debugging messages via MSM UART1"
		depends on ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50
		help
		  Say Y here if you want the debug print routines to direct
		  their output to the first serial port on MSM devices.

	config DEBUG_MSM_UART2
		bool "Kernel low-level debugging messages via MSM UART2"
		depends on ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50
		help
		  Say Y here if you want the debug print routines to direct
		  their output to the second serial port on MSM devices.

	config DEBUG_MSM_UART3
		bool "Kernel low-level debugging messages via MSM UART3"
		depends on ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50
		help
		  Say Y here if you want the debug print routines to direct
		  their output to the third serial port on MSM devices.

	config DEBUG_MSM8660_UART
		bool "Kernel low-level debugging messages via MSM 8660 UART"
		depends on ARCH_MSM8X60
		select MSM_HAS_DEBUG_UART_HS
		help
		  Say Y here if you want the debug print routines to direct
		  their output to the serial port on MSM 8660 devices.

	config DEBUG_MSM8960_UART
		bool "Kernel low-level debugging messages via MSM 8960 UART"
		depends on ARCH_MSM8960
		select MSM_HAS_DEBUG_UART_HS
		help
		  Say Y here if you want the debug print routines to direct
		  their output to the serial port on MSM 8960 devices.

	config DEBUG_MVEBU_UART
		bool "Kernel low-level debugging messages via MVEBU UART"
		depends on ARCH_MVEBU
		help
		  Say Y here if you want kernel low-level debugging support
		  on MVEBU based platforms.

	config DEBUG_PICOXCELL_UART
		depends on ARCH_PICOXCELL
		bool "Use PicoXcell UART for low-level debug"
		help
		  Say Y here if you want kernel low-level debugging support
		  on PicoXcell based platforms.

	config DEBUG_REALVIEW_STD_PORT
		bool "RealView Default UART"
		depends on ARCH_REALVIEW
		help
		  Say Y here if you want the debug print routines to direct
		  their output to the serial port on RealView EB, PB11MP, PBA8
		  and PBX platforms.

	config DEBUG_REALVIEW_PB1176_PORT
		bool "RealView PB1176 UART"
		depends on MACH_REALVIEW_PB1176
		help
		  Say Y here if you want the debug print routines to direct
		  their output to the standard serial port on the RealView
		  PB1176 platform.

	config DEBUG_S3C_UART0
		depends on PLAT_SAMSUNG
		bool "Use S3C UART 0 for low-level debug"
		help
		  Say Y here if you want the debug print routines to direct
		  their output to UART 0. The port must have been initialised
		  by the boot-loader before use.

		  The uncompressor code port configuration is now handled
		  by CONFIG_S3C_LOWLEVEL_UART_PORT.

	config DEBUG_S3C_UART1
		depends on PLAT_SAMSUNG
		bool "Use S3C UART 1 for low-level debug"
		help
		  Say Y here if you want the debug print routines to direct
		  their output to UART 1. The port must have been initialised
		  by the boot-loader before use.

		  The uncompressor code port configuration is now handled
		  by CONFIG_S3C_LOWLEVEL_UART_PORT.

	config DEBUG_S3C_UART2
		depends on PLAT_SAMSUNG
		bool "Use S3C UART 2 for low-level debug"
		help
		  Say Y here if you want the debug print routines to direct
		  their output to UART 2. The port must have been initialised
		  by the boot-loader before use.

		  The uncompressor code port configuration is now handled
		  by CONFIG_S3C_LOWLEVEL_UART_PORT.

	config DEBUG_SOCFPGA_UART
		depends on ARCH_SOCFPGA
		bool "Use SOCFPGA UART for low-level debug"
		help
		  Say Y here if you want kernel low-level debugging support
		  on SOCFPGA based platforms.

	config DEBUG_VEXPRESS_UART0_DETECT
		bool "Autodetect UART0 on Versatile Express Cortex-A core tiles"
		depends on ARCH_VEXPRESS && CPU_CP15_MMU
		help
		  This option enables a simple heuristic which tries to determine
		  the motherboard's memory map variant (original or RS1) and then
		  choose the relevant UART0 base address.

		  Note that this will only work with standard A-class core tiles,
		  and may fail with non-standard SMM or custom software models.

	config DEBUG_VEXPRESS_UART0_CA9
		bool "Use PL011 UART0 at 0x10009000 (V2P-CA9 core tile)"
		depends on ARCH_VEXPRESS
		help
		  This option selects UART0 at 0x10009000. Except for custom models,
		  this applies only to the V2P-CA9 tile.

	config DEBUG_VEXPRESS_UART0_RS1
		bool "Use PL011 UART0 at 0x1c090000 (RS1 complaint tiles)"
		depends on ARCH_VEXPRESS
		help
		  This option selects UART0 at 0x1c090000. This applies to most
		  of the tiles using the RS1 memory map, including all new A-class
		  core tiles, FPGA-based SMMs and software models.

	config DEBUG_LL_UART_NONE
		bool "No low-level debugging UART"
		depends on !ARCH_MULTIPLATFORM
		help
		  Say Y here if your platform doesn't provide a UART option
		  below. This relies on your platform choosing the right UART
		  definition internally in order for low-level debugging to
		  work.

	config DEBUG_ICEDCC
		bool "Kernel low-level debugging via EmbeddedICE DCC channel"
		help
		  Say Y here if you want the debug print routines to direct
		  their output to the EmbeddedICE macrocell's DCC channel using
		  co-processor 14. This is known to work on the ARM9 style ICE
		  channel and on the XScale with the PEEDI.

		  Note that the system will appear to hang during boot if there
		  is nothing connected to read from the DCC.

	config DEBUG_SEMIHOSTING
		bool "Kernel low-level debug output via semihosting I/O"
		help
		  Semihosting enables code running on an ARM target to use
		  the I/O facilities on a host debugger/emulator through a
		  simple SVC call. The host debugger or emulator must have
		  semihosting enabled for the special svc call to be trapped
		  otherwise the kernel will crash.

		  This is known to work with OpenOCD, as well as
		  ARM's Fast Models, or any other controlling environment
		  that implements semihosting.

		  For more details about semihosting, please see
		  chapter 8 of DUI0203I_rvct_developer_guide.pdf from ARM Ltd.

endchoice

config DEBUG_LL_INCLUDE
	string
	default "debug/icedcc.S" if DEBUG_ICEDCC
	default "debug/highbank.S" if DEBUG_HIGHBANK_UART
	default "debug/mvebu.S" if DEBUG_MVEBU_UART
	default "debug/picoxcell.S" if DEBUG_PICOXCELL_UART
	default "debug/socfpga.S" if DEBUG_SOCFPGA_UART
	default "debug/vexpress.S" if DEBUG_VEXPRESS_UART0_DETECT || \
		DEBUG_VEXPRESS_UART0_CA9 || DEBUG_VEXPRESS_UART0_RS1
	default "mach/debug-macro.S"

config EARLY_PRINTK
	bool "Early printk"
	depends on DEBUG_LL
	help
	  Say Y here if you want to have an early console using the
	  kernel low-level debugging functions. Add earlyprintk to your
	  kernel parameters to enable this console.

config OC_ETM
	bool "On-chip ETM and ETB"
	depends on ARM_AMBA
	help
	  Enables the on-chip embedded trace macrocell and embedded trace
	  buffer driver that will allow you to collect traces of the
	  kernel code.

config ARM_KPROBES_TEST
	tristate "Kprobes test module"
	depends on KPROBES && MODULES
	help
	  Perform tests of kprobes API and instruction set simulation.

config PID_IN_CONTEXTIDR
	bool "Write the current PID to the CONTEXTIDR register"
	depends on CPU_COPY_V6
	help
	  Enabling this option causes the kernel to write the current PID to
	  the PROCID field of the CONTEXTIDR register, at the expense of some
	  additional instructions during context switch. Say Y here only if you
	  are planning to use hardware trace tools with this kernel.

endmenu
Commit	Line	Data
1da177e4 LT	1	menu "Kernel hacking"
	2
	3	source "lib/Kconfig.debug"
	4
087aaffc NP	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
adf8b37b	19	# RMK wants arm kernels compiled with frame pointers or stack unwinding.
1da177e4 LT	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
16c79651	25	depends on !THUMB2_KERNEL
0e341af8	26	default y if !ARM_UNWIND \|\| FUNCTION_GRAPH_TRACER
1da177e4 LT	27	help
1da177e4 LT	28	If you say N here, the resulting kernel will be slightly smaller and
adf8b37b CM	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
4a50bfe3	34	bool "Enable stack unwinding support (EXPERIMENTAL)"
adf8b37b CM	35	depends on AEABI && EXPERIMENTAL
	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.
1da177e4	43
09bfafac RV	44	config OLD_MCOUNT
	45	bool
	46	depends on FUNCTION_TRACER && FRAME_POINTER
	47	default y
	48
1da177e4 LT	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
1da177e4 LT	66	# These options are only for real kernel hackers who want to get their hands dirty.
1da177e4 LT	67	config DEBUG_LL
4f5ef922	68	bool "Kernel low-level debugging functions (read help!)"
1da177e4 LT	69	depends on DEBUG_KERNEL
1da177e4 LT	70	help
35efb606	71	Say Y here to include definitions of printascii, printch, printhex
1da177e4 LT	72	in the kernel. This is helpful if you are debugging code that
	73	executes before the console is initialized.
	74
4f5ef922 WD	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
17916b28 WD	80	choice
	81	prompt "Kernel low-level debugging port"
	82	depends on DEBUG_LL
	83
13079a73 JCPV	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
9918ceaf	89	bool "Kernel low-level debugging on 9263 and 9g45"
13079a73 JCPV	90	depends on HAVE_AT91_DBGU1
13079a73 JCPV	91
164acf96 SB	92	config DEBUG_CLPS711X_UART1
	93	bool "Kernel low-level debugging messages via UART1"
	94	depends on ARCH_CLPS711X
	95	help
	96	Say Y here if you want the debug print routines to direct
	97	their output to the first serial port on these devices.
17916b28 WD	98
	99	config DEBUG_CLPS711X_UART2
	100	bool "Kernel low-level debugging messages via UART2"
	101	depends on ARCH_CLPS711X
	102	help
	103	Say Y here if you want the debug print routines to direct
	104	their output to the second serial port on these devices.
17916b28	105
477099f1 UKK	106	config DEBUG_DAVINCI_DA8XX_UART1
	107	bool "Kernel low-level debugging on DaVinci DA8XX using UART1"
	108	depends on ARCH_DAVINCI_DA8XX
	109	help
	110	Say Y here if you want the debug print routines to direct
	111	their output to UART1 serial port on DaVinci DA8XX devices.
	112
	113	config DEBUG_DAVINCI_DA8XX_UART2
	114	bool "Kernel low-level debugging on DaVinci DA8XX using UART2"
	115	depends on ARCH_DAVINCI_DA8XX
	116	help
	117	Say Y here if you want the debug print routines to direct
	118	their output to UART2 serial port on DaVinci DA8XX devices.
	119
	120	config DEBUG_DAVINCI_DMx_UART0
	121	bool "Kernel low-level debugging on DaVinci DMx using UART0"
	122	depends on ARCH_DAVINCI_DMx
	123	help
	124	Say Y here if you want the debug print routines to direct
	125	their output to UART0 serial port on DaVinci DMx devices.
	126
	127	config DEBUG_DAVINCI_TNETV107X_UART1
	128	bool "Kernel low-level debugging on DaVinci TNETV107x using UART1"
	129	depends on ARCH_DAVINCI_TNETV107X
	130	help
	131	Say Y here if you want the debug print routines to direct
	132	their output to UART1 serial port on DaVinci TNETV107X
	133	devices.
	134
aaf5e0be NB	135	config DEBUG_ZYNQ_UART0
	136	bool "Kernel low-level debugging on Xilinx Zynq using UART0"
	137	depends on ARCH_ZYNQ
	138	help
	139	Say Y here if you want the debug print routines to direct
	140	their output to UART0 on the Zynq platform.
	141
	142	config DEBUG_ZYNQ_UART1
	143	bool "Kernel low-level debugging on Xilinx Zynq using UART1"
	144	depends on ARCH_ZYNQ
	145	help
	146	Say Y here if you want the debug print routines to direct
	147	their output to UART1 on the Zynq platform.
	148
	149	If you have a ZC702 board and want early boot messages to
	150	appear on the USB serial adaptor, select this option.
	151
e76f4750 RK	152	config DEBUG_DC21285_PORT
	153	bool "Kernel low-level debugging messages via footbridge serial port"
	154	depends on FOOTBRIDGE
	155	help
	156	Say Y here if you want the debug print routines to direct
	157	their output to the serial port in the DC21285 (Footbridge).
	158
	159	config DEBUG_FOOTBRIDGE_COM1
	160	bool "Kernel low-level debugging messages via footbridge 8250 at PCI COM1"
	161	depends on FOOTBRIDGE
	162	help
	163	Say Y here if you want the debug print routines to direct
	164	their output to the 8250 at PCI COM1.
	165
220e6cf7 RH	166	config DEBUG_HIGHBANK_UART
	167	bool "Kernel low-level debugging messages via Highbank UART"
	168	depends on ARCH_HIGHBANK
	169	help
	170	Say Y here if you want the debug print routines to direct
	171	their output to the UART on Highbank based devices.
	172
f350b861 SG	173	config DEBUG_IMX1_UART
	174	bool "i.MX1 Debug UART"
	175	depends on SOC_IMX1
	176	help
	177	Say Y here if you want kernel low-level debugging support
	178	on i.MX1.
	179
	180	config DEBUG_IMX23_UART
	181	bool "i.MX23 Debug UART"
	182	depends on SOC_IMX23
	183	help
	184	Say Y here if you want kernel low-level debugging support
	185	on i.MX23.
	186
	187	config DEBUG_IMX25_UART
	188	bool "i.MX25 Debug UART"
	189	depends on SOC_IMX25
	190	help
	191	Say Y here if you want kernel low-level debugging support
	192	on i.MX25.
	193
	194	config DEBUG_IMX21_IMX27_UART
	195	bool "i.MX21 and i.MX27 Debug UART"
	196	depends on SOC_IMX21 \|\| SOC_IMX27
	197	help
	198	Say Y here if you want kernel low-level debugging support
	199	on i.MX21 or i.MX27.
	200
	201	config DEBUG_IMX28_UART
	202	bool "i.MX28 Debug UART"
	203	depends on SOC_IMX28
	204	help
	205	Say Y here if you want kernel low-level debugging support
	206	on i.MX28.
	207
	208	config DEBUG_IMX31_IMX35_UART
	209	bool "i.MX31 and i.MX35 Debug UART"
	210	depends on SOC_IMX31 \|\| SOC_IMX35
	211	help
	212	Say Y here if you want kernel low-level debugging support
	213	on i.MX31 or i.MX35.
	214
	215	config DEBUG_IMX51_UART
	216	bool "i.MX51 Debug UART"
	217	depends on SOC_IMX51
	218	help
	219	Say Y here if you want kernel low-level debugging support
	220	on i.MX51.
	221
	222	config DEBUG_IMX50_IMX53_UART
	223	bool "i.MX50 and i.MX53 Debug UART"
	224	depends on SOC_IMX50 \|\| SOC_IMX53
	225	help
	226	Say Y here if you want kernel low-level debugging support
	227	on i.MX50 or i.MX53.
	228
785d7fab DB	229	config DEBUG_IMX6Q_UART2
	230	bool "i.MX6Q Debug UART2"
	231	depends on SOC_IMX6Q
	232	help
	233	Say Y here if you want kernel low-level debugging support
	234	on i.MX6Q UART2. This is correct for e.g. the SabreLite
	235	board.
	236
cdaf29cf DB	237	config DEBUG_IMX6Q_UART4
cdaf29cf DB	238	bool "i.MX6Q Debug UART4"
bac89d75 SG	239	depends on SOC_IMX6Q
	240	help
	241	Say Y here if you want kernel low-level debugging support
cdaf29cf	242	on i.MX6Q UART4.
bac89d75	243
fa4cd2a8 HZ	244	config DEBUG_MMP_UART2
	245	bool "Kernel low-level debugging message via MMP UART2"
	246	depends on ARCH_MMP
	247	help
	248	Say Y here if you want kernel low-level debugging support
	249	on MMP UART2.
	250
	251	config DEBUG_MMP_UART3
	252	bool "Kernel low-level debugging message via MMP UART3"
	253	depends on ARCH_MMP
	254	help
	255	Say Y here if you want kernel low-level debugging support
	256	on MMP UART3.
	257
e76f4750 RK	258	config DEBUG_MSM_UART1
	259	bool "Kernel low-level debugging messages via MSM UART1"
	260	depends on ARCH_MSM7X00A \|\| ARCH_MSM7X30 \|\| ARCH_QSD8X50
952aeeb2 WD	261	help
952aeeb2 WD	262	Say Y here if you want the debug print routines to direct
e76f4750	263	their output to the first serial port on MSM devices.
952aeeb2	264
e76f4750 RK	265	config DEBUG_MSM_UART2
	266	bool "Kernel low-level debugging messages via MSM UART2"
	267	depends on ARCH_MSM7X00A \|\| ARCH_MSM7X30 \|\| ARCH_QSD8X50
952aeeb2 WD	268	help
952aeeb2 WD	269	Say Y here if you want the debug print routines to direct
e76f4750	270	their output to the second serial port on MSM devices.
952aeeb2	271
e76f4750 RK	272	config DEBUG_MSM_UART3
	273	bool "Kernel low-level debugging messages via MSM UART3"
	274	depends on ARCH_MSM7X00A \|\| ARCH_MSM7X30 \|\| ARCH_QSD8X50
	275	help
	276	Say Y here if you want the debug print routines to direct
	277	their output to the third serial port on MSM devices.
952aeeb2	278
e76f4750 RK	279	config DEBUG_MSM8660_UART
	280	bool "Kernel low-level debugging messages via MSM 8660 UART"
	281	depends on ARCH_MSM8X60
	282	select MSM_HAS_DEBUG_UART_HS
952aeeb2 WD	283	help
952aeeb2 WD	284	Say Y here if you want the debug print routines to direct
e76f4750	285	their output to the serial port on MSM 8660 devices.
952aeeb2	286
e76f4750 RK	287	config DEBUG_MSM8960_UART
	288	bool "Kernel low-level debugging messages via MSM 8960 UART"
	289	depends on ARCH_MSM8960
	290	select MSM_HAS_DEBUG_UART_HS
	291	help
	292	Say Y here if you want the debug print routines to direct
	293	their output to the serial port on MSM 8960 devices.
952aeeb2	294
bfd5af99 RH	295	config DEBUG_MVEBU_UART
	296	bool "Kernel low-level debugging messages via MVEBU UART"
	297	depends on ARCH_MVEBU
	298	help
	299	Say Y here if you want kernel low-level debugging support
	300	on MVEBU based platforms.
	301
59bba2a9 RH	302	config DEBUG_PICOXCELL_UART
	303	depends on ARCH_PICOXCELL
	304	bool "Use PicoXcell UART for low-level debug"
	305	help
	306	Say Y here if you want kernel low-level debugging support
	307	on PicoXcell based platforms.
	308
1285b8f8 WD	309	config DEBUG_REALVIEW_STD_PORT
	310	bool "RealView Default UART"
	311	depends on ARCH_REALVIEW
	312	help
	313	Say Y here if you want the debug print routines to direct
	314	their output to the serial port on RealView EB, PB11MP, PBA8
	315	and PBX platforms.
	316
	317	config DEBUG_REALVIEW_PB1176_PORT
	318	bool "RealView PB1176 UART"
	319	depends on MACH_REALVIEW_PB1176
	320	help
	321	Say Y here if you want the debug print routines to direct
	322	their output to the standard serial port on the RealView
	323	PB1176 platform.
	324
e76f4750 RK	325	config DEBUG_S3C_UART0
	326	depends on PLAT_SAMSUNG
	327	bool "Use S3C UART 0 for low-level debug"
650e3f0d SB	328	help
650e3f0d SB	329	Say Y here if you want the debug print routines to direct
e76f4750 RK	330	their output to UART 0. The port must have been initialised
e76f4750 RK	331	by the boot-loader before use.
650e3f0d	332
e76f4750 RK	333	The uncompressor code port configuration is now handled
	334	by CONFIG_S3C_LOWLEVEL_UART_PORT.
	335
	336	config DEBUG_S3C_UART1
	337	depends on PLAT_SAMSUNG
	338	bool "Use S3C UART 1 for low-level debug"
650e3f0d SB	339	help
650e3f0d SB	340	Say Y here if you want the debug print routines to direct
e76f4750 RK	341	their output to UART 1. The port must have been initialised
e76f4750 RK	342	by the boot-loader before use.
650e3f0d	343
e76f4750 RK	344	The uncompressor code port configuration is now handled
	345	by CONFIG_S3C_LOWLEVEL_UART_PORT.
	346
	347	config DEBUG_S3C_UART2
	348	depends on PLAT_SAMSUNG
	349	bool "Use S3C UART 2 for low-level debug"
650e3f0d SB	350	help
650e3f0d SB	351	Say Y here if you want the debug print routines to direct
e76f4750 RK	352	their output to UART 2. The port must have been initialised
e76f4750 RK	353	by the boot-loader before use.
650e3f0d	354
e76f4750 RK	355	The uncompressor code port configuration is now handled
	356	by CONFIG_S3C_LOWLEVEL_UART_PORT.
	357
6111bf7c RH	358	config DEBUG_SOCFPGA_UART
	359	depends on ARCH_SOCFPGA
	360	bool "Use SOCFPGA UART for low-level debug"
	361	help
	362	Say Y here if you want kernel low-level debugging support
	363	on SOCFPGA based platforms.
	364
1b820eaf PM	365	config DEBUG_VEXPRESS_UART0_DETECT
	366	bool "Autodetect UART0 on Versatile Express Cortex-A core tiles"
	367	depends on ARCH_VEXPRESS && CPU_CP15_MMU
	368	help
	369	This option enables a simple heuristic which tries to determine
	370	the motherboard's memory map variant (original or RS1) and then
	371	choose the relevant UART0 base address.
	372
	373	Note that this will only work with standard A-class core tiles,
	374	and may fail with non-standard SMM or custom software models.
	375
	376	config DEBUG_VEXPRESS_UART0_CA9
	377	bool "Use PL011 UART0 at 0x10009000 (V2P-CA9 core tile)"
	378	depends on ARCH_VEXPRESS
	379	help
	380	This option selects UART0 at 0x10009000. Except for custom models,
	381	this applies only to the V2P-CA9 tile.
	382
	383	config DEBUG_VEXPRESS_UART0_RS1
	384	bool "Use PL011 UART0 at 0x1c090000 (RS1 complaint tiles)"
	385	depends on ARCH_VEXPRESS
	386	help
	387	This option selects UART0 at 0x1c090000. This applies to most
	388	of the tiles using the RS1 memory map, including all new A-class
	389	core tiles, FPGA-based SMMs and software models.
	390
e76f4750 RK	391	config DEBUG_LL_UART_NONE
e76f4750 RK	392	bool "No low-level debugging UART"
387798b3	393	depends on !ARCH_MULTIPLATFORM
a3d3ef9d	394	help
e76f4750 RK	395	Say Y here if your platform doesn't provide a UART option
	396	below. This relies on your platform choosing the right UART
	397	definition internally in order for low-level debugging to
	398	work.
a3d3ef9d	399
e76f4750 RK	400	config DEBUG_ICEDCC
e76f4750 RK	401	bool "Kernel low-level debugging via EmbeddedICE DCC channel"
a3d3ef9d SB	402	help
a3d3ef9d SB	403	Say Y here if you want the debug print routines to direct
e76f4750 RK	404	their output to the EmbeddedICE macrocell's DCC channel using
	405	co-processor 14. This is known to work on the ARM9 style ICE
	406	channel and on the XScale with the PEEDI.
	407
	408	Note that the system will appear to hang during boot if there
	409	is nothing connected to read from the DCC.
a3d3ef9d	410
b0df8986	411	config DEBUG_SEMIHOSTING
62194bda	412	bool "Kernel low-level debug output via semihosting I/O"
650e3f0d	413	help
b0df8986 RK	414	Semihosting enables code running on an ARM target to use
b0df8986 RK	415	the I/O facilities on a host debugger/emulator through a
62194bda	416	simple SVC call. The host debugger or emulator must have
b0df8986 RK	417	semihosting enabled for the special svc call to be trapped
b0df8986 RK	418	otherwise the kernel will crash.
650e3f0d	419
62194bda	420	This is known to work with OpenOCD, as well as
b0df8986 RK	421	ARM's Fast Models, or any other controlling environment
b0df8986 RK	422	that implements semihosting.
a3d3ef9d	423
b0df8986 RK	424	For more details about semihosting, please see
b0df8986 RK	425	chapter 8 of DUI0203I_rvct_developer_guide.pdf from ARM Ltd.
a3d3ef9d	426
17916b28 WD	427	endchoice
17916b28 WD	428
91a9fec0 RH	429	config DEBUG_LL_INCLUDE
	430	string
	431	default "debug/icedcc.S" if DEBUG_ICEDCC
2e9bb084	432	default "debug/highbank.S" if DEBUG_HIGHBANK_UART
bfd5af99	433	default "debug/mvebu.S" if DEBUG_MVEBU_UART
59bba2a9	434	default "debug/picoxcell.S" if DEBUG_PICOXCELL_UART
6111bf7c	435	default "debug/socfpga.S" if DEBUG_SOCFPGA_UART
fa04e4db RH	436	default "debug/vexpress.S" if DEBUG_VEXPRESS_UART0_DETECT \|\| \
fa04e4db RH	437	DEBUG_VEXPRESS_UART0_CA9 \|\| DEBUG_VEXPRESS_UART0_RS1
91a9fec0 RH	438	default "mach/debug-macro.S"
91a9fec0 RH	439
93fd03a8 CM	440	config EARLY_PRINTK
	441	bool "Early printk"
	442	depends on DEBUG_LL
	443	help
	444	Say Y here if you want to have an early console using the
	445	kernel low-level debugging functions. Add earlyprintk to your
	446	kernel parameters to enable this console.
	447
c5d6c770 AS	448	config OC_ETM
c5d6c770 AS	449	bool "On-chip ETM and ETB"
53eebb0d	450	depends on ARM_AMBA
c5d6c770 AS	451	help
	452	Enables the on-chip embedded trace macrocell and embedded trace
	453	buffer driver that will allow you to collect traces of the
	454	kernel code.
	455
4189bc71 JM	456	config ARM_KPROBES_TEST
	457	tristate "Kprobes test module"
	458	depends on KPROBES && MODULES
	459	help
	460	Perform tests of kprobes API and instruction set simulation.
	461
575320d6 WD	462	config PID_IN_CONTEXTIDR
	463	bool "Write the current PID to the CONTEXTIDR register"
	464	depends on CPU_COPY_V6
	465	help
	466	Enabling this option causes the kernel to write the current PID to
	467	the PROCID field of the CONTEXTIDR register, at the expense of some
	468	additional instructions during context switch. Say Y here only if you
	469	are planning to use hardware trace tools with this kernel.
	470
1da177e4	471	endmenu