[alsa-devel] [PATCH] asoc: davinci: let platform data define edma queue numbers
lrg at slimlogic.co.uk
Sat Jul 17 19:28:53 CEST 2010
On Thu, 2010-07-15 at 17:44 +0530, Sekhar Nori wrote:
> Currently the EDMA queue to be used by for servicing ASP through
> internal RAM is fixed to EDMAQ_0 and that to service internal RAM
> from external RAM is fixed to EDMAQ_1.
> This may not be the desirable configuration on all platforms. For
> example, on DM365, queue 0 has large fifo size and is more suitable
> for video transfers. Having audio and video transfers on the same
> queue may lead to starvation on audio side.
> platform data as defined currently passes a queue number to the driver
> but that remains unused inside the driver.
> Fix this by defining one queue each for ASP and RAM transfers in the
> platform data and using it inside the driver.
> Since EDMAQ_0 maps to 0, thats the queue that will be used if
> the asp queue number is not initialized. None of the platforms
> currently utilize ping-pong transfers through internal RAM so that
> functionality remains unchanged too.
> This patch has been tested on DM644x and OMAP-L138 EVMs.
> Signed-off-by: Sekhar Nori <nsekhar at ti.com>
Acked-by: Liam Girdwood <lrg at slimlogic.co.uk>
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
More information about the Alsa-devel