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

[Zhang Wei-r63237]

Hi, Dan,

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

Cheers,
Wei. 

> -----Original Message-----
> From: dan.j.williams@xxxxxxxxx 
> [mailto:dan.j.williams@xxxxxxxxx] On Behalf Of Dan Williams
> Sent: Thursday, July 12, 2007 12:57 AM
> To: Zhang Wei-r63237
> Cc: akpm@xxxxxxxxxxxxxxxxxxxx; paulus@xxxxxxxxx; 
> galak@xxxxxxxxxxxxxxxxxxx; linuxppc-dev@xxxxxxxxxx; 
> linux-kernel@xxxxxxxxxxxxxxx; shannon.nelson@xxxxxxxxx
> Subject: Re: [PATCH 3/4] Extend the DMA-engine API.
> 
> On 7/11/07, Zhang Wei-r63237 <Wei.Zhang@xxxxxxxxxxxxx> wrote:
> > Hi, Dan,
> >
> > Do you mention here: 
> http://marc.info/?l=linux-raid&m=118290909614463&w=2 ?
> > I see the async_tx is located at crypto/ of the above page, 
> but my patch is for DMA engine in drivers/dma and for DMA 
> engine driver.
> >
> > Thanks!
> > Wei.
> 
> Hi Wei,
> 
> I was referring to:
> http://marc.info/?l=linux-raid&m=118290909528910&w=2
> 
> 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:
> 
> tx = 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)
> 
> 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.
> 
> --
> Dan
> 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/