From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
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, 2 Jul 2016 13:53:17 +0200 [thread overview]
Message-ID: <dbaa0abe-06ab-57ee-4ba3-4e4717af4a62@leemhuis.info> (raw)
In-Reply-To: <1465920046.30123.83.camel@linux.intel.com>
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? 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.
CU, Thorsten
next prev parent reply other threads:[~2016-07-02 11:53 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 [this message]
2016-07-02 11:58 ` Andy Shevchenko
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=dbaa0abe-06ab-57ee-4ba3-4e4717af4a62@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=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 \
/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).