From: Vignesh R <vigneshr@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
Peter Hurley <peter@hurleysoftware.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 0/3] tty: serial: 8250_omap: Enable DMA support
Date: Tue, 17 Jan 2017 11:36:17 +0530 [thread overview]
Message-ID: <b27b95a9-40b8-ebef-3457-ce87db6b26e5@ti.com> (raw)
In-Reply-To: <20170113182021.GD2630@atomide.com>
On Friday 13 January 2017 11:50 PM, Tony Lindgren wrote:
> * Vignesh R <vigneshr@ti.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
next prev parent reply other threads:[~2017-01-17 6:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 8:01 Vignesh R
2017-01-13 8:01 ` [PATCH 1/3] serial: 8250: omap: pause DMA only if DMA transfer in progress Vignesh R
2017-01-13 8:02 ` [PATCH 2/3] tty: serial: 8250_omap: Add OMAP_DMA_TX_KICK quirk for AM437x Vignesh R
2017-01-13 8:02 ` [PATCH 3/3] tty: serial: 8250_omap: Remove rx_dma_broken flag Vignesh R
2017-01-13 18:20 ` [PATCH 0/3] tty: serial: 8250_omap: Enable DMA support Tony Lindgren
2017-01-17 6:06 ` Vignesh R [this message]
2017-01-17 10:05 ` Vignesh R
2017-01-17 23:25 ` Tony Lindgren
2017-01-18 12:04 ` Vignesh R
2017-01-18 17:07 ` Tony Lindgren
2017-01-19 13:24 ` Greg Kroah-Hartman
2017-01-19 14:54 ` Tony Lindgren
2017-01-19 15:35 ` Greg Kroah-Hartman
2017-01-20 8:22 ` Vignesh R
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b27b95a9-40b8-ebef-3457-ce87db6b26e5@ti.com \
--to=vigneshr@ti.com \
--cc=bigeasy@linutronix.de \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=peter@hurleysoftware.com \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®