* Fwd: Dmaengine query [not found] ` <m2vdbb048f61004190326ve4220de6za13c94eed059ec2@mail.gmail.com> @ 2010-04-19 10:28 ` rd bairva 2010-04-22 4:05 ` rd bairva 2010-05-21 8:44 ` rd bairva 2 siblings, 0 replies; 3+ messages in thread From: rd bairva @ 2010-04-19 10:28 UTC (permalink / raw) To: linux-arm-kernel Hi Dan, On Thu, Apr 15, 2010 at 6:00 AM, Dan Williams <dan.j.williams@intel.com> wrote: > On Tue, Apr 13, 2010 at 11:26 PM, rd bairva <rbairva@gmail.com> wrote: >> Hi Dan, >> >> ? ? ? ?I am currently writing dmaengine compatible DMA driver for our ARM >> based architecture, But I am facing some performance issues doing >> that. >> >> 1. dmaengine says callback should run in tasklet, and next transfer >> cannot be scheduled from the callback. >> >> Due to these restrictions I am getting some performance issue while >> playing sound in our architecture. >> >> >> Can callback call in DMA driver be placed out of spin_lock to submit >> new operations from callback? (only in asynchronous case) >> >> is this Ok? please comment. > > Other dma driver authors are dropping the lock across the call to the > callback in the mem-to-io case. ?The compliance points in the > documentation are primarily targeted at the expectations of the > async_tx api. ?In the mem-to-io (slave dma) model you are not using > the async_tx api. > > -- > Dan > ? ?My DMA controller supports device to device DMA transfers and we need it in some of our drivers. Existing DMA engine framework doesn't have support for device to device transfers. Do you have any plans for device to device support in DMA engine? Can you suggest me some other suggestion for doing this? Regards Ramdayal ^ permalink raw reply [flat|nested] 3+ messages in thread
* Dmaengine query [not found] ` <m2vdbb048f61004190326ve4220de6za13c94eed059ec2@mail.gmail.com> 2010-04-19 10:28 ` Fwd: Dmaengine query rd bairva @ 2010-04-22 4:05 ` rd bairva 2010-05-21 8:44 ` rd bairva 2 siblings, 0 replies; 3+ messages in thread From: rd bairva @ 2010-04-22 4:05 UTC (permalink / raw) To: linux-arm-kernel My DMA controller supports device to device DMA transfers and we need it in some of our drivers. Existing DMA engine framework doesn't have support for device to device transfers. Do you have any plans for device to device support in DMA engine? Can you suggest me some other suggestion for doing this? Regards Ramdayal ^ permalink raw reply [flat|nested] 3+ messages in thread
* Dmaengine query [not found] ` <m2vdbb048f61004190326ve4220de6za13c94eed059ec2@mail.gmail.com> 2010-04-19 10:28 ` Fwd: Dmaengine query rd bairva 2010-04-22 4:05 ` rd bairva @ 2010-05-21 8:44 ` rd bairva 2 siblings, 0 replies; 3+ messages in thread From: rd bairva @ 2010-05-21 8:44 UTC (permalink / raw) To: linux-arm-kernel Hi Dan, ? ?My DMA controller supports device to device DMA transfers and we need it in some of our drivers. Existing DMA engine framework doesn't have support for device to device transfers. Do you have any plans for device to device support in DMA engine? Can you suggest me some other suggestion for doing this? Regards Ramdayal ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2010-05-21 8:44 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <v2mdbb048f61004132326r8ac75382k1e42321ff0ed484a@mail.gmail.com>
[not found] ` <v2he9c3a7c21004141730vcc79dd58t5478c9d83af9816@mail.gmail.com>
[not found] ` <m2vdbb048f61004190326ve4220de6za13c94eed059ec2@mail.gmail.com>
2010-04-19 10:28 ` Fwd: Dmaengine query rd bairva
2010-04-22 4:05 ` rd bairva
2010-05-21 8:44 ` rd bairva
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).