1. 30 Jan, 2014 8 commits
  2. 25 Jan, 2014 1 commit
  3. 23 Jan, 2014 2 commits
  4. 22 Jan, 2014 2 commits
  5. 20 Jan, 2014 5 commits
  6. 17 Jan, 2014 3 commits
  7. 16 Jan, 2014 12 commits
  8. 15 Jan, 2014 3 commits
  9. 14 Jan, 2014 4 commits
    • Lars-Peter Clausen's avatar
      ASoC: samsung: Remove SND_DMAENGINE_PCM_FLAG_NO_RESIDUE flag · d70e861a
      Lars-Peter Clausen authored
      The Samsung dmaengine ASoC driver is used with two different dmaengine drivers.
      The pl80x, which properly supports residue reporting and the pl330, which
      reports that it does not support residue reporting. So there is no need to
      manually set the NO_RESIDUE flag. This has the advantage that a proper (race
      condition free) PCM pointer() implementation is used when the pl80x driver is
      used. Also once the pl330 driver supports residue reporting the ASoC PCM driver
      will automatically start using it.
      Signed-off-by: default avatarLars-Peter Clausen <lars@metafoo.de>
      Signed-off-by: default avatarMark Brown <broonie@linaro.org>
      d70e861a
    • Lars-Peter Clausen's avatar
      ASoC: axi-{spdif,i2s}: Remove SND_DMAENGINE_PCM_FLAG_NO_RESIDUE flag · 153e66f5
      Lars-Peter Clausen authored
      The pl330 driver properly reports that it does not have residue reporting
      support, which means the PCM dmanegine driver is able to figure this out on its
      own. So there is no need to set the flag manually. Removing the flag has the
      advantage that once the pl330 driver gains support for residue reporting it will
      automatically be used by the generic dmaengine PCM driver.
      Signed-off-by: default avatarLars-Peter Clausen <lars@metafoo.de>
      Signed-off-by: default avatarMark Brown <broonie@linaro.org>
      153e66f5
    • Lars-Peter Clausen's avatar
      ASoC: generic-dmaengine-pcm: Check DMA residue granularity · 478028e0
      Lars-Peter Clausen authored
      The dmaengine framework now exposes the granularity with which it is able to
      report the transfer residue for a certain DMA channel. Check the granularity in
      the generic dmaengine PCM driver and
      	a) Set the SNDRV_PCM_INFO_BATCH if the granularity is per period or worse.
      	b) Fallback to the (race condition prone) period counting if the driver does
      	not support any residue reporting.
      Signed-off-by: default avatarLars-Peter Clausen <lars@metafoo.de>
      Signed-off-by: default avatarMark Brown <broonie@linaro.org>
      478028e0
    • Lars-Peter Clausen's avatar
      ASoC: generic-dmaengine-pcm: Check NO_RESIDUE flag at runtime · 93b943ed
      Lars-Peter Clausen authored
      Currently we have two different snd_soc_platform_driver structs in the generic
      dmaengine PCM driver. One for dmaengine drivers that support residue reporting
      and one for those which do not. When registering the PCM component we check
      whether the NO_RESIDUE flag is set or not and use the corresponding
      snd_soc_platform_driver. This patch modifies the driver to only have one
      snd_soc_platform_driver struct where the pointer() callback checks the
      NO_RESIDUE flag at runtime. This allows us to set the NO_RESIDUE flag after the
      PCM component has been registered. This becomes necessary when querying whether
      the dmaengine driver supports residue reporting from the dmaengine driver itself
      since the DMA channel might only be requested after the PCM component has been
      registered.
      Signed-off-by: default avatarLars-Peter Clausen <lars@metafoo.de>
      Signed-off-by: default avatarMark Brown <broonie@linaro.org>
      93b943ed