On 08/15/2014 04:28 PM, Tony Lindgren wrote:
* Sebastian Andrzej Siewior bige...@linutronix.de [140815 12:16]:
On 08/15/2014 08:17 PM, Lennart Sorensen wrote:
Are you saying that with the new driver you have to respond to the RX
irq faster than before to avoid overflows? It is not quite
On Mon, Aug 18, 2014 at 11:15:17AM -0400, Peter Hurley wrote:
On 08/15/2014 04:28 PM, Tony Lindgren wrote:
* Sebastian Andrzej Siewior bige...@linutronix.de [140815 12:16]:
On 08/15/2014 08:17 PM, Lennart Sorensen wrote:
Are you saying that with the new driver you have to respond to the
* Tony Lindgren | 2014-08-15 13:28:27 [-0700]:
It configured the trigger levels to 1 for RX and 16 for TX.
Hmm that weird RX trigger level is a workaround for lost characters.
See commit 0ba5f66836 (tty: serial: OMAP: use a 1-byte RX FIFO
threshold in PIO mode :)
There's paste test in that
This is my complete queue fo the omap serial driver based on the 8250 core
code. I played with it on beagle bone, am335x-evm and dra7xx including DMA.
The uncertain remain the runtime-pm pieces.
I hacked a small serial testing application which sent 10x 4KiB of data in
raw mode. The number of
On Fri, Aug 15, 2014 at 07:42:28PM +0200, Sebastian Andrzej Siewior wrote:
This is my complete queue fo the omap serial driver based on the 8250 core
code. I played with it on beagle bone, am335x-evm and dra7xx including DMA.
The uncertain remain the runtime-pm pieces.
I hacked a small serial
On 08/15/2014 08:17 PM, Lennart Sorensen wrote:
Are you saying that with the new driver you have to respond to the RX
irq faster than before to avoid overflows? It is not quite clear.
Yes. The irq fires 46 bytes giving you 16 bytes buffer before overflow
vs 63 bytes buffer the old one had.
* Sebastian Andrzej Siewior bige...@linutronix.de [140815 12:16]:
On 08/15/2014 08:17 PM, Lennart Sorensen wrote:
Are you saying that with the new driver you have to respond to the RX
irq faster than before to avoid overflows? It is not quite clear.
Yes. The irq fires 46 bytes giving
