From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: maciej.sosnowski@intel.com,
linux-arm-kernel@lists.arm.linux.org.uk,
patrice.vilchez@atmel.com, linux-kernel@vger.kernel.org,
haavard.skinnemoen@atmel.com
Subject: Re: [PATCH] dmaengine: at_hdmac: add DMA slave transfers
Date: Fri, 24 Jul 2009 09:35:37 +0200 [thread overview]
Message-ID: <4A696449.7050303@atmel.com> (raw)
In-Reply-To: <e9c3a7c20907231013k3d5e8c89w1069e8509539438f@mail.gmail.com>
Dan Williams :
> On Wed, Jul 22, 2009 at 11:04 AM, Nicolas Ferre<nicolas.ferre@atmel.com> wrote:
>> This patch for at_hdmac adds the slave transfers capability to the Atmel DMA
>> controller available on some AT91 SOCs. This allow peripheral to memory and
>> memory to peripheral transfers with hardware handshaking.
>>
>> Slave structure for controller specific information is passed through channel
>> private data. This at_dma_slave structure is defined in at_hdmac.h header file
>> and relative hardware definition are moved to this file from at_hdmac_regs.h.
>> Doing this we allow the channel configuration from platform definition code.
>>
>> This work is intensively based on dw_dmac and several slave implementations.
>>
>> Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
>> ---
>
> Seems straightforward and self contained, applied. Just curious which
> drivers will take advantage of this slave capability? As it stands I
> do not see any in-tree users of at_hdmac beyond dmatest?
Well, in fact the same as dw_dmac: atmel-mci. Adaptation of other
drivers are coming: probably ac97 and spi interfaces.
The patches for adaptation of atmel-mci to at_hdmac are coming...
Best regards,
--
Nicolas Ferre
next prev parent reply other threads:[~2009-07-24 7:35 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 10:42 [PATCH 1/2 v2] dmaengine: at_hdmac: new driver for the Atmel AHB DMA Controller Nicolas Ferre
2009-06-26 10:42 ` [PATCH 2/2 v2] at91/dmaengine: integration of at_hdmac driver in at91sam9rl Nicolas Ferre
2009-06-27 15:06 ` [PATCH 1/2 v2] dmaengine: at_hdmac: new driver for the Atmel AHB DMA Controller Atsushi Nemoto
2009-07-01 15:30 ` Nicolas Ferre
2009-07-03 15:12 ` Atsushi Nemoto
2009-07-01 13:58 ` Nicolas Ferre
2009-07-02 0:58 ` Dan Williams
2009-07-02 1:18 ` Dan Williams
2009-07-03 12:59 ` Sosnowski, Maciej
2009-07-03 13:03 ` Nicolas Ferre
[not found] ` <0bb1aaf3fca441453fbb9296e1a35d7921d74467.1246641180.git.nicolas.ferre@atmel.com>
2009-07-03 17:24 ` [PATCH 1/2 v3] " Nicolas Ferre
2009-07-17 10:38 ` Nicolas Ferre
2009-07-18 16:01 ` Dan Williams
2009-07-21 8:33 ` Nicolas Ferre
2009-07-22 13:35 ` Sosnowski, Maciej
2009-07-22 18:04 ` [PATCH] dmaengine: at_hdmac: add DMA slave transfers Nicolas Ferre
2009-07-23 17:13 ` Dan Williams
2009-07-24 7:35 ` Nicolas Ferre [this message]
2009-07-24 13:29 ` Atsushi Nemoto
2009-07-24 14:10 ` Haavard Skinnemoen
2009-07-27 13:24 ` Sosnowski, Maciej
2009-07-28 15:13 ` Atsushi Nemoto
2009-07-29 13:05 ` Sosnowski, Maciej
2009-07-29 15:16 ` Atsushi Nemoto
2009-07-29 14:27 ` Dan Williams
2009-07-31 3:58 ` Atsushi Nemoto
2009-07-27 13:22 ` Sosnowski, Maciej
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=4A696449.7050303@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=dan.j.williams@intel.com \
--cc=haavard.skinnemoen@atmel.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.sosnowski@intel.com \
--cc=patrice.vilchez@atmel.com \
/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