25 Sep
2009
25 Sep
'09
12:37 a.m.
You shouldn't need to touch the DMA code itself, it's normally an issue with the clocks and/or the pinmux code not managing to get the signals required to clock the data transfer.
I noticed the dma code has been changed from what I have.
Also noticed that the beagleboard is getting DMA interrupts when I "aplay":
cat /proc/interrupts | grep DMA
12: 4646 INTC DMA
but I'm not. As I mentioned, I'm at "2.6.29-rc3-omap1", anyone think there is a problem with pcm DMA's in that version?
Thanks
Rick