From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Jiri Slaby <jslaby@suse.cz>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
linux-serial@vger.kernel.org
Subject: Re: [PATCH] serial: 8250_dma: call serial8250_tx_dma unconditionally
Date: Wed, 5 Nov 2014 19:26:01 -0800 [thread overview]
Message-ID: <20141106032601.GA10724@kroah.com> (raw)
In-Reply-To: <1412772129-22816-1-git-send-email-andriy.shevchenko@linux.intel.com>
On Wed, Oct 08, 2014 at 03:42:09PM +0300, Andy Shevchenko wrote:
> Since we have the same check inside the function we may drop it away in
> __dma_tx_complete().
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> ---
> drivers/tty/serial/8250/8250_dma.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/tty/serial/8250/8250_dma.c b/drivers/tty/serial/8250/8250_dma.c
> index 148ffe4..189ae3c 100644
> --- a/drivers/tty/serial/8250/8250_dma.c
> +++ b/drivers/tty/serial/8250/8250_dma.c
> @@ -36,8 +36,7 @@ static void __dma_tx_complete(void *param)
> if (uart_circ_chars_pending(xmit) < WAKEUP_CHARS)
> uart_write_wakeup(&p->port);
>
> - if (!uart_circ_empty(xmit) && !uart_tx_stopped(&p->port))
> - serial8250_tx_dma(p);
> + serial8250_tx_dma(p);
>
> spin_unlock_irqrestore(&p->port.lock, flags);
> }
The code in this area has changed a lot now due to some dma work added
to this driver. Can you look at my tty-testing branch of tty.git on
git.kernel.org and see if this is still relevant now? If so, please
refresh this patch and resend.
thanks,
greg k-h
next prev parent reply other threads:[~2014-11-06 3:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 12:42 [PATCH] serial: 8250_dma: call serial8250_tx_dma unconditionally Andy Shevchenko
2014-10-15 12:53 ` Heikki Krogerus
2014-11-06 3:26 ` Greg Kroah-Hartman [this message]
2014-11-06 10:32 ` 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=20141106032601.GA10724@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=jslaby@suse.cz \
--cc=linux-serial@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.