Hello.

David Brownell wrote:

EDMA doesn't need to live in arch/... anywhere, if
it comes to that...
    In drivers/dma/ you think?

Or drivers/misc ... a "DMA framework" wrapper around
it would live in drivers/dma.

However, this will probably take a while to move it there (frankly speaking, I'm not convinced it should be moved there) and in the meantime it's going to continue its existance within arch/arm/?

Unless you want to take up the argument for lifting
the restriction that drivers/dma implies DMA framework
support.  Me, I keep thinking that framework imposes
WAY too much overhead.  Though I'm glad it finally
learned that the primary purpose of DMA is talking to
peripherals, not as a memcpy() accelerator for certain
Intel chips.

Though having ported EDMA to OMAP-L1x, I haven't delved into the EDMA spec. as deep as to ascertain whether it can do memory-to-memory transfers... well, the porting was a relatively simple task anyway, not requiring deep understanding (and it wasn't even my task originally).

- Dave

WBR, Sergei



_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Reply via email to