[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b27b95a9-40b8-ebef-3457-ce87db6b26e5@ti.com>
Date: Tue, 17 Jan 2017 11:36:17 +0530
From: Vignesh R <vigneshr@...com>
To: Tony Lindgren <tony@...mide.com>
CC: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jiri Slaby <jslaby@...e.com>,
Peter Hurley <peter@...leysoftware.com>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
"linux-serial@...r.kernel.org" <linux-serial@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>
Subject: Re: [PATCH 0/3] tty: serial: 8250_omap: Enable DMA support
On Friday 13 January 2017 11:50 PM, 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.
>
Yes, I did face the same issue on omap5 using 8250_omap driver for
console. Looks like this bug has existed all along.
> 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.
>
True.
--
Regards
Vignesh
Powered by blists - more mailing lists