On 2013-09-12 14:08, Mark Brown wrote:
On Wed, Sep 11, 2013 at 02:48:19PM +0300, Jyri Sarha wrote:
...
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?
I'm not clear what that means in concrete terms, sorry. Do you mean you can just use the existing register ranges for the McASP? Please bear in mind that I don't really know anything about this hardware.
The bottom line of my suggestion is only to add the dma register location to reg-property, since that info is needed in the mcasp node also in the future dmaengine_pcm-implementation.
The driver implementation would still remain pretty much the same. The McASP code would - instead of adding new properties to DT - use sensible hard-coded default event queue selection (= dma priority selection) for now.
Best regards, Jyri