1. 04 Oct, 2011 1 commit
  2. 02 Oct, 2011 3 commits
  3. 27 Sep, 2011 1 commit
  4. 23 Sep, 2011 1 commit
    • Jarkko Nikula's avatar
      ASoC: omap-mcbsp: Do not attempt to change DAI sysclk if stream is active · 34c86985
      Jarkko Nikula authored
      Attempt to change McBSP CLKS source while another stream is active is not
      safe after commit d1358657 ("OMAP: McBSP: implement functional clock
      switching via clock framework") in 2.6.37.
      
      CLKS parent clock switching using clock framework have to idle the McBSP
      before switching and then activate it again. This short break can cause a
      DMA transaction error to already running stream which halts and recovers
      only by closing and restarting the stream.
      
      This goes more fatal after commit e2fa61d4 ("OMAP3: l3: Introduce
      l3-interconnect error handling driver") in 2.6.39 where l3 driver detects a
      severe timeout error and does BUG_ON().
      
      Fix this by not changing any configuration in omap_mcbsp_dai_set_dai_sysclk
      if the McBSP is already active. This test should have been here just from
      the beginning anyway.
      Signed-off-by: default avatarJarkko Nikula <jarkko.nikula@bitmer.com>
      Acked-by: default avatarPeter Ujfalusi <peter.ujfalusi@ti.com>
      Signed-off-by: default avatarMark Brown <broonie@opensource.wolfsonmicro.com>
      Cc: stable@kernel.org
      34c86985
  5. 21 Sep, 2011 1 commit
  6. 20 Sep, 2011 1 commit
  7. 15 Sep, 2011 1 commit
  8. 12 Sep, 2011 1 commit
  9. 06 Sep, 2011 2 commits
  10. 31 Aug, 2011 4 commits
  11. 29 Aug, 2011 1 commit
  12. 24 Aug, 2011 5 commits
  13. 22 Aug, 2011 11 commits
  14. 18 Aug, 2011 1 commit
  15. 17 Aug, 2011 1 commit
    • Sascha Hauer's avatar
      ASoC: Fix check for symmetric rate enforcement · 25b76791
      Sascha Hauer authored
      The ASoC core tries to not enforce symmetric rates when
      two streams open simultaneously. It does so by checking
      rtd->rate being zero. This works exactly once after booting
      because it is not set to zero again when the streams close.
      Fix this by setting rtd->rate when no active stream is left.
      
      [This leads to lots of warnings about not enforcing the symmetry in some
      situations as there's a race in the userspace API where we know we've
      got two applications but don't know what rates they want to set.
      -- broonie ]
      Signed-off-by: default avatarSascha Hauer <s.hauer@pengutronix.de>
      Signed-off-by: default avatarMark Brown <broonie@opensource.wolfsonmicro.com>
      25b76791
  16. 15 Aug, 2011 5 commits