| 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_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. |
| 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. |
| 105 | |
| 106 | config DEBUG_CNS3XXX |
| 107 | bool "Kernel Kernel low-level debugging on Cavium Networks CNS3xxx" |
| 108 | depends on ARCH_CNS3XXX |
| 109 | help |
| 110 | Say Y here if you want the debug print routines to direct |
| 111 | their output to the CNS3xxx UART0. |
| 112 | |
| 113 | config DEBUG_DAVINCI_DA8XX_UART1 |
| 114 | bool "Kernel low-level debugging on DaVinci DA8XX using UART1" |
| 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 UART1 serial port on DaVinci DA8XX devices. |
| 119 | |
| 120 | config DEBUG_DAVINCI_DA8XX_UART2 |
| 121 | bool "Kernel low-level debugging on DaVinci DA8XX using UART2" |
| 122 | depends on ARCH_DAVINCI_DA8XX |
| 123 | help |
| 124 | Say Y here if you want the debug print routines to direct |
| 125 | their output to UART2 serial port on DaVinci DA8XX devices. |
| 126 | |
| 127 | config DEBUG_DAVINCI_DMx_UART0 |
| 128 | bool "Kernel low-level debugging on DaVinci DMx using UART0" |
| 129 | depends on ARCH_DAVINCI_DMx |
| 130 | help |
| 131 | Say Y here if you want the debug print routines to direct |
| 132 | their output to UART0 serial port on DaVinci DMx devices. |
| 133 | |
| 134 | config DEBUG_DAVINCI_TNETV107X_UART1 |
| 135 | bool "Kernel low-level debugging on DaVinci TNETV107x using UART1" |
| 136 | depends on ARCH_DAVINCI_TNETV107X |
| 137 | help |
| 138 | Say Y here if you want the debug print routines to direct |
| 139 | their output to UART1 serial port on DaVinci TNETV107X |
| 140 | devices. |
| 141 | |
| 142 | config DEBUG_ZYNQ_UART0 |
| 143 | bool "Kernel low-level debugging on Xilinx Zynq using UART0" |
| 144 | depends on ARCH_ZYNQ |
| 145 | help |
| 146 | Say Y here if you want the debug print routines to direct |
| 147 | their output to UART0 on the Zynq platform. |
| 148 | |
| 149 | config DEBUG_ZYNQ_UART1 |
| 150 | bool "Kernel low-level debugging on Xilinx Zynq using UART1" |
| 151 | depends on ARCH_ZYNQ |
| 152 | help |
| 153 | Say Y here if you want the debug print routines to direct |
| 154 | their output to UART1 on the Zynq platform. |
| 155 | |
| 156 | If you have a ZC702 board and want early boot messages to |
| 157 | appear on the USB serial adaptor, select this option. |
| 158 | |
| 159 | config DEBUG_DC21285_PORT |
| 160 | bool "Kernel low-level debugging messages via footbridge serial port" |
| 161 | depends on FOOTBRIDGE |
| 162 | help |
| 163 | Say Y here if you want the debug print routines to direct |
| 164 | their output to the serial port in the DC21285 (Footbridge). |
| 165 | |
| 166 | config DEBUG_FOOTBRIDGE_COM1 |
| 167 | bool "Kernel low-level debugging messages via footbridge 8250 at PCI COM1" |
| 168 | depends on FOOTBRIDGE |
| 169 | help |
| 170 | Say Y here if you want the debug print routines to direct |
| 171 | their output to the 8250 at PCI COM1. |
| 172 | |
| 173 | config DEBUG_HIGHBANK_UART |
| 174 | bool "Kernel low-level debugging messages via Highbank UART" |
| 175 | depends on ARCH_HIGHBANK |
| 176 | help |
| 177 | Say Y here if you want the debug print routines to direct |
| 178 | their output to the UART on Highbank based devices. |
| 179 | |
| 180 | config DEBUG_IMX1_UART |
| 181 | bool "i.MX1 Debug UART" |
| 182 | depends on SOC_IMX1 |
| 183 | help |
| 184 | Say Y here if you want kernel low-level debugging support |
| 185 | on i.MX1. |
| 186 | |
| 187 | config DEBUG_IMX23_UART |
| 188 | bool "i.MX23 Debug UART" |
| 189 | depends on SOC_IMX23 |
| 190 | help |
| 191 | Say Y here if you want kernel low-level debugging support |
| 192 | on i.MX23. |
| 193 | |
| 194 | config DEBUG_IMX25_UART |
| 195 | bool "i.MX25 Debug UART" |
| 196 | depends on SOC_IMX25 |
| 197 | help |
| 198 | Say Y here if you want kernel low-level debugging support |
| 199 | on i.MX25. |
| 200 | |
| 201 | config DEBUG_IMX21_IMX27_UART |
| 202 | bool "i.MX21 and i.MX27 Debug UART" |
| 203 | depends on SOC_IMX21 || SOC_IMX27 |
| 204 | help |
| 205 | Say Y here if you want kernel low-level debugging support |
| 206 | on i.MX21 or i.MX27. |
| 207 | |
| 208 | config DEBUG_IMX28_UART |
| 209 | bool "i.MX28 Debug UART" |
| 210 | depends on SOC_IMX28 |
| 211 | help |
| 212 | Say Y here if you want kernel low-level debugging support |
| 213 | on i.MX28. |
| 214 | |
| 215 | config DEBUG_IMX31_UART |
| 216 | bool "i.MX31 Debug UART" |
| 217 | depends on SOC_IMX31 |
| 218 | help |
| 219 | Say Y here if you want kernel low-level debugging support |
| 220 | on i.MX31. |
| 221 | |
| 222 | config DEBUG_IMX35_UART |
| 223 | bool "i.MX35 Debug UART" |
| 224 | depends on SOC_IMX35 |
| 225 | help |
| 226 | Say Y here if you want kernel low-level debugging support |
| 227 | on i.MX35. |
| 228 | |
| 229 | config DEBUG_IMX51_UART |
| 230 | bool "i.MX51 Debug UART" |
| 231 | depends on SOC_IMX51 |
| 232 | help |
| 233 | Say Y here if you want kernel low-level debugging support |
| 234 | on i.MX51. |
| 235 | |
| 236 | config DEBUG_IMX53_UART |
| 237 | bool "i.MX53 Debug UART" |
| 238 | depends on SOC_IMX53 |
| 239 | help |
| 240 | Say Y here if you want kernel low-level debugging support |
| 241 | on i.MX53. |
| 242 | |
| 243 | config DEBUG_IMX6Q_UART |
| 244 | bool "i.MX6Q Debug UART" |
| 245 | depends on SOC_IMX6Q |
| 246 | help |
| 247 | Say Y here if you want kernel low-level debugging support |
| 248 | on i.MX6Q. |
| 249 | |
| 250 | config DEBUG_MMP_UART2 |
| 251 | bool "Kernel low-level debugging message via MMP UART2" |
| 252 | depends on ARCH_MMP |
| 253 | help |
| 254 | Say Y here if you want kernel low-level debugging support |
| 255 | on MMP UART2. |
| 256 | |
| 257 | config DEBUG_MMP_UART3 |
| 258 | bool "Kernel low-level debugging message via MMP UART3" |
| 259 | depends on ARCH_MMP |
| 260 | help |
| 261 | Say Y here if you want kernel low-level debugging support |
| 262 | on MMP UART3. |
| 263 | |
| 264 | config DEBUG_MSM_UART1 |
| 265 | bool "Kernel low-level debugging messages via MSM UART1" |
| 266 | depends on ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50 |
| 267 | help |
| 268 | Say Y here if you want the debug print routines to direct |
| 269 | their output to the first serial port on MSM devices. |
| 270 | |
| 271 | config DEBUG_MSM_UART2 |
| 272 | bool "Kernel low-level debugging messages via MSM UART2" |
| 273 | depends on ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50 |
| 274 | help |
| 275 | Say Y here if you want the debug print routines to direct |
| 276 | their output to the second serial port on MSM devices. |
| 277 | |
| 278 | config DEBUG_MSM_UART3 |
| 279 | bool "Kernel low-level debugging messages via MSM UART3" |
| 280 | depends on ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50 |
| 281 | help |
| 282 | Say Y here if you want the debug print routines to direct |
| 283 | their output to the third serial port on MSM devices. |
| 284 | |
| 285 | config DEBUG_MSM8660_UART |
| 286 | bool "Kernel low-level debugging messages via MSM 8660 UART" |
| 287 | depends on ARCH_MSM8X60 |
| 288 | select MSM_HAS_DEBUG_UART_HS |
| 289 | help |
| 290 | Say Y here if you want the debug print routines to direct |
| 291 | their output to the serial port on MSM 8660 devices. |
| 292 | |
| 293 | config DEBUG_MSM8960_UART |
| 294 | bool "Kernel low-level debugging messages via MSM 8960 UART" |
| 295 | depends on ARCH_MSM8960 |
| 296 | select MSM_HAS_DEBUG_UART_HS |
| 297 | help |
| 298 | Say Y here if you want the debug print routines to direct |
| 299 | their output to the serial port on MSM 8960 devices. |
| 300 | |
| 301 | config DEBUG_MVEBU_UART |
| 302 | bool "Kernel low-level debugging messages via MVEBU UART" |
| 303 | depends on ARCH_MVEBU |
| 304 | help |
| 305 | Say Y here if you want kernel low-level debugging support |
| 306 | on MVEBU based platforms. |
| 307 | |
| 308 | config DEBUG_NOMADIK_UART |
| 309 | bool "Kernel low-level debugging messages via NOMADIK UART" |
| 310 | depends on ARCH_NOMADIK |
| 311 | help |
| 312 | Say Y here if you want kernel low-level debugging support |
| 313 | on NOMADIK based platforms. |
| 314 | |
| 315 | config DEBUG_OMAP2PLUS_UART |
| 316 | bool "Kernel low-level debugging messages via OMAP2PLUS UART" |
| 317 | depends on ARCH_OMAP2PLUS |
| 318 | help |
| 319 | Say Y here if you want kernel low-level debugging support |
| 320 | on OMAP2PLUS based platforms. |
| 321 | |
| 322 | config DEBUG_PICOXCELL_UART |
| 323 | depends on ARCH_PICOXCELL |
| 324 | bool "Use PicoXcell UART for low-level debug" |
| 325 | help |
| 326 | Say Y here if you want kernel low-level debugging support |
| 327 | on PicoXcell based platforms. |
| 328 | |
| 329 | config DEBUG_REALVIEW_STD_PORT |
| 330 | bool "RealView Default UART" |
| 331 | depends on ARCH_REALVIEW |
| 332 | help |
| 333 | Say Y here if you want the debug print routines to direct |
| 334 | their output to the serial port on RealView EB, PB11MP, PBA8 |
| 335 | and PBX platforms. |
| 336 | |
| 337 | config DEBUG_REALVIEW_PB1176_PORT |
| 338 | bool "RealView PB1176 UART" |
| 339 | depends on MACH_REALVIEW_PB1176 |
| 340 | help |
| 341 | Say Y here if you want the debug print routines to direct |
| 342 | their output to the standard serial port on the RealView |
| 343 | PB1176 platform. |
| 344 | |
| 345 | config DEBUG_S3C_UART0 |
| 346 | depends on PLAT_SAMSUNG |
| 347 | bool "Use S3C UART 0 for low-level debug" |
| 348 | help |
| 349 | Say Y here if you want the debug print routines to direct |
| 350 | their output to UART 0. The port must have been initialised |
| 351 | by the boot-loader before use. |
| 352 | |
| 353 | The uncompressor code port configuration is now handled |
| 354 | by CONFIG_S3C_LOWLEVEL_UART_PORT. |
| 355 | |
| 356 | config DEBUG_S3C_UART1 |
| 357 | depends on PLAT_SAMSUNG |
| 358 | bool "Use S3C UART 1 for low-level debug" |
| 359 | help |
| 360 | Say Y here if you want the debug print routines to direct |
| 361 | their output to UART 1. The port must have been initialised |
| 362 | by the boot-loader before use. |
| 363 | |
| 364 | The uncompressor code port configuration is now handled |
| 365 | by CONFIG_S3C_LOWLEVEL_UART_PORT. |
| 366 | |
| 367 | config DEBUG_S3C_UART2 |
| 368 | depends on PLAT_SAMSUNG |
| 369 | bool "Use S3C UART 2 for low-level debug" |
| 370 | help |
| 371 | Say Y here if you want the debug print routines to direct |
| 372 | their output to UART 2. The port must have been initialised |
| 373 | by the boot-loader before use. |
| 374 | |
| 375 | The uncompressor code port configuration is now handled |
| 376 | by CONFIG_S3C_LOWLEVEL_UART_PORT. |
| 377 | |
| 378 | config DEBUG_S3C_UART3 |
| 379 | depends on PLAT_SAMSUNG && ARCH_EXYNOS |
| 380 | bool "Use S3C UART 3 for low-level debug" |
| 381 | help |
| 382 | Say Y here if you want the debug print routines to direct |
| 383 | their output to UART 3. The port must have been initialised |
| 384 | by the boot-loader before use. |
| 385 | |
| 386 | The uncompressor code port configuration is now handled |
| 387 | by CONFIG_S3C_LOWLEVEL_UART_PORT. |
| 388 | |
| 389 | config DEBUG_SOCFPGA_UART |
| 390 | depends on ARCH_SOCFPGA |
| 391 | bool "Use SOCFPGA UART for low-level debug" |
| 392 | help |
| 393 | Say Y here if you want kernel low-level debugging support |
| 394 | on SOCFPGA based platforms. |
| 395 | |
| 396 | config DEBUG_SUNXI_UART0 |
| 397 | bool "Kernel low-level debugging messages via sunXi UART0" |
| 398 | depends on ARCH_SUNXI |
| 399 | help |
| 400 | Say Y here if you want kernel low-level debugging support |
| 401 | on Allwinner A1X based platforms on the UART0. |
| 402 | |
| 403 | config DEBUG_SUNXI_UART1 |
| 404 | bool "Kernel low-level debugging messages via sunXi UART1" |
| 405 | depends on ARCH_SUNXI |
| 406 | help |
| 407 | Say Y here if you want kernel low-level debugging support |
| 408 | on Allwinner A1X based platforms on the UART1. |
| 409 | |
| 410 | config DEBUG_TEGRA_UART |
| 411 | depends on ARCH_TEGRA |
| 412 | bool "Use Tegra UART for low-level debug" |
| 413 | help |
| 414 | Say Y here if you want kernel low-level debugging support |
| 415 | on Tegra based platforms. |
| 416 | |
| 417 | config DEBUG_SIRFPRIMA2_UART1 |
| 418 | bool "Kernel low-level debugging messages via SiRFprimaII UART1" |
| 419 | depends on ARCH_PRIMA2 |
| 420 | help |
| 421 | Say Y here if you want the debug print routines to direct |
| 422 | their output to the uart1 port on SiRFprimaII devices. |
| 423 | |
| 424 | config DEBUG_SIRFMARCO_UART1 |
| 425 | bool "Kernel low-level debugging messages via SiRFmarco UART1" |
| 426 | depends on ARCH_MARCO |
| 427 | help |
| 428 | Say Y here if you want the debug print routines to direct |
| 429 | their output to the uart1 port on SiRFmarco devices. |
| 430 | |
| 431 | config DEBUG_VEXPRESS_UART0_DETECT |
| 432 | bool "Autodetect UART0 on Versatile Express Cortex-A core tiles" |
| 433 | depends on ARCH_VEXPRESS && CPU_CP15_MMU |
| 434 | help |
| 435 | This option enables a simple heuristic which tries to determine |
| 436 | the motherboard's memory map variant (original or RS1) and then |
| 437 | choose the relevant UART0 base address. |
| 438 | |
| 439 | Note that this will only work with standard A-class core tiles, |
| 440 | and may fail with non-standard SMM or custom software models. |
| 441 | |
| 442 | config DEBUG_VEXPRESS_UART0_CA9 |
| 443 | bool "Use PL011 UART0 at 0x10009000 (V2P-CA9 core tile)" |
| 444 | depends on ARCH_VEXPRESS |
| 445 | help |
| 446 | This option selects UART0 at 0x10009000. Except for custom models, |
| 447 | this applies only to the V2P-CA9 tile. |
| 448 | |
| 449 | config DEBUG_VEXPRESS_UART0_RS1 |
| 450 | bool "Use PL011 UART0 at 0x1c090000 (RS1 complaint tiles)" |
| 451 | depends on ARCH_VEXPRESS |
| 452 | help |
| 453 | This option selects UART0 at 0x1c090000. This applies to most |
| 454 | of the tiles using the RS1 memory map, including all new A-class |
| 455 | core tiles, FPGA-based SMMs and software models. |
| 456 | |
| 457 | config DEBUG_VT8500_UART0 |
| 458 | bool "Use UART0 on VIA/Wondermedia SoCs" |
| 459 | depends on ARCH_VT8500 |
| 460 | help |
| 461 | This option selects UART0 on VIA/Wondermedia System-on-a-chip |
| 462 | devices, including VT8500, WM8505, WM8650 and WM8850. |
| 463 | |
| 464 | config DEBUG_LL_UART_NONE |
| 465 | bool "No low-level debugging UART" |
| 466 | depends on !ARCH_MULTIPLATFORM |
| 467 | help |
| 468 | Say Y here if your platform doesn't provide a UART option |
| 469 | below. This relies on your platform choosing the right UART |
| 470 | definition internally in order for low-level debugging to |
| 471 | work. |
| 472 | |
| 473 | config DEBUG_ICEDCC |
| 474 | bool "Kernel low-level debugging via EmbeddedICE DCC channel" |
| 475 | help |
| 476 | Say Y here if you want the debug print routines to direct |
| 477 | their output to the EmbeddedICE macrocell's DCC channel using |
| 478 | co-processor 14. This is known to work on the ARM9 style ICE |
| 479 | channel and on the XScale with the PEEDI. |
| 480 | |
| 481 | Note that the system will appear to hang during boot if there |
| 482 | is nothing connected to read from the DCC. |
| 483 | |
| 484 | config DEBUG_SEMIHOSTING |
| 485 | bool "Kernel low-level debug output via semihosting I/O" |
| 486 | help |
| 487 | Semihosting enables code running on an ARM target to use |
| 488 | the I/O facilities on a host debugger/emulator through a |
| 489 | simple SVC call. The host debugger or emulator must have |
| 490 | semihosting enabled for the special svc call to be trapped |
| 491 | otherwise the kernel will crash. |
| 492 | |
| 493 | This is known to work with OpenOCD, as well as |
| 494 | ARM's Fast Models, or any other controlling environment |
| 495 | that implements semihosting. |
| 496 | |
| 497 | For more details about semihosting, please see |
| 498 | chapter 8 of DUI0203I_rvct_developer_guide.pdf from ARM Ltd. |
| 499 | |
| 500 | endchoice |
| 501 | |
| 502 | config DEBUG_IMX_UART_PORT |
| 503 | int "i.MX Debug UART Port Selection" if DEBUG_IMX1_UART || \ |
| 504 | DEBUG_IMX25_UART || \ |
| 505 | DEBUG_IMX21_IMX27_UART || \ |
| 506 | DEBUG_IMX31_UART || \ |
| 507 | DEBUG_IMX35_UART || \ |
| 508 | DEBUG_IMX51_UART || \ |
| 509 | DEBUG_IMX50_IMX53_UART || \ |
| 510 | DEBUG_IMX6Q_UART |
| 511 | default 1 |
| 512 | help |
| 513 | Choose UART port on which kernel low-level debug messages |
| 514 | should be output. |
| 515 | |
| 516 | choice |
| 517 | prompt "Low-level debug console UART" |
| 518 | depends on DEBUG_OMAP2PLUS_UART |
| 519 | |
| 520 | config DEBUG_OMAP2UART1 |
| 521 | bool "OMAP2/3/4 UART1 (omap2/3 sdp boards and some omap3 boards)" |
| 522 | help |
| 523 | This covers at least h4, 2430sdp, 3430sdp, 3630sdp, |
| 524 | omap3 torpedo and 3530 lv som. |
| 525 | |
| 526 | config DEBUG_OMAP2UART2 |
| 527 | bool "OMAP2/3/4 UART2" |
| 528 | |
| 529 | config DEBUG_OMAP2UART3 |
| 530 | bool "OMAP2 UART3 (n8x0)" |
| 531 | |
| 532 | config DEBUG_OMAP3UART3 |
| 533 | bool "OMAP3 UART3 (most omap3 boards)" |
| 534 | help |
| 535 | This covers at least cm_t3x, beagle, crane, devkit8000, |
| 536 | igep00x0, ldp, n900, n9(50), pandora, overo, touchbook, |
| 537 | and 3517evm. |
| 538 | |
| 539 | config DEBUG_OMAP4UART3 |
| 540 | bool "OMAP4/5 UART3 (omap4 blaze, panda, omap5 sevm)" |
| 541 | |
| 542 | config DEBUG_OMAP3UART4 |
| 543 | bool "OMAP36XX UART4" |
| 544 | |
| 545 | config DEBUG_OMAP4UART4 |
| 546 | bool "OMAP4/5 UART4" |
| 547 | |
| 548 | config DEBUG_TI81XXUART1 |
| 549 | bool "TI81XX UART1 (ti8148evm)" |
| 550 | |
| 551 | config DEBUG_TI81XXUART2 |
| 552 | bool "TI81XX UART2" |
| 553 | |
| 554 | config DEBUG_TI81XXUART3 |
| 555 | bool "TI81XX UART3 (ti8168evm)" |
| 556 | |
| 557 | config DEBUG_AM33XXUART1 |
| 558 | bool "AM33XX UART1" |
| 559 | |
| 560 | config DEBUG_ZOOM_UART |
| 561 | bool "Zoom2/3 UART" |
| 562 | endchoice |
| 563 | |
| 564 | choice |
| 565 | prompt "Low-level debug console UART" |
| 566 | depends on DEBUG_LL && DEBUG_TEGRA_UART |
| 567 | |
| 568 | config TEGRA_DEBUG_UART_AUTO_ODMDATA |
| 569 | bool "Via ODMDATA" |
| 570 | help |
| 571 | Automatically determines which UART to use for low-level debug based |
| 572 | on the ODMDATA value. This value is part of the BCT, and is written |
| 573 | to the boot memory device using nvflash, or other flashing tool. |
| 574 | When bits 19:18 are 3, then bits 17:15 indicate which UART to use; |
| 575 | 0/1/2/3/4 are UART A/B/C/D/E. |
| 576 | |
| 577 | config TEGRA_DEBUG_UARTA |
| 578 | bool "UART A" |
| 579 | |
| 580 | config TEGRA_DEBUG_UARTB |
| 581 | bool "UART B" |
| 582 | |
| 583 | config TEGRA_DEBUG_UARTC |
| 584 | bool "UART C" |
| 585 | |
| 586 | config TEGRA_DEBUG_UARTD |
| 587 | bool "UART D" |
| 588 | |
| 589 | config TEGRA_DEBUG_UARTE |
| 590 | bool "UART E" |
| 591 | |
| 592 | endchoice |
| 593 | |
| 594 | config DEBUG_LL_INCLUDE |
| 595 | string |
| 596 | default "debug/cns3xxx.S" if DEBUG_CNS3XXX |
| 597 | default "debug/icedcc.S" if DEBUG_ICEDCC |
| 598 | default "debug/imx.S" if DEBUG_IMX1_UART || \ |
| 599 | DEBUG_IMX25_UART || \ |
| 600 | DEBUG_IMX21_IMX27_UART || \ |
| 601 | DEBUG_IMX31_UART || \ |
| 602 | DEBUG_IMX35_UART || \ |
| 603 | DEBUG_IMX51_UART || \ |
| 604 | DEBUG_IMX53_UART ||\ |
| 605 | DEBUG_IMX6Q_UART |
| 606 | default "debug/highbank.S" if DEBUG_HIGHBANK_UART |
| 607 | default "debug/mvebu.S" if DEBUG_MVEBU_UART |
| 608 | default "debug/nomadik.S" if DEBUG_NOMADIK_UART |
| 609 | default "debug/omap2plus.S" if DEBUG_OMAP2PLUS_UART |
| 610 | default "debug/picoxcell.S" if DEBUG_PICOXCELL_UART |
| 611 | default "debug/socfpga.S" if DEBUG_SOCFPGA_UART |
| 612 | default "debug/sunxi.S" if DEBUG_SUNXI_UART0 || DEBUG_SUNXI_UART1 |
| 613 | default "debug/vexpress.S" if DEBUG_VEXPRESS_UART0_DETECT || \ |
| 614 | DEBUG_VEXPRESS_UART0_CA9 || DEBUG_VEXPRESS_UART0_RS1 |
| 615 | default "debug/vt8500.S" if DEBUG_VT8500_UART0 |
| 616 | default "debug/tegra.S" if DEBUG_TEGRA_UART |
| 617 | default "debug/zynq.S" if DEBUG_ZYNQ_UART0 || DEBUG_ZYNQ_UART1 |
| 618 | default "mach/debug-macro.S" |
| 619 | |
| 620 | config EARLY_PRINTK |
| 621 | bool "Early printk" |
| 622 | depends on DEBUG_LL |
| 623 | help |
| 624 | Say Y here if you want to have an early console using the |
| 625 | kernel low-level debugging functions. Add earlyprintk to your |
| 626 | kernel parameters to enable this console. |
| 627 | |
| 628 | config OC_ETM |
| 629 | bool "On-chip ETM and ETB" |
| 630 | depends on ARM_AMBA |
| 631 | help |
| 632 | Enables the on-chip embedded trace macrocell and embedded trace |
| 633 | buffer driver that will allow you to collect traces of the |
| 634 | kernel code. |
| 635 | |
| 636 | config ARM_KPROBES_TEST |
| 637 | tristate "Kprobes test module" |
| 638 | depends on KPROBES && MODULES |
| 639 | help |
| 640 | Perform tests of kprobes API and instruction set simulation. |
| 641 | |
| 642 | config PID_IN_CONTEXTIDR |
| 643 | bool "Write the current PID to the CONTEXTIDR register" |
| 644 | depends on CPU_COPY_V6 |
| 645 | help |
| 646 | Enabling this option causes the kernel to write the current PID to |
| 647 | the PROCID field of the CONTEXTIDR register, at the expense of some |
| 648 | additional instructions during context switch. Say Y here only if you |
| 649 | are planning to use hardware trace tools with this kernel. |
| 650 | |
| 651 | endmenu |