linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Vignesh R <vigneshr@ti.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: Wed, 18 Jan 2017 09:07:26 -0800	[thread overview]
Message-ID: <20170118170726.GE7403@atomide.com> (raw)
In-Reply-To: <a3055b9c-613b-6c64-db17-05b32ec24457@ti.com>

* Vignesh R <vigneshr@ti.com> [170118 04:04]:
> 
> 
> On Wednesday 18 January 2017 04:55 AM, Tony Lindgren wrote:
> > * Vignesh R <vigneshr@ti.com> [170117 02:06]:
> >>
> >>
> >> On Tuesday 17 January 2017 11:36 AM, Vignesh R wrote:
> >>>
> >>>
> >>> 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.
> >>>
> >>
> >> This looks a separate issue, I don't see any errata specific errata wrt
> >> UART on OMAP5. I will try to debug further.
> > 
> > OK maybe it's something configured or not configured by the bootloader
> > that we're missing in the Linux driver?
> > 
> 
> omap-serial uses a UART RX FIFO trigger of 1 byte whereas 8250_omap
> driver uses a RX FIFO trigger of 48 bytes. If less than 48 bytes is
> received then RX Timeout interrupt is raised which will help the driver
> to flush the FIFO. It seems like RX timeout does not seem to bring out
> UART IP from idle state on OMAP5.
> 
> I have posted a fix based on what is done for DRA7 in hwmod code:
> http://lists.infradead.org/pipermail/linux-arm-kernel/2017-January/480619.html

OK great, thanks for fixing that! Will give it a try a bit later today.

Regards,

Tony

  reply	other threads:[~2017-01-18 17:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-13  8:01 [PATCH 0/3] tty: serial: 8250_omap: Enable DMA support 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
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 [this message]
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=20170118170726.GE7403@atomide.com \
    --to=tony@atomide.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=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).