License cleanup: add SPDX GPL-2.0 license identifier to files with no license
Many source files in the tree are missing licensing information, which
makes it harder for compliance tools to determine the correct license.
By default all files without license information are under the default
license of the kernel, which is GPL version 2.
Update the files which contain no license information with the 'GPL-2.0'
SPDX license identifier. The SPDX identifier is a legally binding
shorthand, which can be used instead of the full boiler plate text.
This patch is based on work done by Thomas Gleixner and Kate Stewart and
Philippe Ombredanne.
How this work was done:
Patches were generated and checked against linux-4.14-rc6 for a subset of
the use cases:
- file had no licensing information it it.
- file was a */uapi/* one with no licensing information in it,
- file was a */uapi/* one with existing licensing information,
Further patches will be generated in subsequent months to fix up cases
where non-standard license headers were used, and references to license
had to be inferred by heuristics based on keywords.
The analysis to determine which SPDX License Identifier to be applied to
a file was done in a spreadsheet of side by side results from of the
output of two independent scanners (ScanCode & Windriver) producing SPDX
tag:value files created by Philippe Ombredanne. Philippe prepared the
base worksheet, and did an initial spot review of a few 1000 files.
The 4.13 kernel was the starting point of the analysis with 60,537 files
assessed. Kate Stewart did a file by file comparison of the scanner
results in the spreadsheet to determine which SPDX license identifier(s)
to be applied to the file. She confirmed any determination that was not
immediately clear with lawyers working with the Linux Foundation.
Criteria used to select files for SPDX license identifier tagging was:
- Files considered eligible had to be source code files.
- Make and config files were included as candidates if they contained >5
lines of source
- File already had some variant of a license header in it (even if <5
lines).
All documentation files were explicitly excluded.
The following heuristics were used to determine which SPDX license
identifiers to apply.
- when both scanners couldn't find any license traces, file was
considered to have no license information in it, and the top level
COPYING file license applied.
For non */uapi/* files that summary was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 11139
and resulted in the first patch in this series.
If that file was a */uapi/* path one, it was "GPL-2.0 WITH
Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 WITH Linux-syscall-note 930
and resulted in the second patch in this series.
- if a file had some form of licensing information in it, and was one
of the */uapi/* ones, it was denoted with the Linux-syscall-note if
any GPL family license was found in the file or had no licensing in
it (per prior point). Results summary:
SPDX license identifier # files
---------------------------------------------------|------
GPL-2.0 WITH Linux-syscall-note 270
GPL-2.0+ WITH Linux-syscall-note 169
((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21
((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17
LGPL-2.1+ WITH Linux-syscall-note 15
GPL-1.0+ WITH Linux-syscall-note 14
((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5
LGPL-2.0+ WITH Linux-syscall-note 4
LGPL-2.1 WITH Linux-syscall-note 3
((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3
((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1
and that resulted in the third patch in this series.
- when the two scanners agreed on the detected license(s), that became
the concluded license(s).
- when there was disagreement between the two scanners (one detected a
license but the other didn't, or they both detected different
licenses) a manual inspection of the file occurred.
- In most cases a manual inspection of the information in the file
resulted in a clear resolution of the license that should apply (and
which scanner probably needed to revisit its heuristics).
- When it was not immediately clear, the license identifier was
confirmed with lawyers working with the Linux Foundation.
- If there was any question as to the appropriate license identifier,
the file was flagged for further research and to be revisited later
in time.
In total, over 70 hours of logged manual review was done on the
spreadsheet to determine the SPDX license identifiers to apply to the
source files by Kate, Philippe, Thomas and, in some cases, confirmation
by lawyers working with the Linux Foundation.
Kate also obtained a third independent scan of the 4.13 code base from
FOSSology, and compared selected files where the other two scanners
disagreed against that SPDX file, to see if there was new insights. The
Windriver scanner is based on an older version of FOSSology in part, so
they are related.
Thomas did random spot checks in about 500 files from the spreadsheets
for the uapi headers and agreed with SPDX license identifier in the
files he inspected. For the non-uapi files Thomas did random spot checks
in about 15000 files.
In initial set of patches against 4.14-rc6, 3 files were found to have
copy/paste license identifier errors, and have been fixed to reflect the
correct identifier.
Additionally Philippe spent 10 hours this week doing a detailed manual
inspection and review of the 12,461 patched files from the initial patch
version early this week with:
- a full scancode scan run, collecting the matched texts, detected
license ids and scores
- reviewing anything where there was a license detected (about 500+
files) to ensure that the applied SPDX license was correct
- reviewing anything where there was no detection but the patch license
was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied
SPDX license was correct
This produced a worksheet with 20 files needing minor correction. This
worksheet was then exported into 3 different .csv files for the
different types of files to be modified.
These .csv files were then reviewed by Greg. Thomas wrote a script to
parse the csv files and add the proper SPDX tag to the file, in the
format that the file expected. This script was further refined by Greg
based on the output to detect more types of files automatically and to
distinguish between header and source .c files (which need different
comment types.) Finally Greg ran the script using the .csv files to
generate the patches.
Reviewed-by: Kate Stewart <kstewart@linuxfoundation.org>
Reviewed-by: Philippe Ombredanne <pombredanne@nexb.com>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2017-11-01 14:07:57 +00:00
|
|
|
# SPDX-License-Identifier: GPL-2.0
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2017-12-12 00:41:09 +00:00
|
|
|
config ARM_PTDUMP_CORE
|
|
|
|
|
def_bool n
|
|
|
|
|
|
|
|
|
|
config ARM_PTDUMP_DEBUGFS
|
2013-10-23 15:13:02 +00:00
|
|
|
bool "Export kernel pagetable layout to userspace via debugfs"
|
|
|
|
|
depends on DEBUG_KERNEL
|
2015-05-26 15:07:51 +00:00
|
|
|
depends on MMU
|
2017-12-12 00:41:09 +00:00
|
|
|
select ARM_PTDUMP_CORE
|
2013-10-23 15:13:02 +00:00
|
|
|
select DEBUG_FS
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2013-10-23 15:13:02 +00:00
|
|
|
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"
|
|
|
|
|
|
2024-01-30 10:34:32 +00:00
|
|
|
config ARM_DEBUG_WX
|
2017-12-12 00:43:57 +00:00
|
|
|
bool "Warn on W+X mappings at boot"
|
2018-02-28 13:56:07 +00:00
|
|
|
depends on MMU
|
2017-12-12 00:43:57 +00:00
|
|
|
select ARM_PTDUMP_CORE
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2017-12-12 00:43:57 +00:00
|
|
|
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".
|
|
|
|
|
|
ARM: 8800/1: use choice for kernel unwinders
While in theory multiple unwinders could be compiled in, it does
not make sense in practise. Use a choice to make the unwinder
selection mutually exclusive and mandatory.
Already before this commit it has not been possible to deselect
FRAME_POINTER. Remove the obsolete comment.
Furthermore, to produce a meaningful backtrace with FRAME_POINTER
enabled the kernel needs a specific function prologue:
mov ip, sp
stmfd sp!, {fp, ip, lr, pc}
sub fp, ip, #4
To get to the required prologue gcc uses apcs and no-sched-prolog.
This compiler options are not available on clang, and clang is not
able to generate the required prologue. Make the FRAME_POINTER
config symbol depending on !clang.
Suggested-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Stefan Agner <stefan@agner.ch>
Reviewed-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
2018-09-30 22:02:33 +00:00
|
|
|
choice
|
|
|
|
|
prompt "Choose kernel unwinder"
|
2019-04-23 16:09:38 +00:00
|
|
|
default UNWINDER_ARM if AEABI
|
|
|
|
|
default UNWINDER_FRAME_POINTER if !AEABI
|
ARM: 8800/1: use choice for kernel unwinders
While in theory multiple unwinders could be compiled in, it does
not make sense in practise. Use a choice to make the unwinder
selection mutually exclusive and mandatory.
Already before this commit it has not been possible to deselect
FRAME_POINTER. Remove the obsolete comment.
Furthermore, to produce a meaningful backtrace with FRAME_POINTER
enabled the kernel needs a specific function prologue:
mov ip, sp
stmfd sp!, {fp, ip, lr, pc}
sub fp, ip, #4
To get to the required prologue gcc uses apcs and no-sched-prolog.
This compiler options are not available on clang, and clang is not
able to generate the required prologue. Make the FRAME_POINTER
config symbol depending on !clang.
Suggested-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Stefan Agner <stefan@agner.ch>
Reviewed-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
2018-09-30 22:02:33 +00:00
|
|
|
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"
|
2019-08-22 20:26:53 +00:00
|
|
|
depends on !THUMB2_KERNEL
|
ARM: 8800/1: use choice for kernel unwinders
While in theory multiple unwinders could be compiled in, it does
not make sense in practise. Use a choice to make the unwinder
selection mutually exclusive and mandatory.
Already before this commit it has not been possible to deselect
FRAME_POINTER. Remove the obsolete comment.
Furthermore, to produce a meaningful backtrace with FRAME_POINTER
enabled the kernel needs a specific function prologue:
mov ip, sp
stmfd sp!, {fp, ip, lr, pc}
sub fp, ip, #4
To get to the required prologue gcc uses apcs and no-sched-prolog.
This compiler options are not available on clang, and clang is not
able to generate the required prologue. Make the FRAME_POINTER
config symbol depending on !clang.
Suggested-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Stefan Agner <stefan@agner.ch>
Reviewed-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
2018-09-30 22:02:33 +00:00
|
|
|
select ARCH_WANT_FRAME_POINTERS
|
|
|
|
|
select FRAME_POINTER
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
ARM: 8800/1: use choice for kernel unwinders
While in theory multiple unwinders could be compiled in, it does
not make sense in practise. Use a choice to make the unwinder
selection mutually exclusive and mandatory.
Already before this commit it has not been possible to deselect
FRAME_POINTER. Remove the obsolete comment.
Furthermore, to produce a meaningful backtrace with FRAME_POINTER
enabled the kernel needs a specific function prologue:
mov ip, sp
stmfd sp!, {fp, ip, lr, pc}
sub fp, ip, #4
To get to the required prologue gcc uses apcs and no-sched-prolog.
This compiler options are not available on clang, and clang is not
able to generate the required prologue. Make the FRAME_POINTER
config symbol depending on !clang.
Suggested-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Stefan Agner <stefan@agner.ch>
Reviewed-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
2018-09-30 22:02:33 +00:00
|
|
|
This option enables the frame pointer unwinder for unwinding
|
|
|
|
|
kernel stack traces.
|
2009-02-12 12:56:34 +00:00
|
|
|
|
ARM: 8800/1: use choice for kernel unwinders
While in theory multiple unwinders could be compiled in, it does
not make sense in practise. Use a choice to make the unwinder
selection mutually exclusive and mandatory.
Already before this commit it has not been possible to deselect
FRAME_POINTER. Remove the obsolete comment.
Furthermore, to produce a meaningful backtrace with FRAME_POINTER
enabled the kernel needs a specific function prologue:
mov ip, sp
stmfd sp!, {fp, ip, lr, pc}
sub fp, ip, #4
To get to the required prologue gcc uses apcs and no-sched-prolog.
This compiler options are not available on clang, and clang is not
able to generate the required prologue. Make the FRAME_POINTER
config symbol depending on !clang.
Suggested-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Stefan Agner <stefan@agner.ch>
Reviewed-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
2018-09-30 22:02:33 +00:00
|
|
|
config UNWINDER_ARM
|
|
|
|
|
bool "ARM EABI stack unwinder"
|
2022-01-25 14:55:24 +00:00
|
|
|
depends on AEABI
|
ARM: 8800/1: use choice for kernel unwinders
While in theory multiple unwinders could be compiled in, it does
not make sense in practise. Use a choice to make the unwinder
selection mutually exclusive and mandatory.
Already before this commit it has not been possible to deselect
FRAME_POINTER. Remove the obsolete comment.
Furthermore, to produce a meaningful backtrace with FRAME_POINTER
enabled the kernel needs a specific function prologue:
mov ip, sp
stmfd sp!, {fp, ip, lr, pc}
sub fp, ip, #4
To get to the required prologue gcc uses apcs and no-sched-prolog.
This compiler options are not available on clang, and clang is not
able to generate the required prologue. Make the FRAME_POINTER
config symbol depending on !clang.
Suggested-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Stefan Agner <stefan@agner.ch>
Reviewed-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
2018-09-30 22:02:33 +00:00
|
|
|
select ARM_UNWIND
|
2009-02-12 12:56:34 +00:00
|
|
|
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
|
ARM: 8800/1: use choice for kernel unwinders
While in theory multiple unwinders could be compiled in, it does
not make sense in practise. Use a choice to make the unwinder
selection mutually exclusive and mandatory.
Already before this commit it has not been possible to deselect
FRAME_POINTER. Remove the obsolete comment.
Furthermore, to produce a meaningful backtrace with FRAME_POINTER
enabled the kernel needs a specific function prologue:
mov ip, sp
stmfd sp!, {fp, ip, lr, pc}
sub fp, ip, #4
To get to the required prologue gcc uses apcs and no-sched-prolog.
This compiler options are not available on clang, and clang is not
able to generate the required prologue. Make the FRAME_POINTER
config symbol depending on !clang.
Suggested-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Stefan Agner <stefan@agner.ch>
Reviewed-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
2018-09-30 22:02:33 +00:00
|
|
|
only works with EABI compilers.
|
|
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
|
|
|
|
config ARM_UNWIND
|
|
|
|
|
bool
|
|
|
|
|
|
2021-05-13 09:59:23 +00:00
|
|
|
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.
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
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
|
2011-09-01 18:04:44 +00:00
|
|
|
bool "Kernel low-level debugging functions (read help!)"
|
2005-04-16 22:20:36 +00:00
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
|
help
|
2005-09-09 14:57:17 +00:00
|
|
|
Say Y here to include definitions of printascii, printch, printhex
|
2005-04-16 22:20:36 +00:00
|
|
|
in the kernel. This is helpful if you are debugging code that
|
|
|
|
|
executes before the console is initialized.
|
|
|
|
|
|
2011-09-01 18:04:44 +00:00
|
|
|
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.
|
|
|
|
|
|
2011-09-01 17:58:51 +00:00
|
|
|
choice
|
|
|
|
|
prompt "Kernel low-level debugging port"
|
|
|
|
|
depends on DEBUG_LL
|
|
|
|
|
|
2015-03-12 11:53:04 +00:00
|
|
|
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.
|
|
|
|
|
|
2014-11-24 11:08:28 +00:00
|
|
|
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
|
|
|
|
|
|
2016-06-08 10:21:38 +00:00
|
|
|
config DEBUG_AT91_RM9200_DBGU
|
2019-11-29 13:51:43 +00:00
|
|
|
bool "Kernel low-level debugging on AT91RM9200, AT91SAM9, SAM9X60 DBGU"
|
2016-06-08 10:21:38 +00:00
|
|
|
select DEBUG_AT91_UART
|
2019-11-29 13:51:43 +00:00
|
|
|
depends on SOC_AT91RM9200 || SOC_AT91SAM9 || SOC_SAM9X60
|
2015-08-08 10:11:11 +00:00
|
|
|
help
|
2016-06-08 10:21:38 +00:00
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on the DBGU port of:
|
|
|
|
|
at91rm9200, at91sam9260, at91sam9g20, at91sam9261,
|
2019-11-29 13:51:43 +00:00
|
|
|
at91sam9g10, at91sam9n12, at91sam9rl64, at91sam9x5, sam9x60
|
2011-11-01 17:43:31 +00:00
|
|
|
|
2016-06-08 10:21:38 +00:00
|
|
|
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
|
2014-09-15 16:15:54 +00:00
|
|
|
|
2016-06-08 10:21:38 +00:00
|
|
|
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.
|
2015-07-30 17:12:12 +00:00
|
|
|
|
2017-05-31 01:06:24 +00:00
|
|
|
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.
|
|
|
|
|
|
2021-04-09 11:31:16 +00:00
|
|
|
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.
|
|
|
|
|
|
2022-05-13 09:25:30 +00:00
|
|
|
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.
|
|
|
|
|
|
2013-03-12 04:40:18 +00:00
|
|
|
config DEBUG_BCM2835
|
|
|
|
|
bool "Kernel low-level debugging on BCM2835 PL011 UART"
|
2015-02-24 15:07:55 +00:00
|
|
|
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
|
2013-07-07 11:32:16 +00:00
|
|
|
select DEBUG_UART_PL01X
|
2013-03-12 04:40:18 +00:00
|
|
|
|
2014-02-03 23:01:44 +00:00
|
|
|
config DEBUG_BCM_5301X
|
2016-07-01 00:10:10 +00:00
|
|
|
bool "Kernel low-level debugging on BCM5301X/NSP UART1"
|
|
|
|
|
depends on ARCH_BCM_5301X || ARCH_BCM_NSP
|
2014-09-14 19:43:40 +00:00
|
|
|
select DEBUG_UART_8250
|
2014-02-03 23:01:44 +00:00
|
|
|
|
2024-09-23 19:49:21 +00:00
|
|
|
config DEBUG_BCMBCA
|
|
|
|
|
bool "Kernel low-level debugging on BCMBCA UART0"
|
|
|
|
|
depends on ARCH_BCMBCA
|
|
|
|
|
|
2017-09-28 23:14:59 +00:00
|
|
|
config DEBUG_BCM_HR2
|
|
|
|
|
bool "Kernel low-level debugging on Hurricane 2 UART2"
|
|
|
|
|
depends on ARCH_BCM_HR2
|
|
|
|
|
select DEBUG_UART_8250
|
|
|
|
|
|
2018-05-30 13:19:55 +00:00
|
|
|
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.
|
|
|
|
|
|
2013-12-23 08:00:01 +00:00
|
|
|
config DEBUG_BCM_KONA_UART
|
|
|
|
|
bool "Kernel low-level debugging messages via BCM KONA UART"
|
2014-03-06 17:45:55 +00:00
|
|
|
depends on ARCH_BCM_MOBILE
|
2013-12-23 08:00:01 +00:00
|
|
|
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...)
|
|
|
|
|
|
2016-01-18 09:45:00 +00:00
|
|
|
config DEBUG_BCM63XX_UART
|
2014-01-08 17:19:50 +00:00
|
|
|
bool "Kernel low-level debugging on BCM63XX UART"
|
2022-07-07 06:57:52 +00:00
|
|
|
depends on ARCH_BCMBCA
|
2014-01-08 17:19:50 +00:00
|
|
|
|
2013-09-09 12:10:54 +00:00
|
|
|
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.
|
|
|
|
|
|
2014-08-13 22:50:02 +00:00
|
|
|
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
|
2016-06-28 19:18:51 +00:00
|
|
|
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.
|
2014-08-13 22:50:02 +00:00
|
|
|
|
|
|
|
|
If you have a Broadcom STB chip and would like early print
|
|
|
|
|
messages to appear over the UART, select this option.
|
|
|
|
|
|
2011-09-22 19:28:35 +00:00
|
|
|
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.
|
2011-09-01 17:58:51 +00:00
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
2012-03-22 09:29:23 +00:00
|
|
|
config DEBUG_DAVINCI_DA8XX_UART1
|
|
|
|
|
bool "Kernel low-level debugging on DaVinci DA8XX using UART1"
|
|
|
|
|
depends on ARCH_DAVINCI_DA8XX
|
2013-07-07 15:18:34 +00:00
|
|
|
select DEBUG_UART_8250
|
2012-03-22 09:29:23 +00:00
|
|
|
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
|
2013-07-07 15:18:34 +00:00
|
|
|
select DEBUG_UART_8250
|
2012-03-22 09:29:23 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want the debug print routines to direct
|
|
|
|
|
their output to UART2 serial port on DaVinci DA8XX devices.
|
|
|
|
|
|
2011-11-23 17:44:05 +00:00
|
|
|
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).
|
|
|
|
|
|
2015-01-14 08:40:31 +00:00
|
|
|
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.
|
|
|
|
|
|
2015-12-03 15:19:22 +00:00
|
|
|
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.
|
|
|
|
|
|
2011-11-23 17:44:05 +00:00
|
|
|
config DEBUG_FOOTBRIDGE_COM1
|
|
|
|
|
bool "Kernel low-level debugging messages via footbridge 8250 at PCI COM1"
|
|
|
|
|
depends on FOOTBRIDGE
|
2015-12-03 17:27:53 +00:00
|
|
|
select DEBUG_UART_8250
|
2011-11-23 17:44:05 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want the debug print routines to direct
|
|
|
|
|
their output to the 8250 at PCI COM1.
|
|
|
|
|
|
2015-12-03 16:54:05 +00:00
|
|
|
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.
|
|
|
|
|
|
2013-08-24 05:58:39 +00:00
|
|
|
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.
|
|
|
|
|
|
2011-06-07 15:02:55 +00:00
|
|
|
config DEBUG_HIGHBANK_UART
|
|
|
|
|
bool "Kernel low-level debugging messages via Highbank UART"
|
|
|
|
|
depends on ARCH_HIGHBANK
|
2013-07-07 11:32:16 +00:00
|
|
|
select DEBUG_UART_PL01X
|
2011-06-07 15:02:55 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want the debug print routines to direct
|
|
|
|
|
their output to the UART on Highbank based devices.
|
|
|
|
|
|
2014-12-24 03:09:56 +00:00
|
|
|
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.
|
|
|
|
|
|
2013-12-20 07:01:41 +00:00
|
|
|
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.
|
|
|
|
|
|
2014-09-24 05:21:54 +00:00
|
|
|
config DEBUG_HIX5HD2_UART
|
|
|
|
|
bool "Hisilicon Hix5hd2 Debug UART"
|
|
|
|
|
depends on ARCH_HIX5HD2
|
2013-07-07 11:32:16 +00:00
|
|
|
select DEBUG_UART_PL01X
|
2011-06-07 15:02:55 +00:00
|
|
|
help
|
2014-09-24 05:21:54 +00:00
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on Hix5hd2 UART.
|
2011-06-07 15:02:55 +00:00
|
|
|
|
2011-08-19 04:56:59 +00:00
|
|
|
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
|
2013-07-07 11:32:16 +00:00
|
|
|
select DEBUG_UART_PL01X
|
2011-08-19 04:56:59 +00:00
|
|
|
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.
|
|
|
|
|
|
2021-10-28 14:19:33 +00:00
|
|
|
config DEBUG_IMX27_UART
|
|
|
|
|
bool "i.MX27 Debug UART"
|
|
|
|
|
depends on SOC_IMX27
|
2011-08-19 04:56:59 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
2021-10-28 14:19:33 +00:00
|
|
|
on i.MX27.
|
2011-08-19 04:56:59 +00:00
|
|
|
|
|
|
|
|
config DEBUG_IMX28_UART
|
|
|
|
|
bool "i.MX28 Debug UART"
|
|
|
|
|
depends on SOC_IMX28
|
2013-07-07 11:32:16 +00:00
|
|
|
select DEBUG_UART_PL01X
|
2011-08-19 04:56:59 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on i.MX28.
|
|
|
|
|
|
2012-12-12 10:54:01 +00:00
|
|
|
config DEBUG_IMX31_UART
|
|
|
|
|
bool "i.MX31 Debug UART"
|
|
|
|
|
depends on SOC_IMX31
|
2011-08-19 04:56:59 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
2012-12-12 10:54:01 +00:00
|
|
|
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.
|
2011-08-19 04:56:59 +00:00
|
|
|
|
2013-10-29 05:15:51 +00:00
|
|
|
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.
|
|
|
|
|
|
2011-08-19 04:56:59 +00:00
|
|
|
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.
|
|
|
|
|
|
2013-01-22 12:40:55 +00:00
|
|
|
config DEBUG_IMX53_UART
|
|
|
|
|
bool "i.MX53 Debug UART"
|
|
|
|
|
depends on SOC_IMX53
|
2011-08-19 04:56:59 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
2013-01-22 12:40:55 +00:00
|
|
|
on i.MX53.
|
2011-08-19 04:56:59 +00:00
|
|
|
|
2012-10-08 05:44:29 +00:00
|
|
|
config DEBUG_IMX6Q_UART
|
2013-04-01 14:13:32 +00:00
|
|
|
bool "i.MX6Q/DL Debug UART"
|
2012-04-27 08:15:45 +00:00
|
|
|
depends on SOC_IMX6Q
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
2013-04-01 14:13:32 +00:00
|
|
|
on i.MX6Q/DL.
|
2011-10-02 07:09:11 +00:00
|
|
|
|
2013-05-03 03:21:03 +00:00
|
|
|
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.
|
|
|
|
|
|
2014-05-11 13:53:48 +00:00
|
|
|
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.
|
|
|
|
|
|
2015-07-09 18:09:47 +00:00
|
|
|
config DEBUG_IMX6UL_UART
|
|
|
|
|
bool "i.MX6UL Debug UART"
|
|
|
|
|
depends on SOC_IMX6UL
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on i.MX6UL.
|
|
|
|
|
|
2015-05-06 15:16:07 +00:00
|
|
|
config DEBUG_IMX7D_UART
|
|
|
|
|
bool "i.MX7D Debug UART"
|
|
|
|
|
depends on SOC_IMX7D
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on i.MX7D.
|
|
|
|
|
|
2015-12-03 16:54:05 +00:00
|
|
|
config DEBUG_INTEGRATOR
|
|
|
|
|
bool "Kernel low-level debugging messages via ARM Integrator UART"
|
|
|
|
|
depends on ARCH_INTEGRATOR
|
|
|
|
|
select DEBUG_UART_PL01X
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on ARM Integrator platforms.
|
|
|
|
|
|
2013-06-10 15:27:13 +00:00
|
|
|
config DEBUG_KEYSTONE_UART0
|
|
|
|
|
bool "Kernel low-level debugging on KEYSTONE2 using UART0"
|
|
|
|
|
depends on ARCH_KEYSTONE
|
2013-07-07 15:05:49 +00:00
|
|
|
select DEBUG_UART_8250
|
2013-06-10 15:27:13 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want the debug print routines to direct
|
|
|
|
|
their output to UART0 serial port on KEYSTONE2 devices.
|
|
|
|
|
|
|
|
|
|
config DEBUG_KEYSTONE_UART1
|
|
|
|
|
bool "Kernel low-level debugging on KEYSTONE2 using UART1"
|
|
|
|
|
depends on ARCH_KEYSTONE
|
2013-07-07 15:05:49 +00:00
|
|
|
select DEBUG_UART_8250
|
2013-06-10 15:27:13 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want the debug print routines to direct
|
|
|
|
|
their output to UART1 serial port on KEYSTONE2 devices.
|
|
|
|
|
|
2015-05-19 18:55:03 +00:00
|
|
|
config DEBUG_LPC18XX_UART0
|
|
|
|
|
bool "Kernel low-level debugging via LPC18xx/43xx UART0"
|
|
|
|
|
depends on ARCH_LPC18XX
|
|
|
|
|
select DEBUG_UART_8250
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on NXP LPC18xx/43xx UART0.
|
|
|
|
|
|
2015-12-03 16:54:05 +00:00
|
|
|
config DEBUG_LPC32XX
|
|
|
|
|
bool "Kernel low-level debugging messages via NXP LPC32xx UART"
|
|
|
|
|
depends on ARCH_LPC32XX
|
|
|
|
|
select DEBUG_UART_8250
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on NXP LPC32xx based platforms.
|
|
|
|
|
|
2014-09-09 19:38:00 +00:00
|
|
|
config DEBUG_MESON_UARTAO
|
|
|
|
|
bool "Kernel low-level debugging via Meson6 UARTAO"
|
|
|
|
|
depends on ARCH_MESON
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-lever debugging support
|
|
|
|
|
on Amlogic Meson6 based platforms on the UARTAO.
|
|
|
|
|
|
2012-08-10 15:49:41 +00:00
|
|
|
config DEBUG_MMP_UART2
|
|
|
|
|
bool "Kernel low-level debugging message via MMP UART2"
|
|
|
|
|
depends on ARCH_MMP
|
2013-07-06 22:13:15 +00:00
|
|
|
select DEBUG_UART_8250
|
2012-08-10 15:49:41 +00:00
|
|
|
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
|
2013-07-06 22:13:15 +00:00
|
|
|
select DEBUG_UART_8250
|
2012-08-10 15:49:41 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on MMP UART3.
|
|
|
|
|
|
2015-01-08 17:38:03 +00:00
|
|
|
config DEBUG_MVEBU_UART0
|
|
|
|
|
bool "Kernel low-level debugging messages via MVEBU UART0 (old bootloaders)"
|
2012-09-02 19:41:34 +00:00
|
|
|
depends on ARCH_MVEBU
|
2015-12-03 13:48:23 +00:00
|
|
|
depends on ARCH_MVEBU && CPU_V7
|
2013-07-06 22:13:15 +00:00
|
|
|
select DEBUG_UART_8250
|
2012-09-02 19:41:34 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
2015-01-08 17:38:03 +00:00
|
|
|
on MVEBU based platforms on UART0.
|
2012-09-02 19:41:34 +00:00
|
|
|
|
2013-06-05 07:05:00 +00:00
|
|
|
This option should be used with the old bootloaders
|
|
|
|
|
that left the internal registers mapped at
|
|
|
|
|
0xd0000000. As of today, this is the case on
|
|
|
|
|
platforms such as the Globalscale Mirabox or the
|
|
|
|
|
Plathome OpenBlocks AX3, when using the original
|
|
|
|
|
bootloader.
|
|
|
|
|
|
2015-12-03 13:48:23 +00:00
|
|
|
This option will not work on older Marvell platforms
|
|
|
|
|
(Kirkwood, Dove, MV78xx0, Orion5x), which should pick
|
|
|
|
|
the "new bootloader" variant.
|
|
|
|
|
|
2013-06-05 07:05:00 +00:00
|
|
|
If the wrong DEBUG_MVEBU_UART* option is selected,
|
|
|
|
|
when u-boot hands over to the kernel, the system
|
|
|
|
|
silently crashes, with no serial output at all.
|
|
|
|
|
|
2015-01-08 17:38:03 +00:00
|
|
|
config DEBUG_MVEBU_UART0_ALTERNATE
|
|
|
|
|
bool "Kernel low-level debugging messages via MVEBU UART0 (new bootloaders)"
|
2015-12-03 13:48:23 +00:00
|
|
|
depends on ARCH_MVEBU || ARCH_DOVE || ARCH_MV78XX0 || ARCH_ORION5X
|
2013-07-06 22:13:15 +00:00
|
|
|
select DEBUG_UART_8250
|
2013-06-05 07:05:00 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
2015-12-03 13:48:23 +00:00
|
|
|
on MVEBU based platforms on UART0. (Armada XP, Armada 3xx,
|
|
|
|
|
Kirkwood, Dove, MV78xx0, Orion5x).
|
|
|
|
|
|
2013-06-05 07:05:00 +00:00
|
|
|
|
|
|
|
|
This option should be used with the new bootloaders
|
|
|
|
|
that remap the internal registers at 0xf1000000.
|
|
|
|
|
|
|
|
|
|
If the wrong DEBUG_MVEBU_UART* option is selected,
|
|
|
|
|
when u-boot hands over to the kernel, the system
|
|
|
|
|
silently crashes, with no serial output at all.
|
|
|
|
|
|
2015-01-08 17:38:04 +00:00
|
|
|
config DEBUG_MVEBU_UART1_ALTERNATE
|
|
|
|
|
bool "Kernel low-level debugging messages via MVEBU UART1 (new bootloaders)"
|
2013-06-05 07:05:00 +00:00
|
|
|
depends on ARCH_MVEBU
|
2013-07-06 22:13:15 +00:00
|
|
|
select DEBUG_UART_8250
|
2013-06-05 07:05:00 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
2015-12-03 13:48:23 +00:00
|
|
|
on MVEBU based platforms on UART1. (Armada XP, Armada 3xx,
|
|
|
|
|
Kirkwood, Dove, MV78xx0, Orion5x).
|
2013-06-05 07:05:00 +00:00
|
|
|
|
|
|
|
|
This option should be used with the new bootloaders
|
|
|
|
|
that remap the internal registers at 0xf1000000.
|
2015-12-03 13:48:23 +00:00
|
|
|
All of the older (pre Armada XP/370) platforms also use
|
|
|
|
|
this address, regardless of the boot loader version.
|
2013-06-05 07:05:00 +00:00
|
|
|
|
|
|
|
|
If the wrong DEBUG_MVEBU_UART* option is selected,
|
|
|
|
|
when u-boot hands over to the kernel, the system
|
|
|
|
|
silently crashes, with no serial output at all.
|
|
|
|
|
|
2021-05-04 17:03:16 +00:00
|
|
|
config DEBUG_MSTARV7_PMUART
|
|
|
|
|
bool "Kernel low-level debugging messages via MSTARV7 PM UART"
|
|
|
|
|
depends on ARCH_MSTARV7
|
|
|
|
|
select DEBUG_UART_8250
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
for MSTAR ARMv7-based platforms on PM UART.
|
|
|
|
|
|
2015-12-03 17:16:45 +00:00
|
|
|
config DEBUG_MT6589_UART0
|
|
|
|
|
bool "Mediatek mt6589 UART0"
|
|
|
|
|
depends on ARCH_MEDIATEK
|
|
|
|
|
select DEBUG_UART_8250
|
2013-05-12 09:22:17 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
2015-12-03 17:16:45 +00:00
|
|
|
for Mediatek mt6589 based platforms on UART0.
|
|
|
|
|
|
|
|
|
|
config DEBUG_MT8127_UART0
|
|
|
|
|
bool "Mediatek mt8127/mt6592 UART0"
|
|
|
|
|
depends on ARCH_MEDIATEK
|
|
|
|
|
select DEBUG_UART_8250
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
for Mediatek mt8127 based platforms on UART0.
|
|
|
|
|
|
|
|
|
|
config DEBUG_MT8135_UART3
|
|
|
|
|
bool "Mediatek mt8135 UART3"
|
|
|
|
|
depends on ARCH_MEDIATEK
|
|
|
|
|
select DEBUG_UART_8250
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
for Mediatek mt8135 based platforms on UART3.
|
2013-05-12 09:22:17 +00:00
|
|
|
|
2013-02-27 21:39:57 +00:00
|
|
|
config DEBUG_NOMADIK_UART
|
|
|
|
|
bool "Kernel low-level debugging messages via NOMADIK UART"
|
|
|
|
|
depends on ARCH_NOMADIK
|
2013-07-07 11:32:16 +00:00
|
|
|
select DEBUG_UART_PL01X
|
2013-02-27 21:39:57 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on NOMADIK based platforms.
|
|
|
|
|
|
2013-06-11 08:40:17 +00:00
|
|
|
config DEBUG_NSPIRE_CLASSIC_UART
|
|
|
|
|
bool "Kernel low-level debugging via TI-NSPIRE 8250 UART"
|
|
|
|
|
depends on ARCH_NSPIRE
|
2013-07-06 22:13:15 +00:00
|
|
|
select DEBUG_UART_8250
|
2013-06-11 08:40:17 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on TI-NSPIRE classic models.
|
|
|
|
|
|
|
|
|
|
config DEBUG_NSPIRE_CX_UART
|
|
|
|
|
bool "Kernel low-level debugging via TI-NSPIRE PL011 UART"
|
|
|
|
|
depends on ARCH_NSPIRE
|
2013-07-07 11:32:16 +00:00
|
|
|
select DEBUG_UART_PL01X
|
2013-06-11 08:40:17 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on TI-NSPIRE CX models.
|
|
|
|
|
|
2015-01-09 17:33:50 +00:00
|
|
|
config DEBUG_OMAP1UART1
|
|
|
|
|
bool "Kernel low-level debugging via OMAP1 UART1"
|
|
|
|
|
depends on ARCH_OMAP1
|
|
|
|
|
select DEBUG_UART_8250
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on OMAP1 based platforms (except OMAP730) on the UART1.
|
|
|
|
|
|
|
|
|
|
config DEBUG_OMAP1UART2
|
|
|
|
|
bool "Kernel low-level debugging via OMAP1 UART2"
|
|
|
|
|
depends on ARCH_OMAP1
|
|
|
|
|
select DEBUG_UART_8250
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on OMAP1 based platforms (except OMAP730) on the UART2.
|
|
|
|
|
|
|
|
|
|
config DEBUG_OMAP1UART3
|
|
|
|
|
bool "Kernel low-level debugging via OMAP1 UART3"
|
|
|
|
|
depends on ARCH_OMAP1
|
|
|
|
|
select DEBUG_UART_8250
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on OMAP1 based platforms (except OMAP730) on the UART3.
|
|
|
|
|
|
2013-07-06 13:23:30 +00:00
|
|
|
config DEBUG_OMAP2UART1
|
|
|
|
|
bool "OMAP2/3/4 UART1 (omap2/3 sdp boards and some omap3 boards)"
|
2013-01-11 19:24:19 +00:00
|
|
|
depends on ARCH_OMAP2PLUS
|
2017-07-17 05:10:13 +00:00
|
|
|
select DEBUG_UART_8250
|
2013-01-11 19:24:19 +00:00
|
|
|
help
|
2013-07-06 13:23:30 +00:00
|
|
|
This covers at least h4, 2430sdp, 3430sdp, 3630sdp,
|
|
|
|
|
omap3 torpedo and 3530 lv som.
|
|
|
|
|
|
|
|
|
|
config DEBUG_OMAP2UART2
|
|
|
|
|
bool "Kernel low-level debugging messages via OMAP2/3/4 UART2"
|
|
|
|
|
depends on ARCH_OMAP2PLUS
|
2017-07-17 05:10:13 +00:00
|
|
|
select DEBUG_UART_8250
|
2013-07-06 13:23:30 +00:00
|
|
|
|
|
|
|
|
config DEBUG_OMAP2UART3
|
|
|
|
|
bool "Kernel low-level debugging messages via OMAP2 UART3 (n8x0)"
|
|
|
|
|
depends on ARCH_OMAP2PLUS
|
2017-07-17 05:10:13 +00:00
|
|
|
select DEBUG_UART_8250
|
2013-07-06 13:23:30 +00:00
|
|
|
|
|
|
|
|
config DEBUG_OMAP3UART3
|
|
|
|
|
bool "Kernel low-level debugging messages via OMAP3 UART3 (most omap3 boards)"
|
|
|
|
|
depends on ARCH_OMAP2PLUS
|
2017-06-14 07:31:13 +00:00
|
|
|
select DEBUG_UART_8250
|
2013-07-06 13:23:30 +00:00
|
|
|
help
|
|
|
|
|
This covers at least cm_t3x, beagle, crane, devkit8000,
|
|
|
|
|
igep00x0, ldp, n900, n9(50), pandora, overo, touchbook,
|
|
|
|
|
and 3517evm.
|
|
|
|
|
|
|
|
|
|
config DEBUG_OMAP4UART3
|
|
|
|
|
bool "Kernel low-level debugging messages via OMAP4/5 UART3 (omap4 blaze, panda, omap5 sevm)"
|
|
|
|
|
depends on ARCH_OMAP2PLUS
|
2017-06-14 07:31:13 +00:00
|
|
|
select DEBUG_UART_8250
|
2013-07-06 13:23:30 +00:00
|
|
|
|
|
|
|
|
config DEBUG_OMAP3UART4
|
|
|
|
|
bool "Kernel low-level debugging messages via OMAP36XX UART4"
|
|
|
|
|
depends on ARCH_OMAP2PLUS
|
2017-06-14 07:31:13 +00:00
|
|
|
select DEBUG_UART_8250
|
2013-07-06 13:23:30 +00:00
|
|
|
|
|
|
|
|
config DEBUG_OMAP4UART4
|
|
|
|
|
bool "Kernel low-level debugging messages via OMAP4/5 UART4"
|
|
|
|
|
depends on ARCH_OMAP2PLUS
|
2017-06-14 07:31:13 +00:00
|
|
|
select DEBUG_UART_8250
|
2013-07-06 13:23:30 +00:00
|
|
|
|
|
|
|
|
config DEBUG_TI81XXUART1
|
|
|
|
|
bool "Kernel low-level debugging messages via TI81XX UART1 (ti8148evm)"
|
|
|
|
|
depends on ARCH_OMAP2PLUS
|
2017-07-17 05:10:14 +00:00
|
|
|
select DEBUG_UART_8250
|
2013-07-06 13:23:30 +00:00
|
|
|
|
|
|
|
|
config DEBUG_TI81XXUART2
|
|
|
|
|
bool "Kernel low-level debugging messages via TI81XX UART2"
|
|
|
|
|
depends on ARCH_OMAP2PLUS
|
2017-07-17 05:10:14 +00:00
|
|
|
select DEBUG_UART_8250
|
2013-07-06 13:23:30 +00:00
|
|
|
|
|
|
|
|
config DEBUG_TI81XXUART3
|
|
|
|
|
bool "Kernel low-level debugging messages via TI81XX UART3 (ti8168evm)"
|
|
|
|
|
depends on ARCH_OMAP2PLUS
|
2017-07-17 05:10:14 +00:00
|
|
|
select DEBUG_UART_8250
|
2013-07-06 13:23:30 +00:00
|
|
|
|
|
|
|
|
config DEBUG_AM33XXUART1
|
|
|
|
|
bool "Kernel low-level debugging messages via AM33XX UART1"
|
|
|
|
|
depends on ARCH_OMAP2PLUS
|
2017-07-17 05:10:14 +00:00
|
|
|
select DEBUG_UART_8250
|
2013-07-06 13:23:30 +00:00
|
|
|
|
|
|
|
|
config DEBUG_ZOOM_UART
|
|
|
|
|
bool "Kernel low-level debugging messages via Zoom2/3 UART"
|
|
|
|
|
depends on ARCH_OMAP2PLUS
|
|
|
|
|
select DEBUG_OMAP2PLUS_UART
|
2013-01-11 19:24:19 +00:00
|
|
|
|
2013-04-10 03:17:04 +00:00
|
|
|
config DEBUG_PXA_UART1
|
|
|
|
|
depends on ARCH_PXA
|
|
|
|
|
bool "Use PXA UART1 for low-level debug"
|
2013-07-06 22:13:15 +00:00
|
|
|
select DEBUG_UART_8250
|
2013-04-10 03:17:04 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on PXA UART1.
|
|
|
|
|
|
2015-12-03 17:16:45 +00:00
|
|
|
config DEBUG_QCOM_UARTDM
|
|
|
|
|
bool "Kernel low-level debugging messages via QCOM UARTDM"
|
|
|
|
|
depends on ARCH_QCOM
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want the debug print routines to direct
|
|
|
|
|
their output to the serial port on Qualcomm devices.
|
|
|
|
|
|
|
|
|
|
ARCH DEBUG_UART_PHYS DEBUG_UART_VIRT
|
|
|
|
|
APQ8064 0x16640000 0xf0040000
|
|
|
|
|
APQ8084 0xf995e000 0xfa75e000
|
2017-03-27 23:11:40 +00:00
|
|
|
IPQ4019 0x078af000 0xf78af000
|
2015-12-03 17:16:45 +00:00
|
|
|
MSM8X60 0x19c40000 0xf0040000
|
|
|
|
|
MSM8960 0x16440000 0xf0040000
|
|
|
|
|
MSM8974 0xf991e000 0xfa71e000
|
|
|
|
|
|
|
|
|
|
Please adjust DEBUG_UART_PHYS and DEBUG_UART_BASE configuration
|
|
|
|
|
options based on your needs.
|
|
|
|
|
|
2011-08-16 21:30:28 +00:00
|
|
|
config DEBUG_REALVIEW_STD_PORT
|
|
|
|
|
bool "RealView Default UART"
|
|
|
|
|
depends on ARCH_REALVIEW
|
2013-07-07 11:32:16 +00:00
|
|
|
select DEBUG_UART_PL01X
|
2011-08-16 21:30:28 +00:00
|
|
|
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
|
2013-07-07 11:32:16 +00:00
|
|
|
select DEBUG_UART_PL01X
|
2011-08-16 21:30:28 +00:00
|
|
|
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.
|
|
|
|
|
|
2016-11-14 12:12:35 +00:00
|
|
|
config DEBUG_RV1108_UART0
|
|
|
|
|
bool "Kernel low-level debugging messages via Rockchip RV1108 UART0"
|
|
|
|
|
depends on ARCH_ROCKCHIP
|
|
|
|
|
select DEBUG_UART_8250
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on Rockchip RV1108 based platforms.
|
|
|
|
|
|
|
|
|
|
config DEBUG_RV1108_UART1
|
|
|
|
|
bool "Kernel low-level debugging messages via Rockchip RV1108 UART1"
|
|
|
|
|
depends on ARCH_ROCKCHIP
|
|
|
|
|
select DEBUG_UART_8250
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on Rockchip RV1108 based platforms.
|
|
|
|
|
|
|
|
|
|
config DEBUG_RV1108_UART2
|
|
|
|
|
bool "Kernel low-level debugging messages via Rockchip RV1108 UART2"
|
|
|
|
|
depends on ARCH_ROCKCHIP
|
|
|
|
|
select DEBUG_UART_8250
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on Rockchip RV1108 based platforms.
|
|
|
|
|
|
2013-07-06 13:23:30 +00:00
|
|
|
config DEBUG_RK29_UART0
|
|
|
|
|
bool "Kernel low-level debugging messages via Rockchip RK29 UART0"
|
|
|
|
|
depends on ARCH_ROCKCHIP
|
2013-07-06 22:13:15 +00:00
|
|
|
select DEBUG_UART_8250
|
2013-07-06 13:23:30 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on Rockchip based platforms.
|
|
|
|
|
|
|
|
|
|
config DEBUG_RK29_UART1
|
|
|
|
|
bool "Kernel low-level debugging messages via Rockchip RK29 UART1"
|
|
|
|
|
depends on ARCH_ROCKCHIP
|
2013-07-06 22:13:15 +00:00
|
|
|
select DEBUG_UART_8250
|
2013-07-06 13:23:30 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on Rockchip based platforms.
|
|
|
|
|
|
|
|
|
|
config DEBUG_RK29_UART2
|
|
|
|
|
bool "Kernel low-level debugging messages via Rockchip RK29 UART2"
|
|
|
|
|
depends on ARCH_ROCKCHIP
|
2013-07-06 22:13:15 +00:00
|
|
|
select DEBUG_UART_8250
|
2013-07-06 13:23:30 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on Rockchip based platforms.
|
|
|
|
|
|
|
|
|
|
config DEBUG_RK3X_UART0
|
2014-07-16 15:08:14 +00:00
|
|
|
bool "Kernel low-level debugging messages via Rockchip RK30/RK31 UART0"
|
2013-07-06 13:23:30 +00:00
|
|
|
depends on ARCH_ROCKCHIP
|
2013-07-06 22:13:15 +00:00
|
|
|
select DEBUG_UART_8250
|
2013-07-06 13:23:30 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on Rockchip based platforms.
|
|
|
|
|
|
|
|
|
|
config DEBUG_RK3X_UART1
|
2014-07-16 15:08:14 +00:00
|
|
|
bool "Kernel low-level debugging messages via Rockchip RK30/RK31 UART1"
|
2013-05-28 20:13:52 +00:00
|
|
|
depends on ARCH_ROCKCHIP
|
2013-07-06 22:13:15 +00:00
|
|
|
select DEBUG_UART_8250
|
2013-07-06 13:23:30 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on Rockchip based platforms.
|
|
|
|
|
|
|
|
|
|
config DEBUG_RK3X_UART2
|
2014-07-16 15:08:14 +00:00
|
|
|
bool "Kernel low-level debugging messages via Rockchip RK30/RK31 UART2"
|
2013-07-06 13:23:30 +00:00
|
|
|
depends on ARCH_ROCKCHIP
|
2013-07-06 22:13:15 +00:00
|
|
|
select DEBUG_UART_8250
|
2013-07-06 13:23:30 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on Rockchip based platforms.
|
|
|
|
|
|
|
|
|
|
config DEBUG_RK3X_UART3
|
2014-07-16 15:08:14 +00:00
|
|
|
bool "Kernel low-level debugging messages via Rockchip RK30/RK31 UART3"
|
2013-07-06 13:23:30 +00:00
|
|
|
depends on ARCH_ROCKCHIP
|
2013-07-06 22:13:15 +00:00
|
|
|
select DEBUG_UART_8250
|
2013-05-28 20:13:52 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on Rockchip based platforms.
|
|
|
|
|
|
2014-06-28 11:31:17 +00:00
|
|
|
config DEBUG_RK32_UART2
|
|
|
|
|
bool "Kernel low-level debugging messages via Rockchip RK32 UART2"
|
|
|
|
|
depends on ARCH_ROCKCHIP
|
|
|
|
|
select DEBUG_UART_8250
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on Rockchip RK32xx based platforms.
|
|
|
|
|
|
ARM: shmobile: Add early debugging support using SCIF(A)
Add serial port debug macros for the SCIF(A) serial ports.
This includes all supported shmobile SoCs, except for EMEV2.
The configuration logic (both Kconfig and #ifdef) is more complicated than
one would expect, for several reasons:
1. Not all SoCs have the same serial devices, and they're not always
at the same addresses.
2. There are two different types: SCIF and SCIFA. Fortunately they can
easily be distinguished by physical address.
3. Not all boards use the same serial port for the console.
The defaults correspond to the boards that are supported in
mainline. If you want to use a different serial port, just change
the value of CONFIG_DEBUG_UART_PHYS, and the rest will auto-adapt.
4. debug_ll_io_init() maps the SCIF(A) registers to a fixed virtual
address. 0xfdxxxxxx was chosen, as it should lie below VMALLOC_END
= 0xff000000, and must not conflict with the 2 MiB reserved region
at PCI_IO_VIRT_BASE = 0xfee00000.
- On SoCs not using the legacy machine_desc.map_io(),
debug_ll_io_init() is called by the ARM core code.
- On SoCs using the legacy machine_desc.map_io(),
debug_ll_io_init() must be called explicitly. Calls are added
for r8a7740, r8a7779, sh7372, and sh73a0.
This was derived from the r8a7790 version by Laurent Pinchart.
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Tested-by: Simon Horman <horms+renesas@verge.net.au>
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
2014-11-14 15:49:47 +00:00
|
|
|
config DEBUG_R7S72100_SCIF2
|
|
|
|
|
bool "Kernel low-level debugging messages via SCIF2 on R7S72100"
|
|
|
|
|
depends on ARCH_R7S72100
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
via SCIF2 on Renesas RZ/A1H (R7S72100).
|
|
|
|
|
|
2019-06-03 07:37:19 +00:00
|
|
|
config DEBUG_R7S9210_SCIF2
|
|
|
|
|
bool "Kernel low-level debugging messages via SCIF2 on R7S9210"
|
|
|
|
|
depends on ARCH_R7S9210
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
via SCIF2 on Renesas RZ/A2M (R7S9210).
|
|
|
|
|
|
|
|
|
|
config DEBUG_R7S9210_SCIF4
|
|
|
|
|
bool "Kernel low-level debugging messages via SCIF4 on R7S9210"
|
|
|
|
|
depends on ARCH_R7S9210
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
via SCIF4 on Renesas RZ/A2M (R7S9210).
|
|
|
|
|
|
ARM: shmobile: Add early debugging support using SCIF(A)
Add serial port debug macros for the SCIF(A) serial ports.
This includes all supported shmobile SoCs, except for EMEV2.
The configuration logic (both Kconfig and #ifdef) is more complicated than
one would expect, for several reasons:
1. Not all SoCs have the same serial devices, and they're not always
at the same addresses.
2. There are two different types: SCIF and SCIFA. Fortunately they can
easily be distinguished by physical address.
3. Not all boards use the same serial port for the console.
The defaults correspond to the boards that are supported in
mainline. If you want to use a different serial port, just change
the value of CONFIG_DEBUG_UART_PHYS, and the rest will auto-adapt.
4. debug_ll_io_init() maps the SCIF(A) registers to a fixed virtual
address. 0xfdxxxxxx was chosen, as it should lie below VMALLOC_END
= 0xff000000, and must not conflict with the 2 MiB reserved region
at PCI_IO_VIRT_BASE = 0xfee00000.
- On SoCs not using the legacy machine_desc.map_io(),
debug_ll_io_init() is called by the ARM core code.
- On SoCs using the legacy machine_desc.map_io(),
debug_ll_io_init() must be called explicitly. Calls are added
for r8a7740, r8a7779, sh7372, and sh73a0.
This was derived from the r8a7790 version by Laurent Pinchart.
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Tested-by: Simon Horman <horms+renesas@verge.net.au>
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
2014-11-14 15:49:47 +00:00
|
|
|
config DEBUG_RCAR_GEN1_SCIF0
|
|
|
|
|
bool "Kernel low-level debugging messages via SCIF0 on R8A7778"
|
|
|
|
|
depends on ARCH_R8A7778
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
via SCIF0 on Renesas R-Car M1A (R8A7778).
|
|
|
|
|
|
|
|
|
|
config DEBUG_RCAR_GEN1_SCIF2
|
|
|
|
|
bool "Kernel low-level debugging messages via SCIF2 on R8A7779"
|
|
|
|
|
depends on ARCH_R8A7779
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
via SCIF2 on Renesas R-Car H1 (R8A7779).
|
|
|
|
|
|
|
|
|
|
config DEBUG_RCAR_GEN2_SCIF0
|
2017-06-08 10:08:14 +00:00
|
|
|
bool "Kernel low-level debugging messages via SCIF0 on R-Car Gen2 and RZ/G1"
|
2018-09-17 15:06:30 +00:00
|
|
|
depends on ARCH_R8A7743 || ARCH_R8A7744 || ARCH_R8A7790 || \
|
|
|
|
|
ARCH_R8A7791 || ARCH_R8A7792 || ARCH_R8A7793
|
ARM: shmobile: Add early debugging support using SCIF(A)
Add serial port debug macros for the SCIF(A) serial ports.
This includes all supported shmobile SoCs, except for EMEV2.
The configuration logic (both Kconfig and #ifdef) is more complicated than
one would expect, for several reasons:
1. Not all SoCs have the same serial devices, and they're not always
at the same addresses.
2. There are two different types: SCIF and SCIFA. Fortunately they can
easily be distinguished by physical address.
3. Not all boards use the same serial port for the console.
The defaults correspond to the boards that are supported in
mainline. If you want to use a different serial port, just change
the value of CONFIG_DEBUG_UART_PHYS, and the rest will auto-adapt.
4. debug_ll_io_init() maps the SCIF(A) registers to a fixed virtual
address. 0xfdxxxxxx was chosen, as it should lie below VMALLOC_END
= 0xff000000, and must not conflict with the 2 MiB reserved region
at PCI_IO_VIRT_BASE = 0xfee00000.
- On SoCs not using the legacy machine_desc.map_io(),
debug_ll_io_init() is called by the ARM core code.
- On SoCs using the legacy machine_desc.map_io(),
debug_ll_io_init() must be called explicitly. Calls are added
for r8a7740, r8a7779, sh7372, and sh73a0.
This was derived from the r8a7790 version by Laurent Pinchart.
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Tested-by: Simon Horman <horms+renesas@verge.net.au>
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
2014-11-14 15:49:47 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
2018-09-17 15:06:30 +00:00
|
|
|
via SCIF0 on Renesas RZ/G1M (R8A7743), RZ/G1N (R8A7744),
|
|
|
|
|
R-Car H2 (R8A7790), M2-W (R8A7791), V2H (R8A7792), or
|
|
|
|
|
M2-N (R8A7793).
|
ARM: shmobile: Add early debugging support using SCIF(A)
Add serial port debug macros for the SCIF(A) serial ports.
This includes all supported shmobile SoCs, except for EMEV2.
The configuration logic (both Kconfig and #ifdef) is more complicated than
one would expect, for several reasons:
1. Not all SoCs have the same serial devices, and they're not always
at the same addresses.
2. There are two different types: SCIF and SCIFA. Fortunately they can
easily be distinguished by physical address.
3. Not all boards use the same serial port for the console.
The defaults correspond to the boards that are supported in
mainline. If you want to use a different serial port, just change
the value of CONFIG_DEBUG_UART_PHYS, and the rest will auto-adapt.
4. debug_ll_io_init() maps the SCIF(A) registers to a fixed virtual
address. 0xfdxxxxxx was chosen, as it should lie below VMALLOC_END
= 0xff000000, and must not conflict with the 2 MiB reserved region
at PCI_IO_VIRT_BASE = 0xfee00000.
- On SoCs not using the legacy machine_desc.map_io(),
debug_ll_io_init() is called by the ARM core code.
- On SoCs using the legacy machine_desc.map_io(),
debug_ll_io_init() must be called explicitly. Calls are added
for r8a7740, r8a7779, sh7372, and sh73a0.
This was derived from the r8a7790 version by Laurent Pinchart.
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Tested-by: Simon Horman <horms+renesas@verge.net.au>
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
2014-11-14 15:49:47 +00:00
|
|
|
|
2018-03-29 10:42:26 +00:00
|
|
|
config DEBUG_RCAR_GEN2_SCIF1
|
|
|
|
|
bool "Kernel low-level debugging messages via SCIF1 on R8A77470"
|
|
|
|
|
depends on ARCH_R8A77470
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
via SCIF1 on Renesas RZ/G1C (R8A77470).
|
|
|
|
|
|
ARM: shmobile: Add early debugging support using SCIF(A)
Add serial port debug macros for the SCIF(A) serial ports.
This includes all supported shmobile SoCs, except for EMEV2.
The configuration logic (both Kconfig and #ifdef) is more complicated than
one would expect, for several reasons:
1. Not all SoCs have the same serial devices, and they're not always
at the same addresses.
2. There are two different types: SCIF and SCIFA. Fortunately they can
easily be distinguished by physical address.
3. Not all boards use the same serial port for the console.
The defaults correspond to the boards that are supported in
mainline. If you want to use a different serial port, just change
the value of CONFIG_DEBUG_UART_PHYS, and the rest will auto-adapt.
4. debug_ll_io_init() maps the SCIF(A) registers to a fixed virtual
address. 0xfdxxxxxx was chosen, as it should lie below VMALLOC_END
= 0xff000000, and must not conflict with the 2 MiB reserved region
at PCI_IO_VIRT_BASE = 0xfee00000.
- On SoCs not using the legacy machine_desc.map_io(),
debug_ll_io_init() is called by the ARM core code.
- On SoCs using the legacy machine_desc.map_io(),
debug_ll_io_init() must be called explicitly. Calls are added
for r8a7740, r8a7779, sh7372, and sh73a0.
This was derived from the r8a7790 version by Laurent Pinchart.
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Tested-by: Simon Horman <horms+renesas@verge.net.au>
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
2014-11-14 15:49:47 +00:00
|
|
|
config DEBUG_RCAR_GEN2_SCIF2
|
|
|
|
|
bool "Kernel low-level debugging messages via SCIF2 on R8A7794"
|
|
|
|
|
depends on ARCH_R8A7794
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
via SCIF2 on Renesas R-Car E2 (R8A7794).
|
|
|
|
|
|
2017-08-16 10:20:10 +00:00
|
|
|
config DEBUG_RCAR_GEN2_SCIF4
|
|
|
|
|
bool "Kernel low-level debugging messages via SCIF4 on R8A7745"
|
|
|
|
|
depends on ARCH_R8A7745
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
via SCIF4 on Renesas RZ/G1E (R8A7745).
|
|
|
|
|
|
2020-04-29 21:56:41 +00:00
|
|
|
config DEBUG_RCAR_GEN2_SCIFA2
|
|
|
|
|
bool "Kernel low-level debugging messages via SCIFA2 on R8A7742"
|
|
|
|
|
depends on ARCH_R8A7742
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
via SCIFA2 on Renesas RZ/G1H (R8A7742).
|
|
|
|
|
|
ARM: shmobile: Add early debugging support using SCIF(A)
Add serial port debug macros for the SCIF(A) serial ports.
This includes all supported shmobile SoCs, except for EMEV2.
The configuration logic (both Kconfig and #ifdef) is more complicated than
one would expect, for several reasons:
1. Not all SoCs have the same serial devices, and they're not always
at the same addresses.
2. There are two different types: SCIF and SCIFA. Fortunately they can
easily be distinguished by physical address.
3. Not all boards use the same serial port for the console.
The defaults correspond to the boards that are supported in
mainline. If you want to use a different serial port, just change
the value of CONFIG_DEBUG_UART_PHYS, and the rest will auto-adapt.
4. debug_ll_io_init() maps the SCIF(A) registers to a fixed virtual
address. 0xfdxxxxxx was chosen, as it should lie below VMALLOC_END
= 0xff000000, and must not conflict with the 2 MiB reserved region
at PCI_IO_VIRT_BASE = 0xfee00000.
- On SoCs not using the legacy machine_desc.map_io(),
debug_ll_io_init() is called by the ARM core code.
- On SoCs using the legacy machine_desc.map_io(),
debug_ll_io_init() must be called explicitly. Calls are added
for r8a7740, r8a7779, sh7372, and sh73a0.
This was derived from the r8a7790 version by Laurent Pinchart.
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Tested-by: Simon Horman <horms+renesas@verge.net.au>
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
2014-11-14 15:49:47 +00:00
|
|
|
config DEBUG_RMOBILE_SCIFA0
|
2015-01-26 06:19:20 +00:00
|
|
|
bool "Kernel low-level debugging messages via SCIFA0 on R8A73A4"
|
|
|
|
|
depends on ARCH_R8A73A4
|
ARM: shmobile: Add early debugging support using SCIF(A)
Add serial port debug macros for the SCIF(A) serial ports.
This includes all supported shmobile SoCs, except for EMEV2.
The configuration logic (both Kconfig and #ifdef) is more complicated than
one would expect, for several reasons:
1. Not all SoCs have the same serial devices, and they're not always
at the same addresses.
2. There are two different types: SCIF and SCIFA. Fortunately they can
easily be distinguished by physical address.
3. Not all boards use the same serial port for the console.
The defaults correspond to the boards that are supported in
mainline. If you want to use a different serial port, just change
the value of CONFIG_DEBUG_UART_PHYS, and the rest will auto-adapt.
4. debug_ll_io_init() maps the SCIF(A) registers to a fixed virtual
address. 0xfdxxxxxx was chosen, as it should lie below VMALLOC_END
= 0xff000000, and must not conflict with the 2 MiB reserved region
at PCI_IO_VIRT_BASE = 0xfee00000.
- On SoCs not using the legacy machine_desc.map_io(),
debug_ll_io_init() is called by the ARM core code.
- On SoCs using the legacy machine_desc.map_io(),
debug_ll_io_init() must be called explicitly. Calls are added
for r8a7740, r8a7779, sh7372, and sh73a0.
This was derived from the r8a7790 version by Laurent Pinchart.
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Tested-by: Simon Horman <horms+renesas@verge.net.au>
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
2014-11-14 15:49:47 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
2015-01-26 06:19:20 +00:00
|
|
|
via SCIFA0 on Renesas R-Mobile APE6 (R8A73A4).
|
ARM: shmobile: Add early debugging support using SCIF(A)
Add serial port debug macros for the SCIF(A) serial ports.
This includes all supported shmobile SoCs, except for EMEV2.
The configuration logic (both Kconfig and #ifdef) is more complicated than
one would expect, for several reasons:
1. Not all SoCs have the same serial devices, and they're not always
at the same addresses.
2. There are two different types: SCIF and SCIFA. Fortunately they can
easily be distinguished by physical address.
3. Not all boards use the same serial port for the console.
The defaults correspond to the boards that are supported in
mainline. If you want to use a different serial port, just change
the value of CONFIG_DEBUG_UART_PHYS, and the rest will auto-adapt.
4. debug_ll_io_init() maps the SCIF(A) registers to a fixed virtual
address. 0xfdxxxxxx was chosen, as it should lie below VMALLOC_END
= 0xff000000, and must not conflict with the 2 MiB reserved region
at PCI_IO_VIRT_BASE = 0xfee00000.
- On SoCs not using the legacy machine_desc.map_io(),
debug_ll_io_init() is called by the ARM core code.
- On SoCs using the legacy machine_desc.map_io(),
debug_ll_io_init() must be called explicitly. Calls are added
for r8a7740, r8a7779, sh7372, and sh73a0.
This was derived from the r8a7790 version by Laurent Pinchart.
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Tested-by: Simon Horman <horms+renesas@verge.net.au>
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
2014-11-14 15:49:47 +00:00
|
|
|
|
|
|
|
|
config DEBUG_RMOBILE_SCIFA1
|
|
|
|
|
bool "Kernel low-level debugging messages via SCIFA1 on R8A7740"
|
|
|
|
|
depends on ARCH_R8A7740
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
via SCIFA1 on Renesas R-Mobile A1 (R8A7740).
|
|
|
|
|
|
|
|
|
|
config DEBUG_RMOBILE_SCIFA4
|
|
|
|
|
bool "Kernel low-level debugging messages via SCIFA4 on SH73A0"
|
|
|
|
|
depends on ARCH_SH73A0
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
via SCIFA4 on Renesas SH-Mobile AG5 (SH73A0).
|
|
|
|
|
|
2011-11-23 17:44:05 +00:00
|
|
|
config DEBUG_S3C_UART0
|
2020-08-06 18:20:35 +00:00
|
|
|
depends on PLAT_SAMSUNG || ARCH_S5PV210 || ARCH_EXYNOS
|
2013-03-04 17:03:10 +00:00
|
|
|
select DEBUG_EXYNOS_UART if ARCH_EXYNOS
|
2014-07-25 15:11:24 +00:00
|
|
|
select DEBUG_S3C64XX_UART if ARCH_S3C64XX
|
2014-07-03 12:39:41 +00:00
|
|
|
select DEBUG_S5PV210_UART if ARCH_S5PV210
|
2014-07-04 21:27:45 +00:00
|
|
|
bool "Use Samsung S3C UART 0 for low-level debug"
|
2011-11-08 18:33:03 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want the debug print routines to direct
|
2011-11-23 17:44:05 +00:00
|
|
|
their output to UART 0. The port must have been initialised
|
|
|
|
|
by the boot-loader before use.
|
2011-11-08 18:33:03 +00:00
|
|
|
|
2011-11-23 17:44:05 +00:00
|
|
|
config DEBUG_S3C_UART1
|
2020-08-06 18:20:35 +00:00
|
|
|
depends on PLAT_SAMSUNG || ARCH_S5PV210 || ARCH_EXYNOS
|
2013-03-04 17:03:10 +00:00
|
|
|
select DEBUG_EXYNOS_UART if ARCH_EXYNOS
|
2014-07-25 15:11:24 +00:00
|
|
|
select DEBUG_S3C64XX_UART if ARCH_S3C64XX
|
2014-07-03 12:39:41 +00:00
|
|
|
select DEBUG_S5PV210_UART if ARCH_S5PV210
|
2014-07-04 21:27:45 +00:00
|
|
|
bool "Use Samsung S3C UART 1 for low-level debug"
|
2011-11-08 18:33:03 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want the debug print routines to direct
|
2011-11-23 17:44:05 +00:00
|
|
|
their output to UART 1. The port must have been initialised
|
|
|
|
|
by the boot-loader before use.
|
2011-11-08 18:33:03 +00:00
|
|
|
|
2011-11-23 17:44:05 +00:00
|
|
|
config DEBUG_S3C_UART2
|
2020-08-06 18:20:35 +00:00
|
|
|
depends on PLAT_SAMSUNG || ARCH_S5PV210 || ARCH_EXYNOS
|
2013-03-04 17:03:10 +00:00
|
|
|
select DEBUG_EXYNOS_UART if ARCH_EXYNOS
|
2014-07-25 15:11:24 +00:00
|
|
|
select DEBUG_S3C64XX_UART if ARCH_S3C64XX
|
2014-07-03 12:39:41 +00:00
|
|
|
select DEBUG_S5PV210_UART if ARCH_S5PV210
|
2014-07-04 21:27:45 +00:00
|
|
|
bool "Use Samsung S3C UART 2 for low-level debug"
|
2011-11-08 18:33:03 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want the debug print routines to direct
|
2011-11-23 17:44:05 +00:00
|
|
|
their output to UART 2. The port must have been initialised
|
|
|
|
|
by the boot-loader before use.
|
2011-11-08 18:33:03 +00:00
|
|
|
|
2012-11-22 05:24:04 +00:00
|
|
|
config DEBUG_S3C_UART3
|
2020-08-06 18:20:32 +00:00
|
|
|
depends on ARCH_EXYNOS || ARCH_S5PV210
|
2014-07-03 12:39:41 +00:00
|
|
|
select DEBUG_EXYNOS_UART if ARCH_EXYNOS
|
2014-07-25 15:11:24 +00:00
|
|
|
select DEBUG_S3C64XX_UART if ARCH_S3C64XX
|
2014-07-03 12:39:41 +00:00
|
|
|
select DEBUG_S5PV210_UART if ARCH_S5PV210
|
2014-07-04 21:27:45 +00:00
|
|
|
bool "Use Samsung S3C UART 3 for low-level debug"
|
2012-11-22 05:24:04 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want the debug print routines to direct
|
|
|
|
|
their output to UART 3. The port must have been initialised
|
|
|
|
|
by the boot-loader before use.
|
|
|
|
|
|
2014-11-06 07:20:23 +00:00
|
|
|
config DEBUG_SA1100
|
|
|
|
|
depends on ARCH_SA1100
|
|
|
|
|
bool "Use SA1100 UARTs for low-level debug"
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on SA-11x0 UART ports. The kernel will check for the first
|
|
|
|
|
enabled UART in a sequence 3-1-2.
|
|
|
|
|
|
2020-09-29 14:14:44 +00:00
|
|
|
config DEBUG_SD5203_UART
|
|
|
|
|
bool "Hisilicon SD5203 Debug UART"
|
|
|
|
|
depends on ARCH_SD5203
|
|
|
|
|
select DEBUG_UART_8250
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on SD5203 UART.
|
|
|
|
|
|
2015-03-09 20:48:31 +00:00
|
|
|
config DEBUG_SOCFPGA_UART0
|
2021-03-11 15:25:32 +00:00
|
|
|
depends on ARCH_INTEL_SOCFPGA
|
2015-03-09 20:48:31 +00:00
|
|
|
bool "Use SOCFPGA UART0 for low-level debug"
|
2013-07-07 10:42:46 +00:00
|
|
|
select DEBUG_UART_8250
|
2012-09-06 19:11:28 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
2015-03-09 20:48:31 +00:00
|
|
|
on SOCFPGA(Cyclone 5 and Arria 5) based platforms.
|
|
|
|
|
|
2018-10-09 11:28:37 +00:00
|
|
|
config DEBUG_SOCFPGA_ARRIA10_UART1
|
2021-03-11 15:25:32 +00:00
|
|
|
depends on ARCH_INTEL_SOCFPGA
|
2018-10-09 11:28:37 +00:00
|
|
|
bool "Use SOCFPGA Arria10 UART1 for low-level debug"
|
2015-03-09 20:48:31 +00:00
|
|
|
select DEBUG_UART_8250
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on SOCFPGA(Arria 10) based platforms.
|
|
|
|
|
|
2018-10-09 11:28:37 +00:00
|
|
|
config DEBUG_SOCFPGA_CYCLONE5_UART1
|
2021-03-11 15:25:32 +00:00
|
|
|
depends on ARCH_INTEL_SOCFPGA
|
2018-10-09 11:28:37 +00:00
|
|
|
bool "Use SOCFPGA Cyclone 5 UART1 for low-level debug"
|
|
|
|
|
select DEBUG_UART_8250
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on SOCFPGA(Cyclone 5 and Arria 5) based platforms.
|
2012-09-06 19:11:28 +00:00
|
|
|
|
2014-09-24 14:48:56 +00:00
|
|
|
config DEBUG_SUN9I_UART0
|
|
|
|
|
bool "Kernel low-level debugging messages via sun9i UART0"
|
|
|
|
|
depends on MACH_SUN9I
|
|
|
|
|
select DEBUG_UART_8250
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on Allwinner A80 based platforms on the UART0.
|
|
|
|
|
|
2012-11-19 11:09:41 +00:00
|
|
|
config DEBUG_SUNXI_UART0
|
|
|
|
|
bool "Kernel low-level debugging messages via sunXi UART0"
|
|
|
|
|
depends on ARCH_SUNXI
|
2013-07-06 22:13:15 +00:00
|
|
|
select DEBUG_UART_8250
|
2012-11-19 11:09:41 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on Allwinner A1X based platforms on the UART0.
|
|
|
|
|
|
2012-11-08 11:40:49 +00:00
|
|
|
config DEBUG_SUNXI_UART1
|
|
|
|
|
bool "Kernel low-level debugging messages via sunXi UART1"
|
|
|
|
|
depends on ARCH_SUNXI
|
2013-07-06 22:13:15 +00:00
|
|
|
select DEBUG_UART_8250
|
2012-11-08 11:40:49 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on Allwinner A1X based platforms on the UART1.
|
|
|
|
|
|
2014-06-20 14:52:51 +00:00
|
|
|
config DEBUG_SUNXI_R_UART
|
|
|
|
|
bool "Kernel low-level debugging messages via sunXi R_UART"
|
|
|
|
|
depends on MACH_SUN6I || MACH_SUN8I
|
|
|
|
|
select DEBUG_UART_8250
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on Allwinner A31/A23 based platforms on the R_UART.
|
|
|
|
|
|
2015-12-03 16:54:05 +00:00
|
|
|
config DEBUG_SPEAR3XX
|
|
|
|
|
bool "Kernel low-level debugging messages via ST SPEAr 3xx/6xx UART"
|
|
|
|
|
depends on ARCH_SPEAR3XX || ARCH_SPEAR6XX
|
|
|
|
|
select DEBUG_UART_PL01X
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on ST SPEAr based platforms.
|
|
|
|
|
|
|
|
|
|
config DEBUG_SPEAR13XX
|
|
|
|
|
bool "Kernel low-level debugging messages via ST SPEAr 13xx UART"
|
|
|
|
|
depends on ARCH_SPEAR13XX
|
|
|
|
|
select DEBUG_UART_PL01X
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on ST SPEAr13xx based platforms.
|
|
|
|
|
|
2020-12-09 19:42:31 +00:00
|
|
|
config DEBUG_STIH41X_ASC2
|
2013-07-06 13:23:30 +00:00
|
|
|
bool "Use StiH415/416 ASC2 UART for low-level debug"
|
|
|
|
|
depends on ARCH_STI
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on STiH415/416 based platforms like b2000, which has
|
|
|
|
|
default UART wired up to ASC2.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2020-12-09 19:42:31 +00:00
|
|
|
config DEBUG_STIH41X_SBC_ASC1
|
2013-07-06 13:23:30 +00:00
|
|
|
bool "Use StiH415/416 SBC ASC1 UART for low-level debug"
|
2013-07-05 14:08:44 +00:00
|
|
|
depends on ARCH_STI
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
2013-07-06 13:23:30 +00:00
|
|
|
on STiH415/416 based platforms like b2020. which has
|
|
|
|
|
default UART wired up to SBC ASC1.
|
2013-07-05 14:08:44 +00:00
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2020-12-09 19:45:43 +00:00
|
|
|
config DEBUG_STIH418_SBC_ASC0
|
|
|
|
|
bool "Use StiH418 SBC ASC0 UART for low-level debug"
|
|
|
|
|
depends on ARCH_STI
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on STiH418 based platforms which has default UART wired
|
|
|
|
|
up to SBC ASC0.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2017-07-27 16:50:20 +00:00
|
|
|
config STM32F4_DEBUG_UART
|
|
|
|
|
bool "Use STM32F4 UART for low-level debug"
|
2020-02-03 14:04:22 +00:00
|
|
|
depends on MACH_STM32F429 || MACH_STM32F469
|
2017-07-27 16:50:20 +00:00
|
|
|
select DEBUG_STM32_UART
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on STM32F4 based platforms, which default UART is wired on
|
2020-02-03 14:04:22 +00:00
|
|
|
USART1, but another UART instance can be selected by modifying
|
|
|
|
|
CONFIG_DEBUG_UART_PHYS.
|
2017-07-27 16:50:20 +00:00
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
|
|
config STM32F7_DEBUG_UART
|
|
|
|
|
bool "Use STM32F7 UART for low-level debug"
|
2020-02-03 14:04:23 +00:00
|
|
|
depends on MACH_STM32F746 || MACH_STM32F769
|
2017-07-27 16:50:20 +00:00
|
|
|
select DEBUG_STM32_UART
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on STM32F7 based platforms, which default UART is wired on
|
2020-02-03 14:04:23 +00:00
|
|
|
USART1, but another UART instance can be selected by modifying
|
|
|
|
|
CONFIG_DEBUG_UART_PHYS.
|
2017-07-27 16:50:20 +00:00
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2020-02-03 14:04:24 +00:00
|
|
|
config STM32H7_DEBUG_UART
|
|
|
|
|
bool "Use STM32H7 UART for low-level debug"
|
|
|
|
|
depends on MACH_STM32H743
|
|
|
|
|
select DEBUG_STM32_UART
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on STM32H7 based platforms, which default UART is wired on
|
|
|
|
|
USART1, but another UART instance can be selected by modifying
|
|
|
|
|
CONFIG_DEBUG_UART_PHYS.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2020-02-03 14:04:25 +00:00
|
|
|
config STM32MP1_DEBUG_UART
|
|
|
|
|
bool "Use STM32MP1 UART for low-level debug"
|
|
|
|
|
depends on MACH_STM32MP157
|
|
|
|
|
select DEBUG_STM32_UART
|
|
|
|
|
help
|
2023-01-24 18:16:18 +00:00
|
|
|
Say Y here if you want kernel low-level debugging support on
|
|
|
|
|
STM32MP1-based platforms, where the default UART is wired to
|
2020-02-03 14:04:25 +00:00
|
|
|
UART4, but another UART instance can be selected by modifying
|
|
|
|
|
CONFIG_DEBUG_UART_PHYS and CONFIG_DEBUG_UART_VIRT.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2013-07-06 13:23:30 +00:00
|
|
|
config TEGRA_DEBUG_UART_AUTO_ODMDATA
|
|
|
|
|
bool "Kernel low-level debugging messages via Tegra UART via ODMDATA"
|
2012-09-25 21:54:56 +00:00
|
|
|
depends on ARCH_TEGRA
|
2013-07-06 13:23:30 +00:00
|
|
|
select DEBUG_TEGRA_UART
|
|
|
|
|
help
|
|
|
|
|
Automatically determines which UART to use for low-level
|
|
|
|
|
debug based on the ODMDATA value. This value is part of
|
|
|
|
|
the BCT, and is written to the boot memory device using
|
|
|
|
|
nvflash, or other flashing tool. When bits 19:18 are 3,
|
|
|
|
|
then bits 17:15 indicate which UART to use; 0/1/2/3/4
|
|
|
|
|
are UART A/B/C/D/E.
|
|
|
|
|
|
|
|
|
|
config TEGRA_DEBUG_UARTA
|
|
|
|
|
bool "Kernel low-level debugging messages via Tegra UART A"
|
|
|
|
|
depends on ARCH_TEGRA
|
|
|
|
|
select DEBUG_TEGRA_UART
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on Tegra based platforms.
|
|
|
|
|
|
|
|
|
|
config TEGRA_DEBUG_UARTB
|
|
|
|
|
bool "Kernel low-level debugging messages via Tegra UART B"
|
|
|
|
|
depends on ARCH_TEGRA
|
|
|
|
|
select DEBUG_TEGRA_UART
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on Tegra based platforms.
|
|
|
|
|
|
|
|
|
|
config TEGRA_DEBUG_UARTC
|
|
|
|
|
bool "Kernel low-level debugging messages via Tegra UART C"
|
|
|
|
|
depends on ARCH_TEGRA
|
|
|
|
|
select DEBUG_TEGRA_UART
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on Tegra based platforms.
|
|
|
|
|
|
|
|
|
|
config TEGRA_DEBUG_UARTD
|
|
|
|
|
bool "Kernel low-level debugging messages via Tegra UART D"
|
|
|
|
|
depends on ARCH_TEGRA
|
|
|
|
|
select DEBUG_TEGRA_UART
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on Tegra based platforms.
|
|
|
|
|
|
|
|
|
|
config TEGRA_DEBUG_UARTE
|
|
|
|
|
bool "Kernel low-level debugging messages via Tegra UART E"
|
|
|
|
|
depends on ARCH_TEGRA
|
|
|
|
|
select DEBUG_TEGRA_UART
|
2012-09-25 21:54:56 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on Tegra based platforms.
|
|
|
|
|
|
2013-03-19 10:01:36 +00:00
|
|
|
config DEBUG_UX500_UART
|
|
|
|
|
depends on ARCH_U8500
|
|
|
|
|
bool "Use Ux500 UART for low-level debug"
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on Ux500 based platforms.
|
|
|
|
|
|
2015-12-03 16:54:05 +00:00
|
|
|
config DEBUG_VERSATILE
|
|
|
|
|
bool "Kernel low-level debugging messages via ARM Versatile UART"
|
|
|
|
|
depends on ARCH_VERSATILE
|
|
|
|
|
select DEBUG_UART_PL01X
|
2014-11-04 07:30:54 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
2015-12-03 16:54:05 +00:00
|
|
|
on ARM Versatile platforms.
|
2014-11-04 07:30:54 +00:00
|
|
|
|
2012-07-11 16:07:25 +00:00
|
|
|
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
|
2013-07-07 11:32:16 +00:00
|
|
|
select DEBUG_UART_PL01X
|
2012-07-11 16:07:25 +00:00
|
|
|
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
|
2013-07-07 11:32:16 +00:00
|
|
|
select DEBUG_UART_PL01X
|
2012-07-11 16:07:25 +00:00
|
|
|
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.
|
|
|
|
|
|
2012-08-30 12:46:44 +00:00
|
|
|
config DEBUG_VEXPRESS_UART0_CRX
|
|
|
|
|
bool "Use PL011 UART0 at 0xb0090000 (Cortex-R compliant tiles)"
|
|
|
|
|
depends on ARCH_VEXPRESS && !MMU
|
2013-07-07 11:32:16 +00:00
|
|
|
select DEBUG_UART_PL01X
|
2012-08-30 12:46:44 +00:00
|
|
|
help
|
|
|
|
|
This option selects UART0 at 0xb0090000. This is appropriate for
|
|
|
|
|
Cortex-R series tiles and SMMs, such as Cortex-R5 and Cortex-R7
|
|
|
|
|
|
2015-12-03 17:16:45 +00:00
|
|
|
config DEBUG_VF_UART
|
|
|
|
|
bool "Vybrid UART"
|
|
|
|
|
depends on SOC_VF610
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
|
|
on Vybrid based platforms.
|
|
|
|
|
|
2012-12-27 23:09:18 +00:00
|
|
|
config DEBUG_VT8500_UART0
|
|
|
|
|
bool "Use UART0 on VIA/Wondermedia SoCs"
|
|
|
|
|
depends on ARCH_VT8500
|
|
|
|
|
help
|
|
|
|
|
This option selects UART0 on VIA/Wondermedia System-on-a-chip
|
|
|
|
|
devices, including VT8500, WM8505, WM8650 and WM8850.
|
|
|
|
|
|
2015-12-03 17:16:45 +00:00
|
|
|
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.
|
|
|
|
|
|
2011-11-23 17:44:05 +00:00
|
|
|
config DEBUG_ICEDCC
|
|
|
|
|
bool "Kernel low-level debugging via EmbeddedICE DCC channel"
|
2011-11-08 18:33:04 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want the debug print routines to direct
|
2011-11-23 17:44:05 +00:00
|
|
|
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.
|
2011-11-08 18:33:04 +00:00
|
|
|
|
2012-03-27 10:30:31 +00:00
|
|
|
config DEBUG_SEMIHOSTING
|
2012-09-06 20:24:32 +00:00
|
|
|
bool "Kernel low-level debug output via semihosting I/O"
|
2011-11-08 18:33:03 +00:00
|
|
|
help
|
2012-03-27 10:30:31 +00:00
|
|
|
Semihosting enables code running on an ARM target to use
|
|
|
|
|
the I/O facilities on a host debugger/emulator through a
|
2012-09-06 20:24:32 +00:00
|
|
|
simple SVC call. The host debugger or emulator must have
|
2012-03-27 10:30:31 +00:00
|
|
|
semihosting enabled for the special svc call to be trapped
|
|
|
|
|
otherwise the kernel will crash.
|
2011-11-08 18:33:03 +00:00
|
|
|
|
2012-09-06 20:24:32 +00:00
|
|
|
This is known to work with OpenOCD, as well as
|
2012-03-27 10:30:31 +00:00
|
|
|
ARM's Fast Models, or any other controlling environment
|
|
|
|
|
that implements semihosting.
|
2011-11-08 18:33:04 +00:00
|
|
|
|
2012-03-27 10:30:31 +00:00
|
|
|
For more details about semihosting, please see
|
|
|
|
|
chapter 8 of DUI0203I_rvct_developer_guide.pdf from ARM Ltd.
|
2011-11-08 18:33:04 +00:00
|
|
|
|
2013-07-07 14:29:38 +00:00
|
|
|
config DEBUG_LL_UART_8250
|
|
|
|
|
bool "Kernel low-level debugging via 8250 UART"
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you wish the debug print routes to direct
|
|
|
|
|
their output to an 8250 UART. You can use this option
|
|
|
|
|
to provide the parameters for the 8250 UART rather than
|
|
|
|
|
selecting one of the platform specific options above if
|
|
|
|
|
you know the parameters for the port.
|
|
|
|
|
|
|
|
|
|
This option is preferred over the platform specific
|
|
|
|
|
options; the platform specific options are deprecated
|
|
|
|
|
and will be soon removed.
|
|
|
|
|
|
|
|
|
|
config DEBUG_LL_UART_PL01X
|
|
|
|
|
bool "Kernel low-level debugging via ARM Ltd PL01x Primecell UART"
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you wish the debug print routes to direct
|
|
|
|
|
their output to a PL01x Primecell UART. You can use
|
|
|
|
|
this option to provide the parameters for the UART
|
|
|
|
|
rather than selecting one of the platform specific
|
|
|
|
|
options above if you know the parameters for the port.
|
|
|
|
|
|
|
|
|
|
This option is preferred over the platform specific
|
|
|
|
|
options; the platform specific options are deprecated
|
|
|
|
|
and will be soon removed.
|
|
|
|
|
|
2011-09-01 17:58:51 +00:00
|
|
|
endchoice
|
|
|
|
|
|
2016-06-08 10:21:38 +00:00
|
|
|
config DEBUG_AT91_UART
|
|
|
|
|
bool
|
|
|
|
|
depends on ARCH_AT91
|
|
|
|
|
|
2013-03-04 17:03:10 +00:00
|
|
|
config DEBUG_EXYNOS_UART
|
|
|
|
|
bool
|
|
|
|
|
|
2014-07-25 15:11:24 +00:00
|
|
|
config DEBUG_S3C64XX_UART
|
|
|
|
|
bool
|
|
|
|
|
|
2014-07-03 12:39:41 +00:00
|
|
|
config DEBUG_S5PV210_UART
|
|
|
|
|
bool
|
|
|
|
|
|
2020-08-06 18:20:30 +00:00
|
|
|
config DEBUG_S3C_UART
|
2022-09-29 13:33:15 +00:00
|
|
|
depends on DEBUG_S3C64XX_UART || DEBUG_S5PV210_UART || \
|
2020-08-06 18:20:30 +00:00
|
|
|
DEBUG_EXYNOS_UART
|
|
|
|
|
int
|
|
|
|
|
default "0" if DEBUG_S3C_UART0
|
|
|
|
|
default "1" if DEBUG_S3C_UART1
|
|
|
|
|
default "2" if DEBUG_S3C_UART2
|
|
|
|
|
default "3" if DEBUG_S3C_UART3
|
|
|
|
|
|
2013-07-06 13:23:30 +00:00
|
|
|
config DEBUG_OMAP2PLUS_UART
|
|
|
|
|
bool
|
|
|
|
|
depends on ARCH_OMAP2PLUS
|
|
|
|
|
|
2012-12-12 11:03:53 +00:00
|
|
|
config DEBUG_IMX_UART_PORT
|
2018-11-28 09:04:16 +00:00
|
|
|
int "i.MX Debug UART Port Selection"
|
|
|
|
|
depends on DEBUG_IMX1_UART || \
|
|
|
|
|
DEBUG_IMX25_UART || \
|
2021-10-28 14:19:33 +00:00
|
|
|
DEBUG_IMX27_UART || \
|
2018-11-28 09:04:16 +00:00
|
|
|
DEBUG_IMX31_UART || \
|
|
|
|
|
DEBUG_IMX35_UART || \
|
|
|
|
|
DEBUG_IMX50_UART || \
|
|
|
|
|
DEBUG_IMX51_UART || \
|
|
|
|
|
DEBUG_IMX53_UART || \
|
|
|
|
|
DEBUG_IMX6Q_UART || \
|
|
|
|
|
DEBUG_IMX6SL_UART || \
|
|
|
|
|
DEBUG_IMX6SX_UART || \
|
|
|
|
|
DEBUG_IMX6UL_UART || \
|
|
|
|
|
DEBUG_IMX7D_UART
|
2012-10-08 05:44:29 +00:00
|
|
|
default 1
|
|
|
|
|
help
|
|
|
|
|
Choose UART port on which kernel low-level debug messages
|
|
|
|
|
should be output.
|
|
|
|
|
|
2014-03-05 22:07:48 +00:00
|
|
|
config DEBUG_VF_UART_PORT
|
|
|
|
|
int "Vybrid Debug UART Port Selection" if DEBUG_VF_UART
|
|
|
|
|
default 1
|
|
|
|
|
range 0 3
|
|
|
|
|
depends on SOC_VF610
|
|
|
|
|
help
|
|
|
|
|
Choose UART port on which kernel low-level debug messages
|
|
|
|
|
should be output.
|
|
|
|
|
|
2013-07-06 13:23:30 +00:00
|
|
|
config DEBUG_TEGRA_UART
|
|
|
|
|
bool
|
|
|
|
|
depends on ARCH_TEGRA
|
2013-06-25 11:15:32 +00:00
|
|
|
|
2017-07-27 16:50:20 +00:00
|
|
|
config DEBUG_STM32_UART
|
|
|
|
|
bool
|
|
|
|
|
depends on ARCH_STM32
|
|
|
|
|
|
2020-08-27 22:28:56 +00:00
|
|
|
config DEBUG_UART_FLOW_CONTROL
|
|
|
|
|
bool "Enable flow control (CTS) for the debug UART"
|
|
|
|
|
depends on DEBUG_LL
|
2020-09-24 18:25:46 +00:00
|
|
|
default y if DEBUG_FOOTBRIDGE_COM1 || DEBUG_GEMINI || ARCH_RPC
|
2020-08-27 22:28:56 +00:00
|
|
|
help
|
|
|
|
|
Some UART ports are connected to terminals that will use modem
|
|
|
|
|
control signals to indicate whether they are ready to receive text.
|
|
|
|
|
In practice this means that the terminal is asserting the special
|
|
|
|
|
control signal CTS (Clear To Send). If your debug UART supports
|
|
|
|
|
this and your debug terminal will require it, enable this option.
|
|
|
|
|
|
2012-08-31 05:03:46 +00:00
|
|
|
config DEBUG_LL_INCLUDE
|
|
|
|
|
string
|
2014-11-06 07:20:23 +00:00
|
|
|
default "debug/sa1100.S" if DEBUG_SA1100
|
2016-02-05 09:49:22 +00:00
|
|
|
default "debug/palmchip.S" if DEBUG_UART_8250_PALMCHIP
|
2013-07-07 14:29:38 +00:00
|
|
|
default "debug/8250.S" if DEBUG_LL_UART_8250 || DEBUG_UART_8250
|
2015-01-20 10:38:02 +00:00
|
|
|
default "debug/at91.S" if DEBUG_AT91_UART
|
2014-11-24 11:08:28 +00:00
|
|
|
default "debug/asm9260.S" if DEBUG_ASM9260_UART
|
2014-06-19 15:26:34 +00:00
|
|
|
default "debug/clps711x.S" if DEBUG_CLPS711X_UART1 || DEBUG_CLPS711X_UART2
|
2015-12-03 17:27:53 +00:00
|
|
|
default "debug/dc21285.S" if DEBUG_DC21285_PORT
|
2014-09-09 19:38:00 +00:00
|
|
|
default "debug/meson.S" if DEBUG_MESON_UARTAO
|
2013-07-07 14:29:38 +00:00
|
|
|
default "debug/pl01x.S" if DEBUG_LL_UART_PL01X || DEBUG_UART_PL01X
|
2013-03-04 17:03:10 +00:00
|
|
|
default "debug/exynos.S" if DEBUG_EXYNOS_UART
|
2012-08-31 05:03:46 +00:00
|
|
|
default "debug/icedcc.S" if DEBUG_ICEDCC
|
2012-09-16 12:50:45 +00:00
|
|
|
default "debug/imx.S" if DEBUG_IMX1_UART || \
|
|
|
|
|
DEBUG_IMX25_UART || \
|
2021-10-28 14:19:33 +00:00
|
|
|
DEBUG_IMX27_UART || \
|
2012-12-12 10:54:01 +00:00
|
|
|
DEBUG_IMX31_UART || \
|
|
|
|
|
DEBUG_IMX35_UART || \
|
2013-10-29 05:15:51 +00:00
|
|
|
DEBUG_IMX50_UART || \
|
2012-09-16 12:50:45 +00:00
|
|
|
DEBUG_IMX51_UART || \
|
2021-10-28 14:19:33 +00:00
|
|
|
DEBUG_IMX53_UART || \
|
2013-05-03 03:21:03 +00:00
|
|
|
DEBUG_IMX6Q_UART || \
|
2014-05-11 13:53:48 +00:00
|
|
|
DEBUG_IMX6SL_UART || \
|
2015-05-06 15:16:07 +00:00
|
|
|
DEBUG_IMX6SX_UART || \
|
2015-07-09 18:09:47 +00:00
|
|
|
DEBUG_IMX6UL_UART || \
|
2015-05-06 15:16:07 +00:00
|
|
|
DEBUG_IMX7D_UART
|
2015-03-13 18:09:34 +00:00
|
|
|
default "debug/msm.S" if DEBUG_QCOM_UARTDM
|
2013-01-11 19:24:19 +00:00
|
|
|
default "debug/omap2plus.S" if DEBUG_OMAP2PLUS_UART
|
ARM: shmobile: Add early debugging support using SCIF(A)
Add serial port debug macros for the SCIF(A) serial ports.
This includes all supported shmobile SoCs, except for EMEV2.
The configuration logic (both Kconfig and #ifdef) is more complicated than
one would expect, for several reasons:
1. Not all SoCs have the same serial devices, and they're not always
at the same addresses.
2. There are two different types: SCIF and SCIFA. Fortunately they can
easily be distinguished by physical address.
3. Not all boards use the same serial port for the console.
The defaults correspond to the boards that are supported in
mainline. If you want to use a different serial port, just change
the value of CONFIG_DEBUG_UART_PHYS, and the rest will auto-adapt.
4. debug_ll_io_init() maps the SCIF(A) registers to a fixed virtual
address. 0xfdxxxxxx was chosen, as it should lie below VMALLOC_END
= 0xff000000, and must not conflict with the 2 MiB reserved region
at PCI_IO_VIRT_BASE = 0xfee00000.
- On SoCs not using the legacy machine_desc.map_io(),
debug_ll_io_init() is called by the ARM core code.
- On SoCs using the legacy machine_desc.map_io(),
debug_ll_io_init() must be called explicitly. Calls are added
for r8a7740, r8a7779, sh7372, and sh73a0.
This was derived from the r8a7790 version by Laurent Pinchart.
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Tested-by: Simon Horman <horms+renesas@verge.net.au>
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
2014-11-14 15:49:47 +00:00
|
|
|
default "debug/renesas-scif.S" if DEBUG_R7S72100_SCIF2
|
2019-06-03 07:37:19 +00:00
|
|
|
default "debug/renesas-scif.S" if DEBUG_R7S9210_SCIF2
|
|
|
|
|
default "debug/renesas-scif.S" if DEBUG_R7S9210_SCIF4
|
ARM: shmobile: Add early debugging support using SCIF(A)
Add serial port debug macros for the SCIF(A) serial ports.
This includes all supported shmobile SoCs, except for EMEV2.
The configuration logic (both Kconfig and #ifdef) is more complicated than
one would expect, for several reasons:
1. Not all SoCs have the same serial devices, and they're not always
at the same addresses.
2. There are two different types: SCIF and SCIFA. Fortunately they can
easily be distinguished by physical address.
3. Not all boards use the same serial port for the console.
The defaults correspond to the boards that are supported in
mainline. If you want to use a different serial port, just change
the value of CONFIG_DEBUG_UART_PHYS, and the rest will auto-adapt.
4. debug_ll_io_init() maps the SCIF(A) registers to a fixed virtual
address. 0xfdxxxxxx was chosen, as it should lie below VMALLOC_END
= 0xff000000, and must not conflict with the 2 MiB reserved region
at PCI_IO_VIRT_BASE = 0xfee00000.
- On SoCs not using the legacy machine_desc.map_io(),
debug_ll_io_init() is called by the ARM core code.
- On SoCs using the legacy machine_desc.map_io(),
debug_ll_io_init() must be called explicitly. Calls are added
for r8a7740, r8a7779, sh7372, and sh73a0.
This was derived from the r8a7790 version by Laurent Pinchart.
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Tested-by: Simon Horman <horms+renesas@verge.net.au>
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
2014-11-14 15:49:47 +00:00
|
|
|
default "debug/renesas-scif.S" if DEBUG_RCAR_GEN1_SCIF0
|
|
|
|
|
default "debug/renesas-scif.S" if DEBUG_RCAR_GEN1_SCIF2
|
|
|
|
|
default "debug/renesas-scif.S" if DEBUG_RCAR_GEN2_SCIF0
|
2018-03-29 10:42:26 +00:00
|
|
|
default "debug/renesas-scif.S" if DEBUG_RCAR_GEN2_SCIF1
|
ARM: shmobile: Add early debugging support using SCIF(A)
Add serial port debug macros for the SCIF(A) serial ports.
This includes all supported shmobile SoCs, except for EMEV2.
The configuration logic (both Kconfig and #ifdef) is more complicated than
one would expect, for several reasons:
1. Not all SoCs have the same serial devices, and they're not always
at the same addresses.
2. There are two different types: SCIF and SCIFA. Fortunately they can
easily be distinguished by physical address.
3. Not all boards use the same serial port for the console.
The defaults correspond to the boards that are supported in
mainline. If you want to use a different serial port, just change
the value of CONFIG_DEBUG_UART_PHYS, and the rest will auto-adapt.
4. debug_ll_io_init() maps the SCIF(A) registers to a fixed virtual
address. 0xfdxxxxxx was chosen, as it should lie below VMALLOC_END
= 0xff000000, and must not conflict with the 2 MiB reserved region
at PCI_IO_VIRT_BASE = 0xfee00000.
- On SoCs not using the legacy machine_desc.map_io(),
debug_ll_io_init() is called by the ARM core code.
- On SoCs using the legacy machine_desc.map_io(),
debug_ll_io_init() must be called explicitly. Calls are added
for r8a7740, r8a7779, sh7372, and sh73a0.
This was derived from the r8a7790 version by Laurent Pinchart.
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Tested-by: Simon Horman <horms+renesas@verge.net.au>
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
2014-11-14 15:49:47 +00:00
|
|
|
default "debug/renesas-scif.S" if DEBUG_RCAR_GEN2_SCIF2
|
2017-08-16 10:20:10 +00:00
|
|
|
default "debug/renesas-scif.S" if DEBUG_RCAR_GEN2_SCIF4
|
2020-04-29 21:56:41 +00:00
|
|
|
default "debug/renesas-scif.S" if DEBUG_RCAR_GEN2_SCIFA2
|
ARM: shmobile: Add early debugging support using SCIF(A)
Add serial port debug macros for the SCIF(A) serial ports.
This includes all supported shmobile SoCs, except for EMEV2.
The configuration logic (both Kconfig and #ifdef) is more complicated than
one would expect, for several reasons:
1. Not all SoCs have the same serial devices, and they're not always
at the same addresses.
2. There are two different types: SCIF and SCIFA. Fortunately they can
easily be distinguished by physical address.
3. Not all boards use the same serial port for the console.
The defaults correspond to the boards that are supported in
mainline. If you want to use a different serial port, just change
the value of CONFIG_DEBUG_UART_PHYS, and the rest will auto-adapt.
4. debug_ll_io_init() maps the SCIF(A) registers to a fixed virtual
address. 0xfdxxxxxx was chosen, as it should lie below VMALLOC_END
= 0xff000000, and must not conflict with the 2 MiB reserved region
at PCI_IO_VIRT_BASE = 0xfee00000.
- On SoCs not using the legacy machine_desc.map_io(),
debug_ll_io_init() is called by the ARM core code.
- On SoCs using the legacy machine_desc.map_io(),
debug_ll_io_init() must be called explicitly. Calls are added
for r8a7740, r8a7779, sh7372, and sh73a0.
This was derived from the r8a7790 version by Laurent Pinchart.
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Tested-by: Simon Horman <horms+renesas@verge.net.au>
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
2014-11-14 15:49:47 +00:00
|
|
|
default "debug/renesas-scif.S" if DEBUG_RMOBILE_SCIFA0
|
|
|
|
|
default "debug/renesas-scif.S" if DEBUG_RMOBILE_SCIFA1
|
|
|
|
|
default "debug/renesas-scif.S" if DEBUG_RMOBILE_SCIFA4
|
2022-09-29 13:33:15 +00:00
|
|
|
default "debug/s3c24xx.S" if DEBUG_S3C64XX_UART
|
2014-07-03 12:39:41 +00:00
|
|
|
default "debug/s5pv210.S" if DEBUG_S5PV210_UART
|
2020-12-09 19:42:31 +00:00
|
|
|
default "debug/sti.S" if DEBUG_STIH41X_ASC2
|
|
|
|
|
default "debug/sti.S" if DEBUG_STIH41X_SBC_ASC1
|
2020-12-09 19:45:43 +00:00
|
|
|
default "debug/sti.S" if DEBUG_STIH418_SBC_ASC0
|
2017-07-27 16:50:20 +00:00
|
|
|
default "debug/stm32.S" if DEBUG_STM32_UART
|
2013-05-04 19:34:30 +00:00
|
|
|
default "debug/tegra.S" if DEBUG_TEGRA_UART
|
|
|
|
|
default "debug/ux500.S" if DEBUG_UX500_UART
|
2013-07-07 11:36:46 +00:00
|
|
|
default "debug/vexpress.S" if DEBUG_VEXPRESS_UART0_DETECT
|
2013-05-12 09:22:17 +00:00
|
|
|
default "debug/vf.S" if DEBUG_VF_UART
|
2012-12-27 23:09:18 +00:00
|
|
|
default "debug/vt8500.S" if DEBUG_VT8500_UART0
|
2012-11-19 16:16:01 +00:00
|
|
|
default "debug/zynq.S" if DEBUG_ZYNQ_UART0 || DEBUG_ZYNQ_UART1
|
2024-09-23 19:49:21 +00:00
|
|
|
default "debug/bcm63xx.S" if DEBUG_BCM63XX_UART || DEBUG_BCMBCA
|
2015-01-14 08:40:31 +00:00
|
|
|
default "debug/digicolor.S" if DEBUG_DIGICOLOR_UA0
|
2016-06-28 19:18:51 +00:00
|
|
|
default "debug/brcmstb.S" if DEBUG_BRCMSTB_UART
|
2012-08-31 05:03:46 +00:00
|
|
|
default "mach/debug-macro.S"
|
|
|
|
|
|
2013-07-07 14:29:38 +00:00
|
|
|
# Compatibility options for PL01x
|
2013-07-07 11:32:16 +00:00
|
|
|
config DEBUG_UART_PL01X
|
2015-01-09 17:34:22 +00:00
|
|
|
bool
|
2013-07-07 11:32:16 +00:00
|
|
|
|
2013-07-07 14:29:38 +00:00
|
|
|
# Compatibility options for 8250
|
2013-07-06 21:59:10 +00:00
|
|
|
config DEBUG_UART_8250
|
2022-09-29 13:31:18 +00:00
|
|
|
def_bool ARCH_IXP4XX || ARCH_RPC
|
2013-07-06 22:13:15 +00:00
|
|
|
|
2013-07-06 23:01:39 +00:00
|
|
|
config DEBUG_UART_PHYS
|
|
|
|
|
hex "Physical base address of debug UART"
|
|
|
|
|
default 0x01c28000 if DEBUG_SUNXI_UART0
|
|
|
|
|
default 0x01c28400 if DEBUG_SUNXI_UART1
|
2013-07-07 15:18:34 +00:00
|
|
|
default 0x01d0c000 if DEBUG_DAVINCI_DA8XX_UART1
|
|
|
|
|
default 0x01d0d000 if DEBUG_DAVINCI_DA8XX_UART2
|
2014-06-20 14:52:51 +00:00
|
|
|
default 0x01f02800 if DEBUG_SUNXI_R_UART
|
2013-07-07 15:05:49 +00:00
|
|
|
default 0x02530c00 if DEBUG_KEYSTONE_UART0
|
|
|
|
|
default 0x02531000 if DEBUG_KEYSTONE_UART1
|
2013-07-06 23:01:39 +00:00
|
|
|
default 0x03010fe0 if ARCH_RPC
|
2014-09-24 14:48:56 +00:00
|
|
|
default 0x07000000 if DEBUG_SUN9I_UART0
|
2020-12-09 19:45:43 +00:00
|
|
|
default 0x09530000 if DEBUG_STIH418_SBC_ASC0
|
2014-09-16 10:35:10 +00:00
|
|
|
default 0x10009000 if DEBUG_REALVIEW_STD_PORT || \
|
2013-07-07 11:32:16 +00:00
|
|
|
DEBUG_VEXPRESS_UART0_CA9
|
|
|
|
|
default 0x1010c000 if DEBUG_REALVIEW_PB1176_PORT
|
2013-07-06 23:01:39 +00:00
|
|
|
default 0x10124000 if DEBUG_RK3X_UART0
|
|
|
|
|
default 0x10126000 if DEBUG_RK3X_UART1
|
2015-12-03 16:54:05 +00:00
|
|
|
default 0x101f1000 if DEBUG_VERSATILE
|
2013-07-07 11:32:16 +00:00
|
|
|
default 0x101fb000 if DEBUG_NOMADIK_UART
|
2016-11-14 12:12:35 +00:00
|
|
|
default 0x10210000 if DEBUG_RV1108_UART2
|
|
|
|
|
default 0x10220000 if DEBUG_RV1108_UART1
|
|
|
|
|
default 0x10230000 if DEBUG_RV1108_UART0
|
2014-11-04 07:30:54 +00:00
|
|
|
default 0x11002000 if DEBUG_MT8127_UART0
|
2014-08-18 14:58:00 +00:00
|
|
|
default 0x11006000 if DEBUG_MT6589_UART0
|
2014-11-04 07:30:54 +00:00
|
|
|
default 0x11009000 if DEBUG_MT8135_UART3
|
2015-12-03 16:54:05 +00:00
|
|
|
default 0x16000000 if DEBUG_INTEGRATOR
|
2020-09-29 14:14:44 +00:00
|
|
|
default 0x1600d000 if DEBUG_SD5203_UART
|
2014-02-03 23:01:44 +00:00
|
|
|
default 0x18000300 if DEBUG_BCM_5301X
|
2017-09-28 23:14:59 +00:00
|
|
|
default 0x18000400 if DEBUG_BCM_HR2
|
2018-05-30 13:19:55 +00:00
|
|
|
default 0x18023000 if DEBUG_BCM_IPROC_UART3
|
2013-07-07 11:32:16 +00:00
|
|
|
default 0x1c090000 if DEBUG_VEXPRESS_UART0_RS1
|
2021-05-04 17:03:16 +00:00
|
|
|
default 0x1f221000 if DEBUG_MSTARV7_PMUART
|
2014-12-24 03:09:56 +00:00
|
|
|
default 0x20001000 if DEBUG_HIP01_UART
|
2013-07-06 23:01:39 +00:00
|
|
|
default 0x20060000 if DEBUG_RK29_UART0
|
|
|
|
|
default 0x20064000 if DEBUG_RK29_UART1 || DEBUG_RK3X_UART2
|
|
|
|
|
default 0x20068000 if DEBUG_RK29_UART2 || DEBUG_RK3X_UART3
|
2013-07-07 11:32:16 +00:00
|
|
|
default 0x20201000 if DEBUG_BCM2835
|
2013-12-23 08:00:01 +00:00
|
|
|
default 0x3e000000 if DEBUG_BCM_KONA_UART
|
2018-05-30 13:19:56 +00:00
|
|
|
default 0x3f201000 if DEBUG_BCM2836
|
2020-02-03 14:04:25 +00:00
|
|
|
default 0x40010000 if STM32MP1_DEBUG_UART
|
2020-02-03 14:04:24 +00:00
|
|
|
default 0x40011000 if STM32F4_DEBUG_UART || STM32F7_DEBUG_UART || \
|
|
|
|
|
STM32H7_DEBUG_UART
|
2017-05-31 01:06:24 +00:00
|
|
|
default 0x40028000 if DEBUG_AT91_SAMV7_USART1
|
2015-05-19 18:55:03 +00:00
|
|
|
default 0x40081000 if DEBUG_LPC18XX_UART0
|
2015-12-03 16:54:05 +00:00
|
|
|
default 0x40090000 if DEBUG_LPC32XX
|
2013-07-06 23:01:39 +00:00
|
|
|
default 0x40100000 if DEBUG_PXA_UART1
|
2015-12-03 16:54:05 +00:00
|
|
|
default 0x42000000 if DEBUG_GEMINI
|
2017-07-17 05:10:14 +00:00
|
|
|
default 0x44e09000 if DEBUG_AM33XXUART1
|
2017-07-17 05:10:14 +00:00
|
|
|
default 0x48020000 if DEBUG_OMAP4UART3 || DEBUG_TI81XXUART1
|
|
|
|
|
default 0x48022000 if DEBUG_TI81XXUART2
|
|
|
|
|
default 0x48024000 if DEBUG_TI81XXUART3
|
arm: debug: reuse the config DEBUG_OMAP2UART{1,2} for OMAP{3,4,5}
Commit d2b310b0234c ("ARM: debug: Use generic 8250 debug_ll for omap2 and
omap3/4/5 common uarts") adds address definitions of DEBUG_UART_PHYS for
OMAP2, OMAP3, OMAP4 and OMAP5 in ./arch/arm/Kconfig.debug.
These definitions depend on DEBUG_OMAP{2,3,4,5}UART{1,2}; however, only
DEBUG_OMAP2UART{1,2} are defined in ./arch/arm/Kconfig.debug, and
DEBUG_OMAP{3,4,5}UART{1,2} are not defined. Hence, the script
./scripts/checkkconfigsymbols.py warns here on non-existing symbols.
Simply reuse the config DEBUG_OMAP2UART{1,2}; there is no need to define
separate config symbols for OMAP{3,4,5}. So, just delete the dead
references to DEBUG_OMAP{3,4,5}UART{1,2}.
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Link: https://lore.kernel.org/r/20231025112136.3445-1-lukas.bulwahn@gmail.com
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
2023-10-25 11:21:36 +00:00
|
|
|
default 0x4806a000 if DEBUG_OMAP2UART1
|
|
|
|
|
default 0x4806c000 if DEBUG_OMAP2UART2
|
2017-06-14 07:31:13 +00:00
|
|
|
default 0x4806e000 if DEBUG_OMAP2UART3 || DEBUG_OMAP4UART4
|
|
|
|
|
default 0x49020000 if DEBUG_OMAP3UART3
|
|
|
|
|
default 0x49042000 if DEBUG_OMAP3UART4
|
2015-12-03 17:27:53 +00:00
|
|
|
default 0x7c0003f8 if DEBUG_FOOTBRIDGE_COM1
|
2014-07-25 15:11:24 +00:00
|
|
|
default 0x7f005000 if DEBUG_S3C64XX_UART && DEBUG_S3C_UART0
|
|
|
|
|
default 0x7f005400 if DEBUG_S3C64XX_UART && DEBUG_S3C_UART1
|
|
|
|
|
default 0x7f005800 if DEBUG_S3C64XX_UART && DEBUG_S3C_UART2
|
|
|
|
|
default 0x7f005c00 if DEBUG_S3C64XX_UART && DEBUG_S3C_UART3
|
2014-11-24 11:08:28 +00:00
|
|
|
default 0x80010000 if DEBUG_ASM9260_UART
|
2013-07-07 11:32:16 +00:00
|
|
|
default 0x80070000 if DEBUG_IMX23_UART
|
|
|
|
|
default 0x80074000 if DEBUG_IMX28_UART
|
2015-12-03 15:19:22 +00:00
|
|
|
default 0x808c0000 if DEBUG_EP93XX || ARCH_EP93XX
|
2013-07-07 11:32:16 +00:00
|
|
|
default 0x90020000 if DEBUG_NSPIRE_CLASSIC_UART || DEBUG_NSPIRE_CX_UART
|
|
|
|
|
default 0xb0090000 if DEBUG_VEXPRESS_UART0_CRX
|
2013-07-06 23:01:39 +00:00
|
|
|
default 0xc8000000 if ARCH_IXP4XX && !CPU_BIG_ENDIAN
|
|
|
|
|
default 0xc8000003 if ARCH_IXP4XX && CPU_BIG_ENDIAN
|
2015-12-03 16:54:05 +00:00
|
|
|
default 0xd0000000 if DEBUG_SPEAR3XX
|
2015-01-08 17:38:03 +00:00
|
|
|
default 0xd0012000 if DEBUG_MVEBU_UART0
|
2014-09-09 19:38:00 +00:00
|
|
|
default 0xc81004c0 if DEBUG_MESON_UARTAO
|
2013-07-06 23:01:39 +00:00
|
|
|
default 0xd4017000 if DEBUG_MMP_UART2
|
|
|
|
|
default 0xd4018000 if DEBUG_MMP_UART3
|
2015-12-03 16:54:05 +00:00
|
|
|
default 0xe0000000 if DEBUG_SPEAR13XX
|
2022-05-13 09:25:30 +00:00
|
|
|
default 0xe0064200 if DEBUG_AT91_LAN966_FLEXCOM
|
2021-04-09 11:31:16 +00:00
|
|
|
default 0xe1824200 if DEBUG_AT91_SAMA7G5_FLEXCOM3
|
2013-12-20 07:01:41 +00:00
|
|
|
default 0xe4007000 if DEBUG_HIP04_UART
|
ARM: shmobile: Add early debugging support using SCIF(A)
Add serial port debug macros for the SCIF(A) serial ports.
This includes all supported shmobile SoCs, except for EMEV2.
The configuration logic (both Kconfig and #ifdef) is more complicated than
one would expect, for several reasons:
1. Not all SoCs have the same serial devices, and they're not always
at the same addresses.
2. There are two different types: SCIF and SCIFA. Fortunately they can
easily be distinguished by physical address.
3. Not all boards use the same serial port for the console.
The defaults correspond to the boards that are supported in
mainline. If you want to use a different serial port, just change
the value of CONFIG_DEBUG_UART_PHYS, and the rest will auto-adapt.
4. debug_ll_io_init() maps the SCIF(A) registers to a fixed virtual
address. 0xfdxxxxxx was chosen, as it should lie below VMALLOC_END
= 0xff000000, and must not conflict with the 2 MiB reserved region
at PCI_IO_VIRT_BASE = 0xfee00000.
- On SoCs not using the legacy machine_desc.map_io(),
debug_ll_io_init() is called by the ARM core code.
- On SoCs using the legacy machine_desc.map_io(),
debug_ll_io_init() must be called explicitly. Calls are added
for r8a7740, r8a7779, sh7372, and sh73a0.
This was derived from the r8a7790 version by Laurent Pinchart.
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Tested-by: Simon Horman <horms+renesas@verge.net.au>
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
2014-11-14 15:49:47 +00:00
|
|
|
default 0xe6c40000 if DEBUG_RMOBILE_SCIFA0
|
|
|
|
|
default 0xe6c50000 if DEBUG_RMOBILE_SCIFA1
|
2020-04-29 21:56:41 +00:00
|
|
|
default 0xe6c60000 if DEBUG_RCAR_GEN2_SCIFA2
|
ARM: shmobile: Add early debugging support using SCIF(A)
Add serial port debug macros for the SCIF(A) serial ports.
This includes all supported shmobile SoCs, except for EMEV2.
The configuration logic (both Kconfig and #ifdef) is more complicated than
one would expect, for several reasons:
1. Not all SoCs have the same serial devices, and they're not always
at the same addresses.
2. There are two different types: SCIF and SCIFA. Fortunately they can
easily be distinguished by physical address.
3. Not all boards use the same serial port for the console.
The defaults correspond to the boards that are supported in
mainline. If you want to use a different serial port, just change
the value of CONFIG_DEBUG_UART_PHYS, and the rest will auto-adapt.
4. debug_ll_io_init() maps the SCIF(A) registers to a fixed virtual
address. 0xfdxxxxxx was chosen, as it should lie below VMALLOC_END
= 0xff000000, and must not conflict with the 2 MiB reserved region
at PCI_IO_VIRT_BASE = 0xfee00000.
- On SoCs not using the legacy machine_desc.map_io(),
debug_ll_io_init() is called by the ARM core code.
- On SoCs using the legacy machine_desc.map_io(),
debug_ll_io_init() must be called explicitly. Calls are added
for r8a7740, r8a7779, sh7372, and sh73a0.
This was derived from the r8a7790 version by Laurent Pinchart.
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Tested-by: Simon Horman <horms+renesas@verge.net.au>
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
2014-11-14 15:49:47 +00:00
|
|
|
default 0xe6c80000 if DEBUG_RMOBILE_SCIFA4
|
|
|
|
|
default 0xe6e58000 if DEBUG_RCAR_GEN2_SCIF2
|
|
|
|
|
default 0xe6e60000 if DEBUG_RCAR_GEN2_SCIF0
|
2018-03-29 10:42:26 +00:00
|
|
|
default 0xe6e68000 if DEBUG_RCAR_GEN2_SCIF1
|
2017-08-16 10:20:10 +00:00
|
|
|
default 0xe6ee0000 if DEBUG_RCAR_GEN2_SCIF4
|
2019-06-03 07:37:19 +00:00
|
|
|
default 0xe8008000 if DEBUG_R7S72100_SCIF2 || DEBUG_R7S9210_SCIF2
|
|
|
|
|
default 0xe8009000 if DEBUG_R7S9210_SCIF4
|
2019-04-17 15:13:27 +00:00
|
|
|
default 0xf0000000 if DEBUG_DIGICOLOR_UA0
|
2015-01-08 17:38:03 +00:00
|
|
|
default 0xf1012000 if DEBUG_MVEBU_UART0_ALTERNATE
|
2015-01-08 17:38:04 +00:00
|
|
|
default 0xf1012100 if DEBUG_MVEBU_UART1_ALTERNATE
|
2013-09-09 12:10:54 +00:00
|
|
|
default 0xf7fc9000 if DEBUG_BERLIN_UART
|
2016-06-08 10:21:38 +00:00
|
|
|
default 0xf8020000 if DEBUG_AT91_SAMA5D2_UART1
|
2014-04-11 03:40:58 +00:00
|
|
|
default 0xf8b00000 if DEBUG_HIX5HD2_UART
|
2014-04-14 13:47:34 +00:00
|
|
|
default 0xf991e000 if DEBUG_QCOM_UARTDM
|
2016-06-08 10:21:38 +00:00
|
|
|
default 0xfc00c000 if DEBUG_AT91_SAMA5D4_USART3
|
2013-08-24 05:58:39 +00:00
|
|
|
default 0xfcb00000 if DEBUG_HI3620_UART
|
2015-03-12 11:53:04 +00:00
|
|
|
default 0xfd883000 if DEBUG_ALPINE_UART0
|
2020-12-09 19:42:31 +00:00
|
|
|
default 0xfe531000 if DEBUG_STIH41X_SBC_ASC1
|
|
|
|
|
default 0xfed32000 if DEBUG_STIH41X_ASC2
|
2014-06-28 11:31:17 +00:00
|
|
|
default 0xff690000 if DEBUG_RK32_UART2
|
2024-09-23 19:49:21 +00:00
|
|
|
default 0xff800640 if DEBUG_BCMBCA
|
2015-03-09 20:48:31 +00:00
|
|
|
default 0xffc02000 if DEBUG_SOCFPGA_UART0
|
2018-10-09 11:28:37 +00:00
|
|
|
default 0xffc02100 if DEBUG_SOCFPGA_ARRIA10_UART1
|
|
|
|
|
default 0xffc03000 if DEBUG_SOCFPGA_CYCLONE5_UART1
|
ARM: shmobile: Add early debugging support using SCIF(A)
Add serial port debug macros for the SCIF(A) serial ports.
This includes all supported shmobile SoCs, except for EMEV2.
The configuration logic (both Kconfig and #ifdef) is more complicated than
one would expect, for several reasons:
1. Not all SoCs have the same serial devices, and they're not always
at the same addresses.
2. There are two different types: SCIF and SCIFA. Fortunately they can
easily be distinguished by physical address.
3. Not all boards use the same serial port for the console.
The defaults correspond to the boards that are supported in
mainline. If you want to use a different serial port, just change
the value of CONFIG_DEBUG_UART_PHYS, and the rest will auto-adapt.
4. debug_ll_io_init() maps the SCIF(A) registers to a fixed virtual
address. 0xfdxxxxxx was chosen, as it should lie below VMALLOC_END
= 0xff000000, and must not conflict with the 2 MiB reserved region
at PCI_IO_VIRT_BASE = 0xfee00000.
- On SoCs not using the legacy machine_desc.map_io(),
debug_ll_io_init() is called by the ARM core code.
- On SoCs using the legacy machine_desc.map_io(),
debug_ll_io_init() must be called explicitly. Calls are added
for r8a7740, r8a7779, sh7372, and sh73a0.
This was derived from the r8a7790 version by Laurent Pinchart.
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Tested-by: Simon Horman <horms+renesas@verge.net.au>
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
2014-11-14 15:49:47 +00:00
|
|
|
default 0xffe40000 if DEBUG_RCAR_GEN1_SCIF0
|
|
|
|
|
default 0xffe42000 if DEBUG_RCAR_GEN1_SCIF2
|
2013-07-07 11:32:16 +00:00
|
|
|
default 0xfff36000 if DEBUG_HIGHBANK_UART
|
2022-09-29 13:38:56 +00:00
|
|
|
default 0xfffb0000 if DEBUG_OMAP1UART1
|
|
|
|
|
default 0xfffb0800 if DEBUG_OMAP1UART2
|
|
|
|
|
default 0xfffb9800 if DEBUG_OMAP1UART3
|
2016-01-18 09:45:00 +00:00
|
|
|
default 0xfffe8600 if DEBUG_BCM63XX_UART
|
2016-06-08 10:21:38 +00:00
|
|
|
default 0xffffee00 if DEBUG_AT91_SAM9263_DBGU
|
|
|
|
|
default 0xfffff200 if DEBUG_AT91_RM9200_DBGU
|
2015-01-09 17:34:12 +00:00
|
|
|
depends on ARCH_EP93XX || \
|
|
|
|
|
DEBUG_LL_UART_8250 || DEBUG_LL_UART_PL01X || \
|
2014-09-09 19:38:00 +00:00
|
|
|
DEBUG_UART_8250 || DEBUG_UART_PL01X || DEBUG_MESON_UARTAO || \
|
2015-01-09 17:34:03 +00:00
|
|
|
DEBUG_QCOM_UARTDM || DEBUG_R7S72100_SCIF2 || \
|
2019-06-03 07:37:19 +00:00
|
|
|
DEBUG_R7S9210_SCIF2 || DEBUG_R7S9210_SCIF4 || \
|
ARM: shmobile: Add early debugging support using SCIF(A)
Add serial port debug macros for the SCIF(A) serial ports.
This includes all supported shmobile SoCs, except for EMEV2.
The configuration logic (both Kconfig and #ifdef) is more complicated than
one would expect, for several reasons:
1. Not all SoCs have the same serial devices, and they're not always
at the same addresses.
2. There are two different types: SCIF and SCIFA. Fortunately they can
easily be distinguished by physical address.
3. Not all boards use the same serial port for the console.
The defaults correspond to the boards that are supported in
mainline. If you want to use a different serial port, just change
the value of CONFIG_DEBUG_UART_PHYS, and the rest will auto-adapt.
4. debug_ll_io_init() maps the SCIF(A) registers to a fixed virtual
address. 0xfdxxxxxx was chosen, as it should lie below VMALLOC_END
= 0xff000000, and must not conflict with the 2 MiB reserved region
at PCI_IO_VIRT_BASE = 0xfee00000.
- On SoCs not using the legacy machine_desc.map_io(),
debug_ll_io_init() is called by the ARM core code.
- On SoCs using the legacy machine_desc.map_io(),
debug_ll_io_init() must be called explicitly. Calls are added
for r8a7740, r8a7779, sh7372, and sh73a0.
This was derived from the r8a7790 version by Laurent Pinchart.
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Tested-by: Simon Horman <horms+renesas@verge.net.au>
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
2014-11-14 15:49:47 +00:00
|
|
|
DEBUG_RCAR_GEN1_SCIF0 || DEBUG_RCAR_GEN1_SCIF2 || \
|
2018-03-29 10:42:26 +00:00
|
|
|
DEBUG_RCAR_GEN2_SCIF0 || DEBUG_RCAR_GEN2_SCIF1 || \
|
|
|
|
|
DEBUG_RCAR_GEN2_SCIF2 || DEBUG_RCAR_GEN2_SCIF4 || \
|
2020-04-29 21:56:41 +00:00
|
|
|
DEBUG_RCAR_GEN2_SCIFA2 || \
|
ARM: shmobile: Add early debugging support using SCIF(A)
Add serial port debug macros for the SCIF(A) serial ports.
This includes all supported shmobile SoCs, except for EMEV2.
The configuration logic (both Kconfig and #ifdef) is more complicated than
one would expect, for several reasons:
1. Not all SoCs have the same serial devices, and they're not always
at the same addresses.
2. There are two different types: SCIF and SCIFA. Fortunately they can
easily be distinguished by physical address.
3. Not all boards use the same serial port for the console.
The defaults correspond to the boards that are supported in
mainline. If you want to use a different serial port, just change
the value of CONFIG_DEBUG_UART_PHYS, and the rest will auto-adapt.
4. debug_ll_io_init() maps the SCIF(A) registers to a fixed virtual
address. 0xfdxxxxxx was chosen, as it should lie below VMALLOC_END
= 0xff000000, and must not conflict with the 2 MiB reserved region
at PCI_IO_VIRT_BASE = 0xfee00000.
- On SoCs not using the legacy machine_desc.map_io(),
debug_ll_io_init() is called by the ARM core code.
- On SoCs using the legacy machine_desc.map_io(),
debug_ll_io_init() must be called explicitly. Calls are added
for r8a7740, r8a7779, sh7372, and sh73a0.
This was derived from the r8a7790 version by Laurent Pinchart.
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Tested-by: Simon Horman <horms+renesas@verge.net.au>
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
2014-11-14 15:49:47 +00:00
|
|
|
DEBUG_RMOBILE_SCIFA0 || DEBUG_RMOBILE_SCIFA1 || \
|
2022-09-29 13:33:15 +00:00
|
|
|
DEBUG_RMOBILE_SCIFA4 || \
|
2014-07-25 15:11:24 +00:00
|
|
|
DEBUG_S3C64XX_UART || \
|
2024-09-23 19:49:21 +00:00
|
|
|
DEBUG_BCM63XX_UART || DEBUG_BCMBCA || DEBUG_ASM9260_UART || \
|
2021-01-18 11:53:11 +00:00
|
|
|
DEBUG_DIGICOLOR_UA0 || \
|
2020-12-09 19:42:31 +00:00
|
|
|
DEBUG_AT91_UART || DEBUG_STM32_UART || \
|
2020-12-09 19:45:43 +00:00
|
|
|
DEBUG_STIH41X_ASC2 || DEBUG_STIH41X_SBC_ASC1 || \
|
|
|
|
|
DEBUG_STIH418_SBC_ASC0
|
2013-07-06 23:01:39 +00:00
|
|
|
|
|
|
|
|
config DEBUG_UART_VIRT
|
|
|
|
|
hex "Virtual base address of debug UART"
|
2016-11-14 12:12:35 +00:00
|
|
|
default 0xc881f000 if DEBUG_RV1108_UART2
|
|
|
|
|
default 0xc8821000 if DEBUG_RV1108_UART1
|
|
|
|
|
default 0xc8912000 if DEBUG_RV1108_UART0
|
2013-07-06 23:01:39 +00:00
|
|
|
default 0xe0010fe0 if ARCH_RPC
|
2021-04-09 11:31:16 +00:00
|
|
|
default 0xe0824200 if DEBUG_AT91_SAMA7G5_FLEXCOM3
|
2014-11-24 11:08:28 +00:00
|
|
|
default 0xf0010000 if DEBUG_ASM9260_UART
|
2019-04-17 15:13:27 +00:00
|
|
|
default 0xf0100000 if DEBUG_DIGICOLOR_UA0
|
2013-07-07 11:32:16 +00:00
|
|
|
default 0xf01fb000 if DEBUG_NOMADIK_UART
|
2015-02-24 15:07:55 +00:00
|
|
|
default 0xf0201000 if DEBUG_BCM2835 || DEBUG_BCM2836
|
2021-05-04 17:03:16 +00:00
|
|
|
default 0xf0221000 if DEBUG_MSTARV7_PMUART
|
2014-02-03 23:01:44 +00:00
|
|
|
default 0xf1000300 if DEBUG_BCM_5301X
|
2017-09-28 23:14:59 +00:00
|
|
|
default 0xf1000400 if DEBUG_BCM_HR2
|
2014-11-04 07:30:54 +00:00
|
|
|
default 0xf1002000 if DEBUG_MT8127_UART0
|
2014-08-18 14:58:00 +00:00
|
|
|
default 0xf1006000 if DEBUG_MT6589_UART0
|
2014-11-04 07:30:54 +00:00
|
|
|
default 0xf1009000 if DEBUG_MT8135_UART3
|
2018-05-30 13:19:55 +00:00
|
|
|
default 0xf1023000 if DEBUG_BCM_IPROC_UART3
|
2015-12-03 16:54:05 +00:00
|
|
|
default 0xf11f1000 if DEBUG_VERSATILE
|
|
|
|
|
default 0xf1600000 if DEBUG_INTEGRATOR
|
2013-07-06 23:01:39 +00:00
|
|
|
default 0xf1c28000 if DEBUG_SUNXI_UART0
|
|
|
|
|
default 0xf1c28400 if DEBUG_SUNXI_UART1
|
2014-06-20 14:52:51 +00:00
|
|
|
default 0xf1f02800 if DEBUG_SUNXI_R_UART
|
2015-12-03 17:16:45 +00:00
|
|
|
default 0xf31004c0 if DEBUG_MESON_UARTAO
|
2015-12-03 16:54:05 +00:00
|
|
|
default 0xf4090000 if DEBUG_LPC32XX
|
2015-12-03 16:54:05 +00:00
|
|
|
default 0xf4200000 if DEBUG_GEMINI
|
2014-10-07 19:18:14 +00:00
|
|
|
default 0xf6200000 if DEBUG_PXA_UART1
|
2014-09-24 14:48:56 +00:00
|
|
|
default 0xf7000000 if DEBUG_SUN9I_UART0
|
2014-07-25 15:11:24 +00:00
|
|
|
default 0xf7000000 if DEBUG_S3C64XX_UART && DEBUG_S3C_UART0
|
|
|
|
|
default 0xf7000400 if DEBUG_S3C64XX_UART && DEBUG_S3C_UART1
|
|
|
|
|
default 0xf7000800 if DEBUG_S3C64XX_UART && DEBUG_S3C_UART2
|
|
|
|
|
default 0xf7000c00 if DEBUG_S3C64XX_UART && DEBUG_S3C_UART3
|
2016-06-08 10:21:38 +00:00
|
|
|
default 0xf7020000 if DEBUG_AT91_SAMA5D2_UART1
|
2013-09-09 12:10:54 +00:00
|
|
|
default 0xf7fc9000 if DEBUG_BERLIN_UART
|
2013-12-20 07:01:41 +00:00
|
|
|
default 0xf8007000 if DEBUG_HIP04_UART
|
2013-07-07 11:32:16 +00:00
|
|
|
default 0xf8009000 if DEBUG_VEXPRESS_UART0_CA9
|
|
|
|
|
default 0xf8090000 if DEBUG_VEXPRESS_UART0_RS1
|
2016-06-08 10:21:38 +00:00
|
|
|
default 0xf8ffee00 if DEBUG_AT91_SAM9263_DBGU
|
|
|
|
|
default 0xf8fff200 if DEBUG_AT91_RM9200_DBGU
|
2020-12-09 19:45:43 +00:00
|
|
|
default 0xf9530000 if DEBUG_STIH418_SBC_ASC0
|
2017-07-17 05:10:14 +00:00
|
|
|
default 0xf9e09000 if DEBUG_AM33XXUART1
|
2017-07-17 05:10:14 +00:00
|
|
|
default 0xfa020000 if DEBUG_OMAP4UART3 || DEBUG_TI81XXUART1
|
|
|
|
|
default 0xfa022000 if DEBUG_TI81XXUART2
|
|
|
|
|
default 0xfa024000 if DEBUG_TI81XXUART3
|
arm: debug: reuse the config DEBUG_OMAP2UART{1,2} for OMAP{3,4,5}
Commit d2b310b0234c ("ARM: debug: Use generic 8250 debug_ll for omap2 and
omap3/4/5 common uarts") adds address definitions of DEBUG_UART_PHYS for
OMAP2, OMAP3, OMAP4 and OMAP5 in ./arch/arm/Kconfig.debug.
These definitions depend on DEBUG_OMAP{2,3,4,5}UART{1,2}; however, only
DEBUG_OMAP2UART{1,2} are defined in ./arch/arm/Kconfig.debug, and
DEBUG_OMAP{3,4,5}UART{1,2} are not defined. Hence, the script
./scripts/checkkconfigsymbols.py warns here on non-existing symbols.
Simply reuse the config DEBUG_OMAP2UART{1,2}; there is no need to define
separate config symbols for OMAP{3,4,5}. So, just delete the dead
references to DEBUG_OMAP{3,4,5}UART{1,2}.
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Link: https://lore.kernel.org/r/20231025112136.3445-1-lukas.bulwahn@gmail.com
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
2023-10-25 11:21:36 +00:00
|
|
|
default 0xfa06a000 if DEBUG_OMAP2UART1
|
|
|
|
|
default 0xfa06c000 if DEBUG_OMAP2UART2
|
2017-06-14 07:31:13 +00:00
|
|
|
default 0xfa06e000 if DEBUG_OMAP2UART3 || DEBUG_OMAP4UART4
|
2014-04-14 13:47:34 +00:00
|
|
|
default 0xfa71e000 if DEBUG_QCOM_UARTDM
|
2013-07-07 11:32:16 +00:00
|
|
|
default 0xfb009000 if DEBUG_REALVIEW_STD_PORT
|
2016-06-08 10:21:38 +00:00
|
|
|
default 0xfb00c000 if DEBUG_AT91_SAMA5D4_USART3
|
2017-06-14 07:31:13 +00:00
|
|
|
default 0xfb020000 if DEBUG_OMAP3UART3
|
|
|
|
|
default 0xfb042000 if DEBUG_OMAP3UART4
|
2013-07-07 11:32:16 +00:00
|
|
|
default 0xfb10c000 if DEBUG_REALVIEW_PB1176_PORT
|
2016-01-18 09:45:00 +00:00
|
|
|
default 0xfcfe8600 if DEBUG_BCM63XX_UART
|
2015-12-03 16:54:05 +00:00
|
|
|
default 0xfd000000 if DEBUG_SPEAR3XX || DEBUG_SPEAR13XX
|
2022-05-13 09:25:30 +00:00
|
|
|
default 0xfd064200 if DEBUG_AT91_LAN966_FLEXCOM
|
2020-12-09 19:42:31 +00:00
|
|
|
default 0xfd531000 if DEBUG_STIH41X_SBC_ASC1
|
2015-03-12 11:53:04 +00:00
|
|
|
default 0xfd883000 if DEBUG_ALPINE_UART0
|
2020-12-09 19:42:31 +00:00
|
|
|
default 0xfdd32000 if DEBUG_STIH41X_ASC2
|
2020-02-03 14:04:25 +00:00
|
|
|
default 0xfe010000 if STM32MP1_DEBUG_UART
|
2013-07-06 23:01:39 +00:00
|
|
|
default 0xfe017000 if DEBUG_MMP_UART2
|
|
|
|
|
default 0xfe018000 if DEBUG_MMP_UART3
|
2013-07-07 11:32:16 +00:00
|
|
|
default 0xfe100000 if DEBUG_IMX23_UART || DEBUG_IMX28_UART
|
2013-12-23 08:00:01 +00:00
|
|
|
default 0xfe300000 if DEBUG_BCM_KONA_UART
|
2024-09-23 19:49:21 +00:00
|
|
|
default 0xfe300640 if DEBUG_BCMBCA
|
2014-04-11 03:40:58 +00:00
|
|
|
default 0xfeb00000 if DEBUG_HI3620_UART || DEBUG_HIX5HD2_UART
|
2013-07-06 23:01:39 +00:00
|
|
|
default 0xfeb24000 if DEBUG_RK3X_UART0
|
|
|
|
|
default 0xfeb26000 if DEBUG_RK3X_UART1
|
2013-07-07 15:05:49 +00:00
|
|
|
default 0xfeb30c00 if DEBUG_KEYSTONE_UART0
|
|
|
|
|
default 0xfeb31000 if DEBUG_KEYSTONE_UART1
|
2015-03-09 20:48:31 +00:00
|
|
|
default 0xfec02000 if DEBUG_SOCFPGA_UART0
|
2018-10-09 11:28:37 +00:00
|
|
|
default 0xfec02100 if DEBUG_SOCFPGA_ARRIA10_UART1
|
|
|
|
|
default 0xfec03000 if DEBUG_SOCFPGA_CYCLONE5_UART1
|
2019-07-31 19:56:55 +00:00
|
|
|
default 0xfec12000 if DEBUG_MVEBU_UART0 || DEBUG_MVEBU_UART0_ALTERNATE
|
2015-01-08 17:38:04 +00:00
|
|
|
default 0xfec12100 if DEBUG_MVEBU_UART1_ALTERNATE
|
2014-06-28 11:31:17 +00:00
|
|
|
default 0xfec90000 if DEBUG_RK32_UART2
|
2013-07-07 15:18:34 +00:00
|
|
|
default 0xfed0c000 if DEBUG_DAVINCI_DA8XX_UART1
|
2020-09-29 14:14:44 +00:00
|
|
|
default 0xfed0d000 if DEBUG_DAVINCI_DA8XX_UART2 || DEBUG_SD5203_UART
|
2014-04-12 05:07:23 +00:00
|
|
|
default 0xfed60000 if DEBUG_RK29_UART0
|
|
|
|
|
default 0xfed64000 if DEBUG_RK29_UART1 || DEBUG_RK3X_UART2
|
|
|
|
|
default 0xfed68000 if DEBUG_RK29_UART2 || DEBUG_RK3X_UART3
|
2015-12-03 15:19:22 +00:00
|
|
|
default 0xfedc0000 if DEBUG_EP93XX
|
2015-12-03 17:27:53 +00:00
|
|
|
default 0xfee003f8 if DEBUG_FOOTBRIDGE_COM1
|
2013-07-07 11:32:16 +00:00
|
|
|
default 0xfee20000 if DEBUG_NSPIRE_CLASSIC_UART || DEBUG_NSPIRE_CX_UART
|
2021-04-29 21:25:11 +00:00
|
|
|
default 0xfec00000 if ARCH_IXP4XX && !CPU_BIG_ENDIAN
|
|
|
|
|
default 0xfec00003 if ARCH_IXP4XX && CPU_BIG_ENDIAN
|
2014-04-12 05:07:23 +00:00
|
|
|
default 0xfef36000 if DEBUG_HIGHBANK_UART
|
2022-09-29 13:38:56 +00:00
|
|
|
default 0xff0b0000 if DEBUG_OMAP1UART1
|
|
|
|
|
default 0xff0b0800 if DEBUG_OMAP1UART2
|
|
|
|
|
default 0xff0b9800 if DEBUG_OMAP1UART3
|
2014-12-24 03:09:56 +00:00
|
|
|
default 0xffd01000 if DEBUG_HIP01_UART
|
2013-07-07 11:32:16 +00:00
|
|
|
default DEBUG_UART_PHYS if !MMU
|
2013-07-07 14:29:38 +00:00
|
|
|
depends on DEBUG_LL_UART_8250 || DEBUG_LL_UART_PL01X || \
|
2014-09-09 19:38:00 +00:00
|
|
|
DEBUG_UART_8250 || DEBUG_UART_PL01X || DEBUG_MESON_UARTAO || \
|
2022-09-29 13:33:15 +00:00
|
|
|
DEBUG_QCOM_UARTDM || \
|
2014-07-25 15:11:24 +00:00
|
|
|
DEBUG_S3C64XX_UART || \
|
2024-09-23 19:49:21 +00:00
|
|
|
DEBUG_BCM63XX_UART || DEBUG_BCMBCA || DEBUG_ASM9260_UART || \
|
2021-01-18 11:53:11 +00:00
|
|
|
DEBUG_DIGICOLOR_UA0 || \
|
2020-12-09 19:42:31 +00:00
|
|
|
DEBUG_AT91_UART || DEBUG_STM32_UART || \
|
2020-12-09 19:45:43 +00:00
|
|
|
DEBUG_STIH41X_ASC2 || DEBUG_STIH41X_SBC_ASC1 || \
|
|
|
|
|
DEBUG_STIH418_SBC_ASC0
|
2013-07-06 23:01:39 +00:00
|
|
|
|
2013-07-06 22:13:15 +00:00
|
|
|
config DEBUG_UART_8250_SHIFT
|
|
|
|
|
int "Register offset shift for the 8250 debug UART"
|
2013-07-07 14:29:38 +00:00
|
|
|
depends on DEBUG_LL_UART_8250 || DEBUG_UART_8250
|
2022-09-29 13:31:18 +00:00
|
|
|
default 0 if DEBUG_FOOTBRIDGE_COM1 || DEBUG_BCM_5301X || \
|
2023-01-12 08:37:46 +00:00
|
|
|
DEBUG_BCM_HR2
|
2021-05-04 17:03:16 +00:00
|
|
|
default 3 if DEBUG_MSTARV7_PMUART
|
2013-07-06 22:13:15 +00:00
|
|
|
default 2
|
2013-07-06 21:59:10 +00:00
|
|
|
|
2013-07-07 10:42:46 +00:00
|
|
|
config DEBUG_UART_8250_WORD
|
|
|
|
|
bool "Use 32-bit accesses for 8250 UART"
|
2013-07-07 14:29:38 +00:00
|
|
|
depends on DEBUG_LL_UART_8250 || DEBUG_UART_8250
|
2013-07-07 10:42:46 +00:00
|
|
|
depends on DEBUG_UART_8250_SHIFT >= 2
|
2020-12-10 20:03:13 +00:00
|
|
|
default y if DEBUG_SOCFPGA_UART0 || DEBUG_SOCFPGA_ARRIA10_UART1 || \
|
2018-10-09 11:28:37 +00:00
|
|
|
DEBUG_SOCFPGA_CYCLONE5_UART1 || DEBUG_KEYSTONE_UART0 || \
|
|
|
|
|
DEBUG_KEYSTONE_UART1 || DEBUG_ALPINE_UART0 || \
|
2022-09-29 13:38:29 +00:00
|
|
|
DEBUG_DAVINCI_DA8XX_UART1 || DEBUG_DAVINCI_DA8XX_UART2 || \
|
|
|
|
|
DEBUG_BCM_IPROC_UART3 || DEBUG_BCM_KONA_UART || \
|
|
|
|
|
DEBUG_RK32_UART2
|
2013-07-07 10:42:46 +00:00
|
|
|
|
2016-02-05 09:49:22 +00:00
|
|
|
config DEBUG_UART_8250_PALMCHIP
|
|
|
|
|
bool "8250 UART is Palmchip BK-310x"
|
|
|
|
|
depends on DEBUG_LL_UART_8250 || DEBUG_UART_8250
|
|
|
|
|
help
|
|
|
|
|
Palmchip provides a UART implementation compatible with 16550
|
|
|
|
|
except for having a different register layout. Say Y here if
|
|
|
|
|
the debug UART is of this type.
|
|
|
|
|
|
2013-03-14 07:48:06 +00:00
|
|
|
config DEBUG_UNCOMPRESS
|
2017-11-16 11:46:22 +00:00
|
|
|
bool "Enable decompressor debugging via DEBUG_LL output"
|
2022-07-27 12:08:24 +00:00
|
|
|
depends on !ARCH_MULTIPLATFORM
|
2022-07-26 12:16:37 +00:00
|
|
|
depends on !(ARCH_FOOTBRIDGE || ARCH_RPC || ARCH_SA1100)
|
2017-11-16 11:46:22 +00:00
|
|
|
depends on DEBUG_LL && !DEBUG_OMAP2PLUS_UART && \
|
2016-06-28 19:18:51 +00:00
|
|
|
(!DEBUG_TEGRA_UART || !ZBOOT_ROM) && \
|
2020-12-11 08:57:25 +00:00
|
|
|
!DEBUG_BRCMSTB_UART && !DEBUG_SEMIHOSTING
|
2013-07-17 16:54:27 +00:00
|
|
|
help
|
2024-01-03 11:04:09 +00:00
|
|
|
Say Y here to enable debug output in the decompressor code, using
|
|
|
|
|
the selected DEBUG_LL output method.
|
2013-03-14 07:48:06 +00:00
|
|
|
|
2013-03-14 07:47:27 +00:00
|
|
|
config UNCOMPRESS_INCLUDE
|
|
|
|
|
string
|
2022-07-26 12:16:37 +00:00
|
|
|
default "mach/uncompress.h" if ARCH_FOOTBRIDGE || ARCH_RPC || ARCH_SA1100
|
|
|
|
|
default "debug/uncompress.h"
|
2013-03-14 07:47:27 +00:00
|
|
|
|
2009-12-09 10:02:18 +00:00
|
|
|
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.
|
|
|
|
|
|
2011-08-27 11:36:58 +00:00
|
|
|
config ARM_KPROBES_TEST
|
|
|
|
|
tristate "Kprobes test module"
|
|
|
|
|
depends on KPROBES && MODULES
|
|
|
|
|
help
|
|
|
|
|
Perform tests of kprobes API and instruction set simulation.
|
|
|
|
|
|
2012-07-06 14:43:03 +00:00
|
|
|
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.
|
|
|
|
|
|
2015-03-30 20:13:41 +00:00
|
|
|
source "drivers/hwtracing/coresight/Kconfig"
|