[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1465920046.30123.83.camel@linux.intel.com>
Date: Tue, 14 Jun 2016 19:00:46 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: dinh.linux@...iebear.net
Cc: Dinh Nguyen <dinguyen@...nel.org>, heikki.krogerus@...ux.intel.com,
peter@...leysoftware.com,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-kernel@...r.kernel.org, linux-serial@...r.kernel.org
Subject: Re: [RFC RESEND] serial: 8250: fix regression in 8250 uart driver
On Tue, 2016-06-14 at 10:27 -0500, dinh.linux@...iebear.net wrote:
> >
> > On Mon, 2016-06-13 at 21:59 -0500, Dinh Nguyen wrote:
> > > Apologies, but my original email bounced for Andy and Heikki,
> > > resending.
> > > ----
> >
> > I suppose this one, i.e. commit dd4e91d538b3 ("dmaengine: slave
> > means at
> > least one of DMA_SLAVE, DMA_CYCLIC"), solves the issue.
> >
>
> Hmm...that commit didn't seem to fix my issue.
>
> In regard to Peter's reply:
>
> "The error is that your dmaengine driver doesn't support the
> functionality
> required by the 8250 driver."
Ah, sorry, indeed. Peter is right.
> Does this mean that the 8250_dw.c driver can no longer use DMA?
It means that previously the use of DMA engine whatever was used is not
correct in your case. There is no issues in UART driver, the issue is in
DMA controller driver.
I'm working on a quirk that will allow user to enforce PIO mode for
Rx/Tx or both. In that case if DMA controller can't be fixed you still
might use DMA for Tx.
--
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Intel Finland Oy
Powered by blists - more mailing lists