• Sekhar Nori's avatar
    ASoC: davinci: let platform data define edma queue numbers · 48519f0a
    Sekhar Nori authored
    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: default avatarSekhar Nori <nsekhar@ti.com>
    Acked-by: default avatarLiam Girdwood <lrg@slimlogic.co.uk>
    Signed-off-by: default avatarMark Brown <broonie@opensource.wolfsonmicro.com>
    48519f0a
davinci-i2s.c 23.1 KB