[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170119145423.GQ7403@atomide.com>
Date: Thu, 19 Jan 2017 06:54:23 -0800
From: Tony Lindgren <tony@...mide.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Vignesh R <vigneshr@...com>, Jiri Slaby <jslaby@...e.com>,
Peter Hurley <peter@...leysoftware.com>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
linux-serial@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-omap@...r.kernel.org
Subject: Re: [PATCH 0/3] tty: serial: 8250_omap: Enable DMA support
* Greg Kroah-Hartman <gregkh@...uxfoundation.org> [170119 05:25]:
> On Fri, Jan 13, 2017 at 10:20:21AM -0800, Tony Lindgren wrote:
> > * Vignesh R <vigneshr@...com> [170113 00:03]:
> > > This patch series re enables DMA support for UART 8250_omap driver.
> > >
> > > Tested on AM335x, AM437x that use EDMA and OMAP5 and DRA74 EVM with
> > > SDMA.
> >
> > Is 8250_omap serial console working for you on omap5 in general?
> >
> > I've noticed that it's really unresponsive for me as if the FIFO
> > interrupt was not working. For example logging in might take several
> > attempts and a long time with each character showing up much later
> > after some timeout.
> >
> > TX on the uart on omap5 seems to work OK, I do see all the console
> > messages fine. And these patches do not make the issue better or
> > worse.
>
> Ok, I'm dropping them from my review queue then.
It turned out to be not related to this set of patches, Vignesh
posted a fix for it. For this set:
Acked-by: Tony Lindgren <tony@...mide.com>
Powered by blists - more mailing lists