[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20130827230348.GA5705@kroah.com>
Date: Tue, 27 Aug 2013 16:03:48 -0700
From: Greg KH <gregkh@...uxfoundation.org>
To: Kevin Hilman <khilman@...aro.org>
Cc: Alexander Savchenko <oleksandr.savchenko@...com>, jslaby@...e.cz,
matts@...mtech-fastcom.com,
Paul McKenney <paulmck@...ux.vnet.ibm.com>,
Santosh Shilimkar <santosh.shilimkar@...com>,
dhowells@...hat.com, linux-serial@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] OMAP: UART: Keep the TX fifo full when possible
On Tue, Aug 20, 2013 at 08:57:25AM -0700, Kevin Hilman wrote:
> + Felipe
>
> On Mon, Jul 8, 2013 at 3:04 AM, Alexander Savchenko
> <oleksandr.savchenko@...com> wrote:
> > From: Dmitry Fink <finik@...com>
> >
> > Current logic results in interrupt storm since the fifo
> > is constantly below the threshold level. Change the logic
> > to fill all the available spaces in the fifo as long as
> > we have data to minimize the possibilty of underflow and
> > elimiate excessive interrupts.
> >
> > Signed-off-by: Dmitry Fink <finik@...com>
> > Signed-off-by: Alexander Savchenko <oleksandr.savchenko@...com>
>
> Hmm, another OMAP serial patch that wasn't Cc'd to linux-omap where
> OMAP users might have seen it. :(
>
> I just bisected a strange problem in linux-next on OMAP3 down to this
> patch. Reverting it fixes the problem.
>
> On OMAP3530 Beagle and Overo, after boot, doing a 'cat /proc/cpuinfo'
> was not returning to a prompt, suggesting something strange with the
> FIFO. Hitting return gets me back to a prompt.
>
> Greg, this one should also be dropped from tty-next until it can be
> further investgated and the problem solved.
Now reverted, thanks.
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists