linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Thorsten Leemhuis <regressions@leemhuis.info>, dinh.linux@anniebear.net
Cc: Dinh Nguyen <dinguyen@kernel.org>,
	heikki.krogerus@linux.intel.com, peter@hurleysoftware.com,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [RFC RESEND] serial: 8250: fix regression in 8250 uart driver
Date: Sat, 02 Jul 2016 14:58:59 +0300	[thread overview]
Message-ID: <1467460739.30123.443.camel@linux.intel.com> (raw)
In-Reply-To: <dbaa0abe-06ab-57ee-4ba3-4e4717af4a62@leemhuis.info>

On Sat, 2016-07-02 at 13:53 +0200, Thorsten Leemhuis wrote:
> On 14.06.2016 18:00, Andy Shevchenko wrote:
> > On Tue, 2016-06-14 at 10:27 -0500, dinh.linux@anniebear.net wrote:
> > > > On Mon, 2016-06-13 at 21:59 -0500, Dinh Nguyen wrote:
> > > > 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.
> > […]
> > > 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.
> 
> What's the status of this issue?

Apparently I'm not going to fix DMA controller engine if it even would
be fixed (I don't know what one you use), but I will continue with the
mentioned quirk as soon as I finish one higher priority task. Sorry for
a delay.

>  Just wondering, as this issue is listed
> in my regression reports for 4.7 and it seems nothing much happened
> for
> more than a week now – which is a bad sign as the 4.7 release seems
> only
> a week or two away.


-- 

Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy

  reply	other threads:[~2016-07-02 11:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-14  2:59 [RFC RESEND] serial: 8250: fix regression in 8250 uart driver Dinh Nguyen
2016-06-14  9:40 ` Andy Shevchenko
2016-06-14 15:27   ` dinh.linux
2016-06-14 16:00     ` Andy Shevchenko
2016-07-02 11:53       ` Thorsten Leemhuis
2016-07-02 11:58         ` Andy Shevchenko [this message]
2016-08-17 11:14         ` Andy Shevchenko
2016-08-17 11:21           ` Heikki Krogerus
2016-08-23 13:53           ` Dinh Nguyen
2016-08-23 15:03             ` Andy Shevchenko
2016-09-07 17:16             ` Andy Shevchenko
2016-09-09 13:57               ` Dinh Nguyen
2016-09-09 14:28                 ` Andy Shevchenko

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=1467460739.30123.443.camel@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=dinguyen@kernel.org \
    --cc=dinh.linux@anniebear.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=peter@hurleysoftware.com \
    --cc=regressions@leemhuis.info \
    /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).