1. 19 4月, 2016 1 次提交
  2. 12 3月, 2016 2 次提交
  3. 27 1月, 2016 1 次提交
  4. 11 12月, 2015 1 次提交
  5. 23 11月, 2015 1 次提交
  6. 11 11月, 2015 1 次提交
  7. 18 9月, 2015 1 次提交
  8. 17 9月, 2015 2 次提交
  9. 15 9月, 2015 2 次提交
  10. 25 8月, 2015 1 次提交
  11. 18 8月, 2015 1 次提交
  12. 10 6月, 2015 1 次提交
  13. 09 6月, 2015 1 次提交
  14. 01 5月, 2015 4 次提交
  15. 12 4月, 2015 1 次提交
  16. 07 4月, 2015 1 次提交
  17. 02 4月, 2015 1 次提交
  18. 27 3月, 2015 1 次提交
  19. 25 3月, 2015 1 次提交
  20. 06 3月, 2015 2 次提交
  21. 05 3月, 2015 5 次提交
  22. 14 2月, 2015 1 次提交
  23. 03 2月, 2015 4 次提交
  24. 29 1月, 2015 1 次提交
    • A
      ASoC: davinci: fix DM365_EVM codec selection · f9a7ba32
      Arnd Bergmann 提交于
      An earlier bug fix of mine made the SND_DM365_VOICE_CODEC symbol
      tristate to avoid creating an undefined reference from the
      davinci-vcif.c driver to the davinci_soc_platform_register
      function that may be in a module.
      
      However, this may now lead to a different error on randconfig
      kernels:
      
      "warning: SND_DM365_VOICE_CODEC creates inconsistent choice state"
      
      This happens because we now have a choice statement with
      one bool and one tristate option, and the latter might not
      support being set to 'y' because of dependencies.
      
      This new change turns the other option into 'tristate' as well,
      which avoids the problem.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Fixes: 19926c6d ("ASoC: davinci: vcif must be a module if SND_DAVINCI_SOC is")
      Signed-off-by: NMark Brown <broonie@kernel.org>
      f9a7ba32
  25. 31 12月, 2014 1 次提交
  26. 12 11月, 2014 1 次提交
    • M
      ASoC: davinci-mcasp: Add overrun/underrun event handling · a7a3324a
      Misael Lopez Cruz 提交于
      An underrun (playback) event occurs when the serializer transfer
      data from the XRBUF buffer to the XRSR shift register, but the
      XRBUF hasn't been filled. Similarly, the overrun (capture) event
      occurs when data from the XRSR shift register is transferred to
      the XRBUF but it hasn't been read yet.
      
      These events are handled as XRUN events that cause the pcm to stop.
      The stream has to be explicitly restarted by the userspace which
      ensures that after stopping/starting McASP the data transfer is
      aligned with DMA. The other possibility was to internally stop and
      start McASP without DMA even knowing about it.
      Signed-off-by: NMisael Lopez Cruz <misael.lopez@ti.com>
      Signed-off-by: NPeter Ujfalusi <peter.ujfalusi@ti.com>
      Signed-off-by: NMark Brown <broonie@kernel.org>
      a7a3324a