From: plagnioj@jcrosoft.com (Jean-Christophe PLAGNIOL-VILLARD)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/6] DMA: AT91: Serial: Add parameter for serial dma use
Date: Mon, 29 Oct 2012 12:42:21 +0100 [thread overview]
Message-ID: <20121029114221.GA31214@game.jcrosoft.org> (raw)
In-Reply-To: <1351501773-29024-1-git-send-email-elen.song@atmel.com>
On 17:09 Mon 29 Oct , Elen Song wrote:
> Signed-off-by: Elen Song <elen.song@atmel.com>
> ---
> arch/arm/mach-at91/include/mach/board.h | 2 ++
> drivers/tty/serial/atmel_serial.c | 1 +
> include/linux/platform_data/dma-atmel.h | 10 ++++++++++
> 3 files changed, 13 insertions(+)
you will have to rebase this over a clean if the platofrm_data I'll send today
or tomorrow that will move all the platform_data to inclide/linux
btw your patch broke the avr32
Best Regards.
J.
>
> diff --git a/arch/arm/mach-at91/include/mach/board.h b/arch/arm/mach-at91/include/mach/board.h
> index c55a436..a2188a6 100644
> --- a/arch/arm/mach-at91/include/mach/board.h
> +++ b/arch/arm/mach-at91/include/mach/board.h
> @@ -129,6 +129,8 @@ struct atmel_uart_data {
> short use_dma_tx; /* use transmit DMA? */
> short use_dma_rx; /* use receive DMA? */
> void __iomem *regs; /* virt. base address, if any */
> + struct at_dma_slave *dma_tx_slave;
> + struct at_dma_slave *dma_rx_slave;
> struct serial_rs485 rs485; /* rs485 settings */
> };
> extern void __init at91_add_device_serial(void);
> diff --git a/drivers/tty/serial/atmel_serial.c b/drivers/tty/serial/atmel_serial.c
> index 3d7e1ee..1b1bd4f 100644
> --- a/drivers/tty/serial/atmel_serial.c
> +++ b/drivers/tty/serial/atmel_serial.c
> @@ -45,6 +45,7 @@
>
> #include <asm/mach/serial_at91.h>
> #include <mach/board.h>
> +#include <linux/platform_data/dma-atmel.h>
>
> #ifdef CONFIG_ARM
> #include <mach/cpu.h>
> diff --git a/include/linux/platform_data/dma-atmel.h b/include/linux/platform_data/dma-atmel.h
> index cab0997..bb05302 100644
> --- a/include/linux/platform_data/dma-atmel.h
> +++ b/include/linux/platform_data/dma-atmel.h
> @@ -26,11 +26,21 @@ struct at_dma_platform_data {
> /**
> * struct at_dma_slave - Controller-specific information about a slave
> * @dma_dev: required DMA master device
> + * @tx_reg: physical address of data register used for
> + * memory-to-peripheral transfers
> + * @rx_reg: physical address of data register used for
> + * peripheral-to-memory transfers
> + * @reg_width: peripheral register width
> * @cfg: Platform-specific initializer for the CFG register
> + * @ctrla: Platform-specific initializer for the CTRLA register
> */
> struct at_dma_slave {
> struct device *dma_dev;
> + dma_addr_t tx_reg;
> + dma_addr_t rx_reg;
> + u32 reg_width;
> u32 cfg;
> + u32 ctrla;
> };
>
>
> --
> 1.7.9.5
>
next prev parent reply other threads:[~2012-10-29 11:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 9:09 [PATCH 0/6] Serial: AT91: Support rx and tx dma Elen Song
2012-10-29 9:09 ` [PATCH 1/6] DMA: AT91: Serial: Add parameter for serial dma use Elen Song
2012-10-29 11:42 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2012-10-30 3:23 ` Elen Song
2012-10-30 6:39 ` Elen Song
2012-11-22 7:40 ` Elen Song
2012-11-22 7:44 ` Jean-Christophe PLAGNIOL-VILLARD
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=20121029114221.GA31214@game.jcrosoft.org \
--to=plagnioj@jcrosoft.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).