linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Hector Palacios <hector.palacios@digi.com>
Cc: linux-serial@vger.kernel.org, u.kleine-koenig@pengutronix.de,
	b32955@freescale.com, gregkh@linuxfoundation.org,
	shawn.guo@linaro.org, fabio.estevam@freescale.com
Subject: Re: [PATCH] serial: mxs-auart: wait for DMA buffer to flush before shutdown
Date: Tue, 1 Oct 2013 21:56:58 +0200	[thread overview]
Message-ID: <201310012156.58888.marex@denx.de> (raw)
In-Reply-To: <1380644315-31581-1-git-send-email-hector.palacios@digi.com>

Dear Hector Palacios,

> The shutdown function was not waiting for the DMA buffer to flush
> before disabling the AUART. This lead to many bytes not being
> transferred (specially at low baudrates), as they were still in the
> DMA buffer when the AUART was shutdown.
> This patch also adds the check for the BUSY flag.
> 
> Signed-off-by: Hector Palacios <hector.palacios@digi.com>
> 
> https://jira.digi.com/browse/DEL-616

The link doesn't work. Otherwise makes sense

Reviewed-by: Marek Vasut <marex@denx.de>

> ---
>  drivers/tty/serial/mxs-auart.c | 16 +++++++++++++++-
>  1 file changed, 15 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/tty/serial/mxs-auart.c
> b/drivers/tty/serial/mxs-auart.c index f85b8e6..0d8b2ca 100644
> --- a/drivers/tty/serial/mxs-auart.c
> +++ b/drivers/tty/serial/mxs-auart.c
> @@ -750,12 +750,26 @@ static int mxs_auart_startup(struct uart_port *u)
>  	return 0;
>  }
> 
> +static unsigned int mxs_auart_tx_empty(struct uart_port *u);
> +
>  static void mxs_auart_shutdown(struct uart_port *u)
>  {
>  	struct mxs_auart_port *s = to_auart_port(u);
> +	unsigned int to;
> +
> +	if (auart_dma_enabled(s)) {
> +		/* Wait enough time to flush DMA buffer completely */
> +		to = u->timeout * UART_XMIT_SIZE / u->fifosize;
> +		while (!mxs_auart_tx_empty(u) && to--)
> +			mdelay(1);
> 
> -	if (auart_dma_enabled(s))
>  		mxs_auart_dma_exit(s);
> +	}
> +
> +	/* Wait for transmitter to become empty ... */
> +	to = u->timeout;
> +	while ((readl(port->membase + AUART_STAT) & AUART_STAT_BUSY) && to--)
> +		mdelay(1);
> 
>  	writel(AUART_CTRL2_UARTEN, u->membase + AUART_CTRL2_CLR);

Best regards,
Marek Vasut

  parent reply	other threads:[~2013-10-01 19:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-01 16:18 [PATCH] serial: mxs-auart: wait for DMA buffer to flush before shutdown Hector Palacios
2013-10-01 19:48 ` Uwe Kleine-König
2013-10-02  7:31   ` Hector Palacios
2013-10-02  7:44     ` Uwe Kleine-König
2013-10-02  8:09       ` Hector Palacios
2013-10-02  8:30         ` Uwe Kleine-König
2013-10-02  8:46           ` Hector Palacios
2013-10-02  9:59             ` Uwe Kleine-König
2013-10-02  8:36     ` Uwe Kleine-König
2013-10-02  8:53       ` Hector Palacios
2013-10-01 19:56 ` Marek Vasut [this message]
2013-10-02  8:24 ` Hector Palacios

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=201310012156.58888.marex@denx.de \
    --to=marex@denx.de \
    --cc=b32955@freescale.com \
    --cc=fabio.estevam@freescale.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hector.palacios@digi.com \
    --cc=linux-serial@vger.kernel.org \
    --cc=shawn.guo@linaro.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /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).