[alsa-devel] [PATCH 03/17] ASoC: Add a generic dmaengine_pcm driver

Peter Ujfalusi peter.ujfalusi at ti.com
Thu Apr 18 09:30:47 CEST 2013

Hi Lars,

On 04/17/2013 08:45 PM, Lars-Peter Clausen wrote:
> On 04/17/2013 03:06 PM, Peter Ujfalusi wrote:
>> On 04/17/2013 12:48 PM, Lars-Peter Clausen wrote:
>>> This sounds like it needs more than just support for custom channel names.
>>> The generic driver currently expects that there is exactly one DMA channel
>>> for capture and one for playback (well and in case the DAI link is simplex
>>> only either one of them).
>>> What are these 8 channels exactly used for?
>> We have 7 FIFOs which can be configured either playback or capture. The last
>> channel is used for debug purposes only right now.
>> Basically we can dynamically configure the 8 DMA channel for playback/capture
>> and the mixing of incoming streams done inside of the AESS.
>> We have 7 DAIs and we have playback/capture on those (some only have playback
>> some only capture some duplex). Right now we have kind of static DMA bindings
>> for them, I'm working on a dynamic model right now.
> Hm, if you need to re-assign the DMA channels dynamically at runtime it
> maybe better to stick with a custom PCM driver. Should I drop OMAP from this
> series for now?

I think this would the best for now. However I did tested the series and it
worked with the code upstream.
Later I can revisit this and probably have two PCM driver for OMAP, but I'm
not sure about this right now, I will know more when I have rebased my
AESS/ABE work on top of 3.10-rc1.

Can you drop the OMAP patches for now?


More information about the Alsa-devel mailing list