linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/4] dmaengine: Device Tree support for Atmel DMA
Date: Mon, 17 Oct 2011 14:54:37 +0200	[thread overview]
Message-ID: <4E9C258D.3030509@atmel.com> (raw)
In-Reply-To: <1318438634-11826-1-git-send-email-nicolas.ferre@atmel.com>

On 10/12/2011 06:57 PM, Nicolas Ferre :
> This series add the device tree support to Atmel DMA controller driver:
> at_hdmac.
> The removal of platform data ease the conversion to device tree. It also have
> the additional benefit of being simpler and cleaner.
> 
> Nicolas Ferre (4):
>       dmaengine: at_hdmac: platform data move to use .id_table
>       dmaengine: at_hdmac: add device tree support
>       ARM: at91/dma: remove platform data from DMA controller
>       ARM: at91/dma: DMA controller registering with DT support
> 
>  .../devicetree/bindings/dma/atmel-dma.txt          |   14 ++++
>  arch/arm/mach-at91/at91sam9g45_devices.c           |   17 ++---
>  arch/arm/mach-at91/at91sam9rl_devices.c            |    8 +--
>  arch/arm/mach-at91/include/mach/at_hdmac.h         |   10 ---
>  drivers/dma/at_hdmac.c                             |   76 +++++++++++++++++---
>  drivers/dma/at_hdmac_regs.h                        |    8 ++
>  6 files changed, 97 insertions(+), 36 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/dma/atmel-dma.txt

Vinod,

I have just rebased the dmaengine at_hdmac driver patches on top of your
"next" branch as a "v4" series. I send it to you with Grant's "Acked-by"
right now.

Best regards,
-- 
Nicolas Ferre

  parent reply	other threads:[~2011-10-17 12:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-12 16:57 [PATCH v3 0/4] dmaengine: Device Tree support for Atmel DMA Nicolas Ferre
2011-10-12 16:57 ` [PATCH v3 1/4] dmaengine: at_hdmac: platform data move to use .id_table Nicolas Ferre
2011-10-13  0:32   ` Grant Likely
2011-10-12 16:57 ` [PATCH v3 2/4] dmaengine: at_hdmac: add device tree support Nicolas Ferre
2011-10-13  0:34   ` Grant Likely
2011-10-13 11:54     ` Nicolas Ferre
2011-10-12 16:57 ` [PATCH v3 3/4] ARM: at91/dma: remove platform data from DMA controller Nicolas Ferre
2011-10-13  0:34   ` Grant Likely
2011-10-12 16:57 ` [PATCH v3 4/4] ARM: at91/dma: DMA controller registering with DT support Nicolas Ferre
2011-10-13  0:35   ` Grant Likely
2011-10-17 12:54 ` Nicolas Ferre [this message]
2011-10-17 12:56   ` [PATCH v4 1/2] dmaengine: at_hdmac: platform data move to use .id_table Nicolas Ferre
2011-10-17 12:56     ` [PATCH v4 2/2] dmaengine: at_hdmac: add device tree support Nicolas Ferre
2011-10-24  9:34     ` [PATCH v4 1/2] dmaengine: at_hdmac: platform data move to use .id_table Grant Likely
2011-11-22 10:55       ` Nicolas Ferre
2011-10-23 14:30   ` [PATCH v3 0/4] dmaengine: Device Tree support for Atmel DMA Nicolas Ferre
2011-10-24  3:04     ` Vinod Koul
2011-10-24  3:28   ` Vinod Koul
2011-10-24  9:05     ` Nicolas Ferre
2011-11-10  9:37   ` Vinod Koul

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=4E9C258D.3030509@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).