1. 15 9月, 2009 1 次提交
  2. 26 8月, 2009 1 次提交
  3. 25 8月, 2009 1 次提交
    • S
      ASoC: S3C platform: Fix s3c2410_dma_started() called at improper time · faf907c7
      Shine Liu 提交于
      s3c24xx dma has the auto reload feature, when the the trnasfer is done,
      CURR_TC(DSTAT[19:0], current value of transfer count) reaches 0, and DMA
      ACK becomes 1, and then, TC(DCON[19:0]) will be loaded into CURR_TC. So
      the transmission is repeated.
      
      IRQ is issued while auto reload occurs. We change the DISRC and
      DCON[19:0] in the ISR, but at this time, the auto reload has been
      performed already. The first block is being re-transmitted by the DMA.
      
      So we need rewrite the DISRC and DCON[19:0] for the next block
      immediatly after the this block has been started to be transported.
      
      The function s3c2410_dma_started() is for this perpose, which is called
      in the form of "s3c2410_dma_ctrl(prtd->params->channel,
      S3C2410_DMAOP_STARTED);" in s3c24xx_pcm_trigger().
      
      But it is not correct. DMA transmission won't start until DMA REQ signal
      arrived, it is the time s3c24xx_snd_txctrl(1) or s3c24xx_snd_rxctrl(1)
      is called in s3c24xx_i2s_trigger().
      
      In the current framework, s3c24xx_pcm_trigger() is always called before
      s3c24xx_pcm_trigger(). So the s3c2410_dma_started() should be called in
      s3c24xx_pcm_trigger() after s3c24xx_snd_txctrl(1) or
      s3c24xx_snd_rxctrl(1) is called in this function.
      
      However, s3c2410_dma_started() is dma related, to call this function we
      should provide the channel number, which is given by
      substream->runtime->private_data->params->channel. The private_data
      points to a struct s3c24xx_runtime_data object, which is define in
      s3c24xx_pcm.c, so s3c2410_dma_started() can't be called in s3c24xx_i2s.c
      
      Fix this by moving the call to signal the DMA started to the DAI
      drivers.
      Signed-off-by: NShine Liu <liuxian@redflag-linux.com>
      Signed-off-by: NShine Liu <shinel@foxmail.com>
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      faf907c7
  4. 18 8月, 2009 1 次提交
  5. 28 5月, 2009 1 次提交
  6. 30 4月, 2009 7 次提交
  7. 28 4月, 2009 2 次提交
  8. 23 4月, 2009 1 次提交
  9. 16 4月, 2009 2 次提交
  10. 07 3月, 2009 2 次提交
  11. 06 3月, 2009 1 次提交
  12. 05 3月, 2009 3 次提交
  13. 10 12月, 2008 1 次提交
  14. 09 12月, 2008 1 次提交
    • M
      ASoC: Register platform DAIs · 3f4b783c
      Mark Brown 提交于
      Register all platform DAIs with the core.  In line with current behaviour
      this is done at module probe time rather than when the devices are probed
      (since currently that only happens as the entire ASoC card is registered
      except for those drivers that currently implement some kind of hotplug).
      Since the core currently ignores DAI registration this has no practical
      effect.
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      3f4b783c
  15. 04 12月, 2008 1 次提交
  16. 25 11月, 2008 1 次提交
    • M
      ASoC: Remove DAI type information · 3ba9e10a
      Mark Brown 提交于
      DAI type information is only ever used within ASoC in order to special
      case AC97 and for diagnostic purposes. Since modern CPUs and codecs
      support multi function DAIs which can be configured for several modes
      it is more trouble than it's worth to maintain anything other than a
      flag identifying AC97 DAIs so remove the type field and replace it with
      an ac97_control flag.
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      3ba9e10a
  17. 21 11月, 2008 1 次提交
    • M
      ASoC: Merge snd_soc_ops into snd_soc_dai_ops · dee89c4d
      Mark Brown 提交于
      Liam Girdwood's ASoC v2 work avoids having two different ops structures
      for DAIs by merging the members of struct snd_soc_ops into struct
      snd_soc_dai_ops, allowing per DAI configuration for everything.
      Backport this change.
      
      This paves the way for future work allowing any combination of DAIs to
      be connected rather than having fixed purpose CODEC and CPU DAIs and
      only allowing CODEC<->CPU interconnections.
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      dee89c4d
  18. 07 8月, 2008 2 次提交
  19. 10 7月, 2008 1 次提交
  20. 13 6月, 2008 1 次提交
  21. 01 2月, 2008 2 次提交