RE: [PATCH 3/4] Extend the DMA-engine API.

Hi, Dan,

Thanks! I get it.
It's so lucky we have the same target.
When your patch could be accepted?

Cheers,
Wei.=20

-----Original Message-----
From: dan.j.williams@gmail.com=20
[mailto:dan.j.williams@gmail.com] On Behalf Of Dan Williams
Sent: Thursday, July 12, 2007 12:57 AM
To: Zhang Wei-r63237
Cc: akpm@linux-foundation.org; paulus@samba.org;=20
galak@kernel.crashing.org; linuxppc-dev@ozlabs.org;=20
linux-kernel@vger.kernel.org; shannon.nelson@intel.com
Subject: Re: [PATCH 3/4] Extend the DMA-engine API.
=20
On 7/11/07, Zhang Wei-r63237 [off-list ref] wrote:

quoted

Hi, Dan,

Do you mention here:=20

http://marc.info/?l=3Dlinux-raid&m=3D118290909614463&w=3D2 ?

quoted

I see the async_tx is located at crypto/ of the above page,=20

but my patch is for DMA engine in drivers/dma and for DMA=20
engine driver.

quoted

Thanks!
Wei.

=20
Hi Wei,
=20
I was referring to:
http://marc.info/?l=3Dlinux-raid&m=3D118290909528910&w=3D2
=20
async_tx is an api that exploits the raw capabilities of the new
dmaengine interface.  For your case when the existing api calls do not
provide the proper interface you can open code something like the
following:
=20
tx =3D dev->device_prep_dma_<operation>(chan, len, int_flag)
tx->tx_set_src(dma_addr_t, tx, index /* for multi-source ops */)
tx->tx_set_dest(dma_addr_t, tx, index)
tx->tx_submit(tx)
=20
The expectation is that the most common usages of dmaengines will use
async_tx calls, or the 'dma_async_memcpy_foo_to_bar' helper routines.
=20
--
Dan
=20