History

Revert "OMAP: UART: Keep the TX fifo full when possible"

This reverts commit c4415084218c68c5ee2fc583431e89a78d896b19. Kevin writes: Hmm, another OMAP serial patch that wasn't Cc'd to linux-omap where OMAP users might have seen it. :( I just bisected a strange problem in linux-next on OMAP3 down to this patch. Reverting it fixes the problem. On OMAP3530 Beagle and Overo, after boot, doing a 'cat /proc/cpuinfo' was not returning to a prompt, suggesting something strange with the FIFO. Hitting return gets me back to a prompt. Greg, this one should also be dropped from tty-next until it can be further investgated and the problem solved.

Greg Kroah-Hartman committed 13 years ago

Commit 355fe561 parent 7b013e42 files · +1 −3Browse files

Showing the changes to include/uapi/linux (1 of 2 files). Show all

Unified · Split

include/uapi/linux/serial_reg.h+0−1
@@ -366,7 +366,6 @@ · 365 unmodified lines
366#define UART_OMAP_MDR1_FIR_MODE 0x05 /* FIR mode */366#define UART_OMAP_MDR1_FIR_MODE 0x05 /* FIR mode */
367#define UART_OMAP_MDR1_CIR_MODE 0x06 /* CIR mode */367#define UART_OMAP_MDR1_CIR_MODE 0x06 /* CIR mode */
368#define UART_OMAP_MDR1_DISABLE 0x07 /* Disable (default state) */368#define UART_OMAP_MDR1_DISABLE 0x07 /* Disable (default state) */
369#define UART_OMAP_TXFIFO_LVL 0x1A /* TX FIFO fullness */
370 369
371/*370/*
372 * These are definitions for the Exar XR17V35X and XR17(C|D)15X371 * These are definitions for the Exar XR17V35X and XR17(C|D)15X