linux-kernel - Re: [PATCH 0/3] tty: serial: 8250

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 19 Jan 2017 14:24:48 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Tony Lindgren <tony@...mide.com>
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

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.

thanks,

greg k-h