On 2013-09-09 18:25, Mark Brown wrote:
On Mon, Sep 09, 2013 at 06:12:14PM +0300, oku@iki.fi wrote: From: Jyri Sarha jsarha@ti.com
This patch adds new DMA related properties to mcasp DT bindings. The new properties may not be needed after davinci audio is updated to use dmaengine.
How hard is it going to be to convert to dmaengine or to open code something that works with the standard bindings even if the implementation is open coded? I'm not enthusiastic about adding temporary bindings, I'm not sure the DT maintainers would be either.
I have not studied the code enough to give a good work estimate about the conversion, but at least the current EDMA driver would need cyclic mode to be implemented before the conversion would be possible. It may also be difficult to make sure all the old davinci HW using the same code would still work after the change. In any case I do not think the conversion is going to be made anytime soon (read: in time for v3.13).
However, after taking a another look at the added DT bindings, I think we could survive with mcasp dma register addresses only for now. To my understanding those are anyway need in mcasp node. In DT boot the mcasp EDMA event queue could be hardcoded to the highest priority for now.
How does this sound?
Best regards, Jyri