2 # Serial device configuration
7 config REQUIRE_SERIAL_CONSOLE
8 bool "Require a serial port for console"
9 # Running without a serial console is not supported by the
14 Require a serial port for the console, and panic if none is found
15 during serial port initialization (default y). Set this to n on
16 boards which have no debug serial port whatsoever.
19 bool "Provide a serial driver"
23 In very space-constrained devices even the full UART driver is too
24 large. In this case the debug UART can still be used in some cases.
25 This option enables the full UART in U-Boot, so if is it disabled,
26 the full UART driver will be omitted, thus saving space.
28 config SPL_SERIAL_PRESENT
29 bool "Provide a serial driver in SPL"
33 In very space-constrained devices even the full UART driver is too
34 large. In this case the debug UART can still be used in some cases.
35 This option enables the full UART in SPL, so if is it disabled,
36 the full UART driver will be omitted, thus saving space.
39 bool "Enable Driver Model for serial drivers"
42 Enable driver model for serial. This replaces
43 drivers/serial/serial.c with the serial uclass, which
44 implements serial_putc() etc. The uclass interface is
45 defined in include/serial.h.
48 bool "Enable an early debug UART for debugging"
50 The debug UART is intended for use very early in U-Boot to debug
51 problems when an ICE or other debug mechanism is not available.
54 - Make sure your UART supports this interface
55 - Enable CONFIG_DEBUG_UART
56 - Enable the CONFIG for your UART to tell it to provide this interface
57 (e.g. CONFIG_DEBUG_UART_NS16550)
58 - Define the required settings as needed (see below)
59 - Call debug_uart_init() before use
60 - Call debug_uart_putc() to output a character
62 Depending on your platform it may be possible to use this UART before
65 If your UART does not support this interface you can probably add
66 support quite easily. Remember that you cannot use driver model and
67 it is preferred to use no stack.
69 You must not use this UART once driver model is working and the
70 serial drivers are up and running (done in serial_init()). Otherwise
71 the drivers may conflict and you will get strange output.
74 prompt "Select which UART will provide the debug UART"
76 default DEBUG_UART_NS16550
78 config DEBUG_UART_ALTERA_JTAGUART
79 bool "Altera JTAG UART"
81 Select this to enable a debug UART using the altera_jtag_uart driver.
82 You will need to provide parameters to make this work. The driver will
83 be available until the real driver model serial is running.
85 config DEBUG_UART_ALTERA_UART
88 Select this to enable a debug UART using the altera_uart driver.
89 You will need to provide parameters to make this work. The driver will
90 be available until the real driver model serial is running.
92 config DEBUG_UART_AR933X
93 bool "QCA/Atheros ar933x"
94 depends on AR933X_UART
96 Select this to enable a debug UART using the ar933x uart driver.
97 You will need to provide parameters to make this work. The
98 driver will be available until the real driver model serial is
101 config DEBUG_UART_NS16550
104 Select this to enable a debug UART using the ns16550 driver. You
105 will need to provide parameters to make this work. The driver will
106 be available until the real driver model serial is running.
108 config DEBUG_EFI_CONSOLE
112 Select this to enable a debug console which calls back to EFI to
113 output to the console. This can be useful for early debugging of
114 U-Boot when running on top of EFI (Extensive Firmware Interface).
115 This is a type of BIOS used by PCs.
117 config DEBUG_UART_S5P
120 Select this to enable a debug UART using the serial_s5p driver. You
121 will need to provide parameters to make this work. The driver will
122 be available until the real driver-model serial is running.
124 config DEBUG_UART_MESON
126 depends on MESON_SERIAL
128 Select this to enable a debug UART using the serial_meson driver. You
129 will need to provide parameters to make this work. The driver will
130 be available until the real driver-model serial is running.
132 config DEBUG_UART_UARTLITE
133 bool "Xilinx Uartlite"
135 Select this to enable a debug UART using the serial_uartlite driver.
136 You will need to provide parameters to make this work. The driver will
137 be available until the real driver-model serial is running.
139 config DEBUG_UART_ARM_DCC
142 Select this to enable a debug UART using the ARM JTAG DCC port.
143 The DCC port can be used for very early debugging and doesn't require
144 any additional setting like address/baudrate/clock. On systems without
145 any serial interface this is the easiest way how to get console.
146 Every ARM core has own DCC port which is the part of debug interface.
147 This port is available at least on ARMv6, ARMv7, ARMv8 and XScale
150 config DEBUG_UART_ZYNQ
153 Select this to enable a debug UART using the serial_zynq driver. You
154 will need to provide parameters to make this work. The driver will
155 be available until the real driver-model serial is running.
157 config DEBUG_UART_APBUART
159 bool "Gaisler APBUART"
161 Select this to enable a debug UART using the serial_leon3 driver. You
162 will need to provide parameters to make this work. The driver will
163 be available until the real driver model serial is running.
165 config DEBUG_UART_PL010
168 Select this to enable a debug UART using the pl01x driver with the
169 PL010 UART type. You will need to provide parameters to make this
170 work. The driver will be available until the real driver model
173 config DEBUG_UART_PL011
176 Select this to enable a debug UART using the pl01x driver with the
177 PL011 UART type. You will need to provide parameters to make this
178 work. The driver will be available until the real driver model
181 config DEBUG_UART_PIC32
182 bool "Microchip PIC32"
183 depends on PIC32_SERIAL
185 Select this to enable a debug UART using the serial_pic32 driver. You
186 will need to provide parameters to make this work. The driver will
187 be available until the real driver model serial is running.
189 config DEBUG_UART_UNIPHIER
190 bool "UniPhier on-chip UART"
191 depends on ARCH_UNIPHIER
193 Select this to enable a debug UART using the UniPhier on-chip UART.
194 You will need to provide DEBUG_UART_BASE to make this work. The
195 driver will be available until the real driver-model serial is
200 config DEBUG_UART_BASE
201 hex "Base address of UART"
202 depends on DEBUG_UART
204 This is the base address of your UART for memory-mapped UARTs.
206 A default should be provided by your board, but if not you will need
207 to use the correct value here.
209 config DEBUG_UART_CLOCK
210 int "UART input clock"
211 depends on DEBUG_UART
213 The UART input clock determines the speed of the internal UART
214 circuitry. The baud rate is derived from this by dividing the input
217 A default should be provided by your board, but if not you will need
218 to use the correct value here.
220 config DEBUG_UART_SHIFT
221 int "UART register shift"
222 depends on DEBUG_UART
223 default 0 if DEBUG_UART
225 Some UARTs (notably ns16550) support different register layouts
226 where the registers are spaced either as bytes, words or some other
227 value. Use this value to specify the shift to use, where 0=byte
228 registers, 2=32-bit word registers, etc.
230 config DEBUG_UART_BOARD_INIT
231 bool "Enable board-specific debug UART init"
232 depends on DEBUG_UART
234 Some boards need to set things up before the debug UART can be used.
235 On these boards a call to debug_uart_init() is insufficient. When
236 this option is enabled, the function board_debug_uart_init() will
237 be called when debug_uart_init() is called. You can put any code
238 here that is needed to set up the UART ready for use, such as set
239 pin multiplexing or enable clocks.
241 config DEBUG_UART_ANNOUNCE
242 bool "Show a message when the debug UART starts up"
243 depends on DEBUG_UART
245 Enable this option to show a message when the debug UART is ready
246 for use. You will see a message like "<debug_uart> " as soon as
247 U-Boot has the UART ready for use (i.e. your code calls
248 debug_uart_init()). This can be useful just as a check that
249 everything is working.
251 config DEBUG_UART_SKIP_INIT
252 bool "Skip UART initialization"
254 Select this if the UART you want to use for debug output is already
255 initialized by the time U-Boot starts its execution.
257 config ALTERA_JTAG_UART
258 bool "Altera JTAG UART support"
261 Select this to enable an JTAG UART for Altera devices.The JTAG UART
262 core implements a method to communicate serial character streams
263 between a host PC and a Qsys system on an Altera FPGA. Please find
264 details on the "Embedded Peripherals IP User Guide" of Altera.
266 config ALTERA_JTAG_UART_BYPASS
267 bool "Bypass output when no connection"
268 depends on ALTERA_JTAG_UART
270 Bypass console output and keep going even if there is no JTAG
271 terminal connection with the host. The console output will resume
272 once the JTAG terminal is connected. Without the bypass, the console
273 output will wait forever until a JTAG terminal is connected. If you
277 bool "Altera UART support"
280 Select this to enable an UART for Altera devices. Please find
281 details on the "Embedded Peripherals IP User Guide" of Altera.
284 bool "QCA/Atheros ar933x UART support"
285 depends on DM_SERIAL && SOC_AR933X
287 Select this to enable UART support for QCA/Atheros ar933x
288 devices. This driver uses driver model and requires a device
289 tree binding to operate, please refer to the document at
290 doc/device-tree-bindings/serial/qca,ar9330-uart.txt.
293 bool "Freescale LPUART support"
295 Select this to enable a Low Power UART for Freescale VF610 and
296 QorIQ Layerscape devices.
299 bool "Support for Microchip PIC32 on-chip UART"
300 depends on DM_SERIAL && MACH_PIC32
303 Support for the UART found on Microchip PIC32 SoC's.
306 bool "NS16550 UART or compatible"
308 Support NS16550 UART or compatible. This can be enabled in the
309 device tree with the correct input clock frequency. If the input
310 clock frequency is not defined in the device tree, the macro
311 CONFIG_SYS_NS16550_CLK defined in a legacy board header file will
312 be used. It can be a constant or a function to get clock, eg,
315 config SANDBOX_SERIAL
316 bool "Sandbox UART support"
319 Select this to enable a seral UART for sandbox. This is required to
320 operate correctly, otherwise you will see no serial output from
321 sandbox. The emulated UART will display to the console and console
322 input will be fed into the UART. This allows you to interact with
325 The operation of the console is controlled by the -t command-line
326 flag. In raw mode, U-Boot sees all characters from the terminal
327 before they are processed, including Ctrl-C. In cooked mode, Ctrl-C
328 is processed by the terminal, and terminates U-Boot. Valid options
331 -t raw-with-sigs Raw mode, Ctrl-C will terminate U-Boot
332 -t raw Raw mode, Ctrl-C is processed by U-Boot
333 -t cooked Cooked mode, Ctrl-C terminates
335 config UNIPHIER_SERIAL
336 bool "Support for UniPhier on-chip UART"
337 depends on ARCH_UNIPHIER
339 If you have a UniPhier based board and want to use the on-chip
340 serial ports, say Y to this option. If unsure, say N.
342 config XILINX_UARTLITE
343 bool "Xilinx Uarlite support"
344 depends on DM_SERIAL && (MICROBLAZE || ARCH_ZYNQ || ARCH_ZYNQMP || 4xx)
346 If you have a Xilinx based board and want to use the uartlite
347 serial ports, say Y to this option. If unsure, say N.
350 bool "Support for Amlogic Meson UART"
351 depends on DM_SERIAL && ARCH_MESON
353 If you have an Amlogic Meson based board and want to use the on-chip
354 serial ports, say Y to this option. If unsure, say N.
357 bool "Qualcomm on-chip UART"
360 Support Data Mover UART used on Qualcomm Snapdragon SoCs.
361 It should support all Qualcomm devices with UARTDM version 1.4,
362 for example APQ8016 and MSM8916.
363 Single baudrate is supported in current implementation (115200).