From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Dinh Nguyen <dinguyen@kernel.org>
Cc: 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: Tue, 14 Jun 2016 12:40:20 +0300 [thread overview]
Message-ID: <1465897220.30123.26.camel@linux.intel.com> (raw)
In-Reply-To: <575F7325.3030907@kernel.org>
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.
>
> Hi Andy,
>
> I saw that you have discovered that commit ec5a11a91eec ("serial:
> 8250:
> Validate dmaengine rx chan meets requirements") introduced a
> regression
> in the 8250 uart driver. For SoCFPGA platform, I am seeing this error:
>
> [ 5.541751] ttyS0 - failed to request DMA
>
> Reverting the commit ec5a11a91eec removes the error.
>
> I saw that you started the discussion, but I didn't see that a patch
> was
> included[1].
>
> The following patch seems to fix the error, but I'm not sure if it's
> the
> same fix that you had in mind.
>
> Thanks,
> Dinh
>
> [1] http://marc.info/?l=linux-serial&m=146254187602862&w=2
>
> ---------------8<------------
> diff --git a/drivers/tty/serial/8250/8250_dma.c
> b/drivers/tty/serial/8250/8250_dma.c
> index 7f33d1c..847a203 100644
> --- a/drivers/tty/serial/8250/8250_dma.c
> +++ b/drivers/tty/serial/8250/8250_dma.c
> @@ -176,7 +176,7 @@ int serial8250_request_dma(struct uart_8250_port
> *p)
> ret = dma_get_slave_caps(dma->rxchan, &caps);
> if (ret)
> goto release_rx;
> - if (!caps.cmd_pause || !caps.cmd_terminate ||
> + if ((!caps.cmd_pause || !caps.cmd_terminate) &&
> caps.residue_granularity ==
> DMA_RESIDUE_GRANULARITY_DESCRIPTOR) {
> ret = -EINVAL;
> goto release_rx;
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2016-06-14 9:40 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 [this message]
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
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=1465897220.30123.26.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=dinguyen@kernel.org \
--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).