Revert "OMAP: UART: Keep the TX fifo full when possible"
This reverts commit c441508421.
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.
Reported-by: Kevin Hilman <khilman@linaro.org>
Cc: Dmitry Fink <finik@ti.com>
Cc: Alexander Savchenko <oleksandr.savchenko@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
This commit is contained in:
parent
7b013e440a
commit
355fe568e2
2 changed files with 1 additions and 3 deletions
|
|
@ -366,7 +366,6 @@
|
|||
#define UART_OMAP_MDR1_FIR_MODE 0x05 /* FIR mode */
|
||||
#define UART_OMAP_MDR1_CIR_MODE 0x06 /* CIR mode */
|
||||
#define UART_OMAP_MDR1_DISABLE 0x07 /* Disable (default state) */
|
||||
#define UART_OMAP_TXFIFO_LVL 0x1A /* TX FIFO fullness */
|
||||
|
||||
/*
|
||||
* These are definitions for the Exar XR17V35X and XR17(C|D)15X
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue