From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] tty/serial: at91: maxburst was missing for dma transfers
Date: Thu, 16 Apr 2015 17:07:56 +0200 [thread overview]
Message-ID: <552FD04C.2030507@atmel.com> (raw)
In-Reply-To: <1429196292-8134-1-git-send-email-ludovic.desroches@atmel.com>
Le 16/04/2015 16:58, Ludovic Desroches a ?crit :
> Maxburst was not set when doing the dma slave configuration. This value
> is checked by the recently introduced xdmac. It causes an error when
> doing the slave configuration and so prevents from using dma.
>
> Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com>
> Cc: <stable@vger.kernel.org> # 3.12 and later
Indeed, thanks!
Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>
> ---
> drivers/tty/serial/atmel_serial.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/tty/serial/atmel_serial.c b/drivers/tty/serial/atmel_serial.c
> index 4e959c4..6afce7e 100644
> --- a/drivers/tty/serial/atmel_serial.c
> +++ b/drivers/tty/serial/atmel_serial.c
> @@ -880,6 +880,7 @@ static int atmel_prepare_tx_dma(struct uart_port *port)
> config.direction = DMA_MEM_TO_DEV;
> config.dst_addr_width = DMA_SLAVE_BUSWIDTH_1_BYTE;
> config.dst_addr = port->mapbase + ATMEL_US_THR;
> + config.dst_maxburst = 1;
>
> ret = dmaengine_slave_config(atmel_port->chan_tx,
> &config);
> @@ -1059,6 +1060,7 @@ static int atmel_prepare_rx_dma(struct uart_port *port)
> config.direction = DMA_DEV_TO_MEM;
> config.src_addr_width = DMA_SLAVE_BUSWIDTH_1_BYTE;
> config.src_addr = port->mapbase + ATMEL_US_RHR;
> + config.src_maxburst = 1;
>
> ret = dmaengine_slave_config(atmel_port->chan_rx,
> &config);
>
--
Nicolas Ferre
prev parent reply other threads:[~2015-04-16 15:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 14:58 [PATCH] tty/serial: at91: maxburst was missing for dma transfers Ludovic Desroches
2015-04-16 15:07 ` Nicolas Ferre [this message]
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=552FD04C.2030507@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=linux-arm-kernel@lists.infradead.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 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).