# SPDX-License-Identifier: GPL-2.0 config ARM_PTDUMP_CORE def_bool n config ARM_PTDUMP_DEBUGFS bool "Export kernel pagetable layout to userspace via debugfs" depends on DEBUG_KERNEL depends on MMU select ARM_PTDUMP_CORE select DEBUG_FS help Say Y here if you want to show the kernel pagetable layout in a debugfs file. This information is only useful for kernel developers who are working in architecture specific areas of the kernel. It is probably not a good idea to enable this feature in a production kernel. If in doubt, say "N" config ARM_DEBUG_WX bool "Warn on W+X mappings at boot" depends on MMU select ARM_PTDUMP_CORE help Generate a warning if any W+X mappings are found at boot. This is useful for discovering cases where the kernel is leaving W+X mappings after applying NX, as such mappings are a security risk. Look for a message in dmesg output like this: arm/mm: Checked W+X mappings: passed, no W+X pages found. or like this, if the check failed: arm/mm: Checked W+X mappings: FAILED, <N> W+X pages found. Note that even if the check fails, your kernel is possibly still fine, as W+X mappings are not a security hole in themselves, what they do is that they make the exploitation of other unfixed kernel bugs easier. There is no runtime or memory usage effect of this option once the kernel has booted up - it's a one time check. If in doubt, say "Y". choice prompt "Choose kernel unwinder" default UNWINDER_ARM if AEABI default UNWINDER_FRAME_POINTER if !AEABI help This determines which method will be used for unwinding kernel stack traces for panics, oopses, bugs, warnings, perf, /proc/<pid>/stack, livepatch, lockdep, and more. config UNWINDER_FRAME_POINTER bool "Frame pointer unwinder" depends on !THUMB2_KERNEL select ARCH_WANT_FRAME_POINTERS select FRAME_POINTER help This option enables the frame pointer unwinder for unwinding kernel stack traces. config UNWINDER_ARM bool "ARM EABI stack unwinder" depends on AEABI select ARM_UNWIND 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. endchoice config ARM_UNWIND bool config BACKTRACE_VERBOSE bool "Verbose backtrace" depends on EXPERT help When the kernel produces a warning or oops, the kernel prints a trace of the call chain. This option controls whether we include the numeric addresses or only include the symbolic information. In most cases, say N here, unless you are intending to debug the kernel and have access to the kernel binary image. 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 DEBUG_ALPINE_UART0 bool "Kernel low-level debugging messages via Alpine UART0" depends on ARCH_ALPINE select DEBUG_UART_8250 help Say Y here if you want kernel low-level debugging support on Alpine based platforms. config DEBUG_ASM9260_UART bool "Kernel low-level debugging via asm9260 UART" depends on MACH_ASM9260 help Say Y here if you want the debug print routines to direct their output to an UART or USART port on asm9260 based machines. DEBUG_UART_PHYS | DEBUG_UART_VIRT 0x80000000 | 0xf0000000 | UART0 0x80004000 | 0xf0004000 | UART1 0x80008000 | 0xf0008000 | UART2 0x8000c000 | 0xf000c000 | UART3 0x80010000 | 0xf0010000 | UART4 0x80014000 | 0xf0014000 | UART5 0x80018000 | 0xf0018000 | UART6 0x8001c000 | 0xf001c000 | UART7 0x80020000 | 0xf0020000 | UART8 0x80024000 | 0xf0024000 | UART9 config DEBUG_AT91_RM9200_DBGU bool "Kernel low-level debugging on AT91RM9200, AT91SAM9, SAM9X60 DBGU" select DEBUG_AT91_UART depends on SOC_AT91RM9200 || SOC_AT91SAM9 || SOC_SAM9X60 help Say Y here if you want kernel low-level debugging support on the DBGU port of: at91rm9200, at91sam9260, at91sam9g20, at91sam9261, at91sam9g10, at91sam9n12, at91sam9rl64, at91sam9x5, sam9x60 config DEBUG_AT91_SAM9263_DBGU bool "Kernel low-level debugging on AT91SAM{9263,9G45,A5D3} DBGU" select DEBUG_AT91_UART depends on SOC_AT91SAM9 || SOC_SAMA5D3 help Say Y here if you want kernel low-level debugging support on the DBGU port of: at91sam9263, at91sam9g45, at91sam9m10, sama5d3 config DEBUG_AT91_SAMA5D2_UART1 bool "Kernel low-level debugging on SAMA5D2 UART1" select DEBUG_AT91_UART depends on SOC_SAMA5D2 help Say Y here if you want kernel low-level debugging support on the UART1 port of sama5d2. config DEBUG_AT91_SAMA5D4_USART3 bool "Kernel low-level debugging on SAMA5D4 USART3" select DEBUG_AT91_UART depends on SOC_SAMA5D4 help Say Y here if you want kernel low-level debugging support on the USART3 port of sama5d4. config DEBUG_AT91_SAMV7_USART1 bool "Kernel low-level debugging via SAMV7 USART1" select DEBUG_AT91_UART depends on SOC_SAMV7 help Say Y here if you want the debug print routines to direct their output to the USART1 port on SAMV7 based machines. config DEBUG_AT91_SAMA7G5_FLEXCOM3 bool "Kernel low-level debugging on SAMA7G5 FLEXCOM3" select DEBUG_AT91_UART depends on SOC_SAMA7G5 help Say Y here if you want kernel low-level debugging support on the FLEXCOM3 port of SAMA7G5. config DEBUG_AT91_LAN966_FLEXCOM bool "Kernel low-level debugging on LAN966 FLEXCOM USART" select DEBUG_AT91_UART depends on SOC_LAN966 help Say Y here if you want kernel low-level debugging support on the FLEXCOM port of LAN966. DEBUG_UART_PHYS | DEBUG_UART_VIRT 0xe0040200 | 0xfd040200 | FLEXCOM0 0xe0044200 | 0xfd044200 | FLEXCOM1 0xe0060200 | 0xfd060200 | FLEXCOM2 0xe0064200 | 0xfd064200 | FLEXCOM3 0xe0070200 | 0xfd070200 | FLEXCOM4 By default, enabling FLEXCOM3 port. Based on requirement, use DEBUG_UART_PHYS and DEBUG_UART_VIRT configurations from above table. config DEBUG_BCM2835 bool "Kernel low-level debugging on BCM2835 PL011 UART" depends on ARCH_BCM2835 && ARCH_MULTI_V6 select DEBUG_UART_PL01X config DEBUG_BCM2836 bool "Kernel low-level debugging on BCM2836 PL011 UART" depends on ARCH_BCM2835 && ARCH_MULTI_V7 select DEBUG_UART_PL01X config DEBUG_BCM_5301X bool "Kernel low-level debugging on BCM5301X/NSP UART1" depends on ARCH_BCM_5301X || ARCH_BCM_NSP select DEBUG_UART_8250 config DEBUG_BCMBCA bool "Kernel low-level debugging on BCMBCA UART0" depends on ARCH_BCMBCA config DEBUG_BCM_HR2 bool "Kernel low-level debugging on Hurricane 2 UART2" depends on ARCH_BCM_HR2 select DEBUG_UART_8250 config DEBUG_BCM_IPROC_UART3 bool "Kernel low-level debugging on BCM IPROC UART3" depends on ARCH_BCM_CYGNUS select DEBUG_UART_8250 help Say Y here if you want the debug print routines to direct their output to the third serial port on these devices. config DEBUG_BCM_KONA_UART bool "Kernel low-level debugging messages via BCM KONA UART" depends on ARCH_BCM_MOBILE select DEBUG_UART_8250 help Say Y here if you want kernel low-level debugging support on Broadcom SoC platforms. This low level debug works for Broadcom mobile SoCs in the Kona family of chips (e.g. bcm28155, bcm11351, etc...) config DEBUG_BCM63XX_UART bool "Kernel low-level debugging on BCM63XX UART" depends on ARCH_BCMBCA config DEBUG_BERLIN_UART bool "Marvell Berlin SoC Debug UART" depends on ARCH_BERLIN select DEBUG_UART_8250 help Say Y here if you want kernel low-level debugging support on Marvell Berlin SoC based platforms. config DEBUG_BRCMSTB_UART bool "Use BRCMSTB UART for low-level debug" depends on ARCH_BRCMSTB help Say Y here if you want the debug print routines to direct their output to the first serial port on these devices. The UART physical and virtual address is automatically provided based on the chip identification register value. If you have a Broadcom STB chip and would like early print messages to appear over the UART, select this option. 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 select DEBUG_UART_8250 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 select DEBUG_UART_8250 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_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_DIGICOLOR_UA0 bool "Kernel low-level debugging messages via Digicolor UA0" depends on ARCH_DIGICOLOR help Say Y here if you want the debug print routines to direct their output to the UA0 serial port in the CX92755. config DEBUG_EP93XX bool "Kernel low-level debugging messages via ep93xx UART" depends on ARCH_EP93XX select DEBUG_UART_PL01X help Say Y here if you want kernel low-level debugging support on Cirrus Logic EP93xx based platforms. config DEBUG_FOOTBRIDGE_COM1 bool "Kernel low-level debugging messages via footbridge 8250 at PCI COM1" depends on FOOTBRIDGE select DEBUG_UART_8250 help Say Y here if you want the debug print routines to direct their output to the 8250 at PCI COM1. config DEBUG_GEMINI bool "Kernel low-level debugging messages via Cortina Systems Gemini UART" depends on ARCH_GEMINI select DEBUG_UART_8250 help Say Y here if you want kernel low-level debugging support on Cortina Gemini based platforms. config DEBUG_HI3620_UART bool "Hisilicon HI3620 Debug UART" depends on ARCH_HI3xxx select DEBUG_UART_PL01X help Say Y here if you want kernel low-level debugging support on HI3620 UART. config DEBUG_HIGHBANK_UART bool "Kernel low-level debugging messages via Highbank UART" depends on ARCH_HIGHBANK select DEBUG_UART_PL01X help Say Y here if you want the debug print routines to direct their output to the UART on Highbank based devices. config DEBUG_HIP01_UART bool "Hisilicon Hip01 Debug UART" depends on ARCH_HIP01 select DEBUG_UART_8250 help Say Y here if you want kernel low-level debugging support on HIP01 UART. config DEBUG_HIP04_UART bool "Hisilicon HiP04 Debug UART" depends on ARCH_HIP04 select DEBUG_UART_8250 help Say Y here if you want kernel low-level debugging support on HIP04 UART. config DEBUG_HIX5HD2_UART bool "Hisilicon Hix5hd2 Debug UART" depends on ARCH_HIX5HD2 select DEBUG_UART_PL01X help Say Y here if you want kernel low-level debugging support on Hix5hd2 UART. 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 select DEBUG_UART_PL01X 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_IMX27_UART bool "i.MX27 Debug UART" depends on SOC_IMX27 help Say Y here if you want kernel low-level debugging support on i.MX27. config DEBUG_IMX28_UART bool "i.MX28 Debug UART" depends on SOC_IMX28 select DEBUG_UART_PL01X help Say Y here if you want kernel low-level debugging support on i.MX28. config DEBUG_IMX31_UART bool "i.MX31 Debug UART" depends on SOC_IMX31 help Say Y here if you want kernel low-level debugging support on i.MX31. config DEBUG_IMX35_UART bool "i.MX35 Debug UART" depends on SOC_IMX35 help Say Y here if you want kernel low-level debugging support on i.MX35. config DEBUG_IMX50_UART bool "i.MX50 Debug UART" depends on SOC_IMX50 help Say Y here if you want kernel low-level debugging support on i.MX50. 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_IMX53_UART bool "i.MX53 Debug UART" depends on SOC_IMX53 help Say Y here if you want kernel low-level debugging support on i.MX53. config DEBUG_IMX6Q_UART bool "i.MX6Q/DL Debug UART" depends on SOC_IMX6Q help Say Y here if you want kernel low-level debugging support on i.MX6Q/DL. config DEBUG_IMX6SL_UART bool "i.MX6SL Debug UART" depends on SOC_IMX6SL help Say Y here if you want kernel low-level debugging support on i.MX6SL. config DEBUG_IMX6SX_UART bool "i.MX6SX Debug UART" depends on SOC_IMX6SX help Say Y here if you want kernel low-level debugging support on i.MX6SX. config DEBUG_IMX6UL_UART bool "i.MX6UL Debug UART" depends on SOC_IMX6ULLines 1–500 of 1846. Load more
# SPDX-License-Identifier: GPL-2.0 config ARM_PTDUMP_CORE def_bool n config ARM_PTDUMP_DEBUGFS bool "Export kernel pagetable layout to userspace via debugfs" depends on DEBUG_KERNEL depends on MMU select ARM_PTDUMP_CORE select DEBUG_FS help Say Y here if you want to show the kernel pagetable layout in a debugfs file. This information is only useful for kernel developers who are working in architecture specific areas of the kernel. It is probably not a good idea to enable this feature in a production kernel. If in doubt, say "N" config ARM_DEBUG_WX bool "Warn on W+X mappings at boot" depends on MMU select ARM_PTDUMP_CORE help Generate a warning if any W+X mappings are found at boot. This is useful for discovering cases where the kernel is leaving W+X mappings after applying NX, as such mappings are a security risk. Look for a message in dmesg output like this: arm/mm: Checked W+X mappings: passed, no W+X pages found. or like this, if the check failed: arm/mm: Checked W+X mappings: FAILED, <N> W+X pages found. Note that even if the check fails, your kernel is possibly still fine, as W+X mappings are not a security hole in themselves, what they do is that they make the exploitation of other unfixed kernel bugs easier. There is no runtime or memory usage effect of this option once the kernel has booted up - it's a one time check. If in doubt, say "Y". choice prompt "Choose kernel unwinder" default UNWINDER_ARM if AEABI default UNWINDER_FRAME_POINTER if !AEABI help This determines which method will be used for unwinding kernel stack traces for panics, oopses, bugs, warnings, perf, /proc/<pid>/stack, livepatch, lockdep, and more. config UNWINDER_FRAME_POINTER bool "Frame pointer unwinder" depends on !THUMB2_KERNEL select ARCH_WANT_FRAME_POINTERS select FRAME_POINTER help This option enables the frame pointer unwinder for unwinding kernel stack traces. config UNWINDER_ARM bool "ARM EABI stack unwinder" depends on AEABI select ARM_UNWIND 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. endchoice config ARM_UNWIND bool config BACKTRACE_VERBOSE bool "Verbose backtrace" depends on EXPERT help When the kernel produces a warning or oops, the kernel prints a trace of the call chain. This option controls whether we include the numeric addresses or only include the symbolic information. In most cases, say N here, unless you are intending to debug the kernel and have access to the kernel binary image. 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 DEBUG_ALPINE_UART0 bool "Kernel low-level debugging messages via Alpine UART0" depends on ARCH_ALPINE select DEBUG_UART_8250 help Say Y here if you want kernel low-level debugging support on Alpine based platforms. config DEBUG_ASM9260_UART bool "Kernel low-level debugging via asm9260 UART" depends on MACH_ASM9260 help Say Y here if you want the debug print routines to direct their output to an UART or USART port on asm9260 based machines. DEBUG_UART_PHYS | DEBUG_UART_VIRT 0x80000000 | 0xf0000000 | UART0 0x80004000 | 0xf0004000 | UART1 0x80008000 | 0xf0008000 | UART2 0x8000c000 | 0xf000c000 | UART3 0x80010000 | 0xf0010000 | UART4 0x80014000 | 0xf0014000 | UART5 0x80018000 | 0xf0018000 | UART6 0x8001c000 | 0xf001c000 | UART7 0x80020000 | 0xf0020000 | UART8 0x80024000 | 0xf0024000 | UART9 config DEBUG_AT91_RM9200_DBGU bool "Kernel low-level debugging on AT91RM9200, AT91SAM9, SAM9X60 DBGU" select DEBUG_AT91_UART depends on SOC_AT91RM9200 || SOC_AT91SAM9 || SOC_SAM9X60 help Say Y here if you want kernel low-level debugging support on the DBGU port of: at91rm9200, at91sam9260, at91sam9g20, at91sam9261, at91sam9g10, at91sam9n12, at91sam9rl64, at91sam9x5, sam9x60 config DEBUG_AT91_SAM9263_DBGU bool "Kernel low-level debugging on AT91SAM{9263,9G45,A5D3} DBGU" select DEBUG_AT91_UART depends on SOC_AT91SAM9 || SOC_SAMA5D3 help Say Y here if you want kernel low-level debugging support on the DBGU port of: at91sam9263, at91sam9g45, at91sam9m10, sama5d3 config DEBUG_AT91_SAMA5D2_UART1 bool "Kernel low-level debugging on SAMA5D2 UART1" select DEBUG_AT91_UART depends on SOC_SAMA5D2 help Say Y here if you want kernel low-level debugging support on the UART1 port of sama5d2. config DEBUG_AT91_SAMA5D4_USART3 bool "Kernel low-level debugging on SAMA5D4 USART3" select DEBUG_AT91_UART depends on SOC_SAMA5D4 help Say Y here if you want kernel low-level debugging support on the USART3 port of sama5d4. config DEBUG_AT91_SAMV7_USART1 bool "Kernel low-level debugging via SAMV7 USART1" select DEBUG_AT91_UART depends on SOC_SAMV7 help Say Y here if you want the debug print routines to direct their output to the USART1 port on SAMV7 based machines. config DEBUG_AT91_SAMA7G5_FLEXCOM3 bool "Kernel low-level debugging on SAMA7G5 FLEXCOM3" select DEBUG_AT91_UART depends on SOC_SAMA7G5 help Say Y here if you want kernel low-level debugging support on the FLEXCOM3 port of SAMA7G5. config DEBUG_AT91_LAN966_FLEXCOM bool "Kernel low-level debugging on LAN966 FLEXCOM USART" select DEBUG_AT91_UART depends on SOC_LAN966 help Say Y here if you want kernel low-level debugging support on the FLEXCOM port of LAN966. DEBUG_UART_PHYS | DEBUG_UART_VIRT 0xe0040200 | 0xfd040200 | FLEXCOM0 0xe0044200 | 0xfd044200 | FLEXCOM1 0xe0060200 | 0xfd060200 | FLEXCOM2 0xe0064200 | 0xfd064200 | FLEXCOM3 0xe0070200 | 0xfd070200 | FLEXCOM4 By default, enabling FLEXCOM3 port. Based on requirement, use DEBUG_UART_PHYS and DEBUG_UART_VIRT configurations from above table. config DEBUG_BCM2835 bool "Kernel low-level debugging on BCM2835 PL011 UART" depends on ARCH_BCM2835 && ARCH_MULTI_V6 select DEBUG_UART_PL01X config DEBUG_BCM2836 bool "Kernel low-level debugging on BCM2836 PL011 UART" depends on ARCH_BCM2835 && ARCH_MULTI_V7 select DEBUG_UART_PL01X config DEBUG_BCM_5301X bool "Kernel low-level debugging on BCM5301X/NSP UART1" depends on ARCH_BCM_5301X || ARCH_BCM_NSP select DEBUG_UART_8250 config DEBUG_BCMBCA bool "Kernel low-level debugging on BCMBCA UART0" depends on ARCH_BCMBCA config DEBUG_BCM_HR2 bool "Kernel low-level debugging on Hurricane 2 UART2" depends on ARCH_BCM_HR2 select DEBUG_UART_8250 config DEBUG_BCM_IPROC_UART3 bool "Kernel low-level debugging on BCM IPROC UART3" depends on ARCH_BCM_CYGNUS select DEBUG_UART_8250 help Say Y here if you want the debug print routines to direct their output to the third serial port on these devices. config DEBUG_BCM_KONA_UART bool "Kernel low-level debugging messages via BCM KONA UART" depends on ARCH_BCM_MOBILE select DEBUG_UART_8250 help Say Y here if you want kernel low-level debugging support on Broadcom SoC platforms. This low level debug works for Broadcom mobile SoCs in the Kona family of chips (e.g. bcm28155, bcm11351, etc...) config DEBUG_BCM63XX_UART bool "Kernel low-level debugging on BCM63XX UART" depends on ARCH_BCMBCA config DEBUG_BERLIN_UART bool "Marvell Berlin SoC Debug UART" depends on ARCH_BERLIN select DEBUG_UART_8250 help Say Y here if you want kernel low-level debugging support on Marvell Berlin SoC based platforms. config DEBUG_BRCMSTB_UART bool "Use BRCMSTB UART for low-level debug" depends on ARCH_BRCMSTB help Say Y here if you want the debug print routines to direct their output to the first serial port on these devices. The UART physical and virtual address is automatically provided based on the chip identification register value. If you have a Broadcom STB chip and would like early print messages to appear over the UART, select this option. 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 select DEBUG_UART_8250 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 select DEBUG_UART_8250 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_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_DIGICOLOR_UA0 bool "Kernel low-level debugging messages via Digicolor UA0" depends on ARCH_DIGICOLOR help Say Y here if you want the debug print routines to direct their output to the UA0 serial port in the CX92755. config DEBUG_EP93XX bool "Kernel low-level debugging messages via ep93xx UART" depends on ARCH_EP93XX select DEBUG_UART_PL01X help Say Y here if you want kernel low-level debugging support on Cirrus Logic EP93xx based platforms. config DEBUG_FOOTBRIDGE_COM1 bool "Kernel low-level debugging messages via footbridge 8250 at PCI COM1" depends on FOOTBRIDGE select DEBUG_UART_8250 help Say Y here if you want the debug print routines to direct their output to the 8250 at PCI COM1. config DEBUG_GEMINI bool "Kernel low-level debugging messages via Cortina Systems Gemini UART" depends on ARCH_GEMINI select DEBUG_UART_8250 help Say Y here if you want kernel low-level debugging support on Cortina Gemini based platforms. config DEBUG_HI3620_UART bool "Hisilicon HI3620 Debug UART" depends on ARCH_HI3xxx select DEBUG_UART_PL01X help Say Y here if you want kernel low-level debugging support on HI3620 UART. config DEBUG_HIGHBANK_UART bool "Kernel low-level debugging messages via Highbank UART" depends on ARCH_HIGHBANK select DEBUG_UART_PL01X help Say Y here if you want the debug print routines to direct their output to the UART on Highbank based devices. config DEBUG_HIP01_UART bool "Hisilicon Hip01 Debug UART" depends on ARCH_HIP01 select DEBUG_UART_8250 help Say Y here if you want kernel low-level debugging support on HIP01 UART. config DEBUG_HIP04_UART bool "Hisilicon HiP04 Debug UART" depends on ARCH_HIP04 select DEBUG_UART_8250 help Say Y here if you want kernel low-level debugging support on HIP04 UART. config DEBUG_HIX5HD2_UART bool "Hisilicon Hix5hd2 Debug UART" depends on ARCH_HIX5HD2 select DEBUG_UART_PL01X help Say Y here if you want kernel low-level debugging support on Hix5hd2 UART. 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 select DEBUG_UART_PL01X 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_IMX27_UART bool "i.MX27 Debug UART" depends on SOC_IMX27 help Say Y here if you want kernel low-level debugging support on i.MX27. config DEBUG_IMX28_UART bool "i.MX28 Debug UART" depends on SOC_IMX28 select DEBUG_UART_PL01X help Say Y here if you want kernel low-level debugging support on i.MX28. config DEBUG_IMX31_UART bool "i.MX31 Debug UART" depends on SOC_IMX31 help Say Y here if you want kernel low-level debugging support on i.MX31. config DEBUG_IMX35_UART bool "i.MX35 Debug UART" depends on SOC_IMX35 help Say Y here if you want kernel low-level debugging support on i.MX35. config DEBUG_IMX50_UART bool "i.MX50 Debug UART" depends on SOC_IMX50 help Say Y here if you want kernel low-level debugging support on i.MX50. 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_IMX53_UART bool "i.MX53 Debug UART" depends on SOC_IMX53 help Say Y here if you want kernel low-level debugging support on i.MX53. config DEBUG_IMX6Q_UART bool "i.MX6Q/DL Debug UART" depends on SOC_IMX6Q help Say Y here if you want kernel low-level debugging support on i.MX6Q/DL. config DEBUG_IMX6SL_UART bool "i.MX6SL Debug UART" depends on SOC_IMX6SL help Say Y here if you want kernel low-level debugging support on i.MX6SL. config DEBUG_IMX6SX_UART bool "i.MX6SX Debug UART" depends on SOC_IMX6SX help Say Y here if you want kernel low-level debugging support on i.MX6SX. config DEBUG_IMX6UL_UART bool "i.MX6UL Debug UART" depends on SOC_IMX6UL