[PATCH 09/16] tty: serial: 8250_dma: Add a TX trigger workaround for AM33xx
From: Frans Klaver <hidden>
Date: 2014-09-29 10:30:50
Also in:
linux-omap, linux-serial, lkml
Possibly related (same subject, not in this thread)
- 2014-09-29 · Re: [PATCH 09/16] tty: serial: 8250_dma: Add a TX trigger workaround for AM33xx · Sebastian Andrzej Siewior <bigeasy@linutronix.de>
- 2014-09-25 · Re: [PATCH 09/16] tty: serial: 8250_dma: Add a TX trigger workaround for AM33xx · Sebastian Andrzej Siewior <bigeasy@linutronix.de>
- 2014-09-22 · Re: [PATCH 09/16] tty: serial: 8250_dma: Add a TX trigger workaround for AM33xx · Heikki Krogerus <heikki.krogerus@linux.intel.com>
- 2014-09-19 · Re: [PATCH 09/16] tty: serial: 8250_dma: Add a TX trigger workaround for AM33xx · Peter Hurley <hidden>
- 2014-09-19 · Re: [PATCH 09/16] tty: serial: 8250_dma: Add a TX trigger workaround for AM33xx · Sebastian Andrzej Siewior <bigeasy@linutronix.de>
On Mon, Sep 29, 2014 at 11:54:40AM +0200, Sebastian Andrzej Siewior wrote:
There is a patch named "ARM: edma: unconditionally ack the error interrupt". I have the feeling that this is not really required once we delay set_termios. I couldn't reproduce the bug with beagleblack with my usual test case.
I think so too. I didn't need it either.
For your "too much work for irq" problem: Could you add trace_printk() in tx/rx dma start/complete, and irq routine? The interresting part is what is the irq routine doing once entered. It might be a condition that is ignored at first and "acked" later while serving another event. Or it is really doing something and this is more or less "legal".
I'll have a look at that.
quoted
Thanks, FransSebastian