1. 20 7月, 2010 1 次提交
    • S
      ASoC: davinci: let platform data define edma queue numbers · 48519f0a
      Sekhar Nori 提交于
      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: NSekhar Nori <nsekhar@ti.com>
      Acked-by: NLiam Girdwood <lrg@slimlogic.co.uk>
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      48519f0a
  2. 06 7月, 2010 2 次提交
  3. 09 6月, 2010 2 次提交
  4. 04 6月, 2010 1 次提交
  5. 03 6月, 2010 3 次提交
  6. 31 5月, 2010 4 次提交
  7. 30 5月, 2010 8 次提交
  8. 29 5月, 2010 2 次提交
  9. 28 5月, 2010 17 次提交