[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46B96294322F7D458F9648B60E15112C6F3CED@zch01exm26.fsl.freescale.net>
Date: Wed, 11 Jul 2007 15:39:58 +0800
From: "Zhang Wei-r63237" <Wei.Zhang@...escale.com>
To: "Dan Williams" <dan.j.williams@...el.com>
Cc: <akpm@...ux-foundation.org>, <paulus@...ba.org>,
<galak@...nel.crashing.org>, <linuxppc-dev@...abs.org>,
<linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 3/4] Extend the DMA-engine API.
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.
> -----Original Message-----
> Subject: Re: [PATCH 3/4] Extend the DMA-engine API.
>
> On 7/10/07, Zhang Wei <wei.zhang@...escale.com> wrote:
> > Add channel wait queue and transfer callback dma_xfer_callback().
> > If the DMA controller and driver support interrupt, when the
> > transfer is finished, it will wakeup the wait queue
> > and call the callback function of the channel.
> >
> > Add dma_async_raw_xfer() to API and device_raw_xfer() to
> struct dma_device
> > for RAW physical address DMA transfer, which will be used
> at transfer
> > between I/O address and memory address.
> >
>
> Please review the async_tx API patch series[1], it should meet your
> needs. What you call "raw" mode support is now default for the
> dmaengine driver interface. I plan to request that this series be
> merged for 2.6.23.
>
> Regards,
> Dan
>
> [1]http://marc.info/?l=linux-raid&w=2&r=1&s=md-accel&q=b
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists