1. 17 4月, 2013 1 次提交
  2. 04 4月, 2013 1 次提交
  3. 28 3月, 2013 3 次提交
  4. 26 3月, 2013 1 次提交
  5. 08 3月, 2013 2 次提交
  6. 15 2月, 2013 1 次提交
  7. 14 2月, 2013 1 次提交
  8. 11 2月, 2013 1 次提交
  9. 08 2月, 2013 1 次提交
    • M
      ASoC: core: Allow digital mute for capture · da18396f
      Mark Brown 提交于
      Help avoid noise from the power up of the capture path propagating through
      into the start of the recording (especially noise caused by the ramp of
      microphone biases) by keeping the capture muted until after we've finished
      powering things up with DAPM in the same manner we do for playback. This
      allows us to take advantage of soft mute support in the hardware more
      effectively and is more consistent.
      
      The core code using the existing digital mute operation is updated to take
      advantage of this. Some additional cases in the soc-pcm code and suspend
      will need separate handling but these are less practically relevant than
      the main runtime stream start/stop case.
      
      Rather than refactor the digital mute function in every single driver a
      new operation is added for drivers taking advantage of this functionality,
      the old operation should be phased out over time.
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      Acked-by Vinod Koul <vinod.koul@intel.com>
      Acked-by: NLiam Girdwood <liam.r.girdwood@linux.intel.com>
      da18396f
  10. 07 2月, 2013 1 次提交
  11. 05 2月, 2013 2 次提交
  12. 30 1月, 2013 1 次提交
  13. 29 1月, 2013 1 次提交
    • A
      ALSA: Force a cast to silence a warning from "sparse" · 019d80db
      Antonio Ospite 提交于
      Some audio drivers are calling snd_dma_continuous_data(GFP_KERNEL)
      which makes "sparse" give a warning:
      
        $ make C=2 M=sound/usb modules
          ...
        sound/usb/6fire/pcm.c:625:25: warning: cast from restricted gfp_t
        sound/usb/caiaq/audio.c:845:41: warning: cast from restricted gfp_t
        sound/usb/usx2y/usbusx2yaudio.c:997:54: warning: cast from restricted gfp_t
        sound/usb/usx2y/usbusx2yaudio.c:1001:54: warning: cast from restricted gfp_t
        sound/usb/usx2y/usx2yhwdeppcm.c:774:54: warning: cast from restricted gfp_t
        sound/usb/usx2y/usx2yhwdeppcm.c:778:54: warning: cast from restricted gfp_t
      
      Add __force to the cast to silence the warning.
      Signed-off-by: NAntonio Ospite <ao2@amarulasolutions.com>
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      019d80db
  14. 27 1月, 2013 1 次提交
  15. 26 1月, 2013 1 次提交
    • T
      ALSA: Make snd_printd() and snd_printdd() inline · 86b27237
      Takashi Iwai 提交于
      Because currently snd_printd() and snd_printdd() macros are expanded
      to empty when CONFIG_SND_DEBUG=n, a compile warning like below
      appears sometimes, and we had to covert it by ugly ifdefs:
        sound/pci/hda/patch_sigmatel.c: In function ‘stac92hd71bxx_fixup_hp’:
        sound/pci/hda/patch_sigmatel.c:2434:24: warning: unused variable ‘spec’ [-Wunused-variable]
      
      For "fixing" these issues better, this patch replaces snd_printd() and
      snd_printdd() definitions with empty inline functions instead of
      macros.  This should have the same effect but shut up warnings like
      above.
      
      But since we had already put ifdefs, changing to inline functions
      would trigger compile errors.  So, such ifdefs is removed in this
      patch.
      
      In addition, snd_pci_quirk name field is defined only when
      CONFIG_SND_DEBUG_VERBOSE is set, and the reference to it in
      snd_printdd() argument triggers the build errors, too.  For avoiding
      these errors, introduce a new macro snd_pci_quirk_name() that is
      defined no matter how the debug option is set.
      Reported-by: NStratos Karafotis <stratosk@semaphore.gr>
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      86b27237
  16. 16 1月, 2013 1 次提交
  17. 14 1月, 2013 2 次提交
  18. 08 1月, 2013 1 次提交
  19. 03 1月, 2013 1 次提交
  20. 24 12月, 2012 5 次提交
  21. 21 12月, 2012 1 次提交
  22. 15 12月, 2012 1 次提交
    • M
      ASoC: Prevent pop_wait overwrite · 9bffb1fb
      Misael Lopez Cruz 提交于
      pop_wait is used to determine if a deferred playback close
      needs to be cancelled when the a PCM is open or if after
      the power-down delay expires it needs to run. pop_wait is
      associated with the CODEC DAI, so the CODEC DAI must be
      unique. This holds true for most CODECs, except for the
      dummy CODEC and its DAI.
      
      In DAI links with non-unique dummy CODECs (e.g. front-ends),
      pop_wait can be overwritten by another DAI link using also a
      dummy CODEC. Failure to cancel a deferred close can cause
      mute due to the DAPM STOP event sent in the deferred work.
      
      One scenario where pop_wait is overwritten and causing mute
      is below (where hw:0,0 and hw:0,1 are two front-ends with
      default pmdown_time = 5 secs):
      
      aplay /dev/urandom -D hw:0,0 -c 2 -r 48000 -f S16_LE -d 1
      sleep 1
      aplay /dev/urandom -D hw:0,1 -c 2 -r 48000 -f S16_LE -d 3 &
      aplay /dev/urandom -D hw:0,0 -c 2 -r 48000 -f S16_LE
      
      Since CODECs may not be unique, pop_wait is moved to the PCM
      runtime structure. Creating separate dummy CODECs for each
      DAI link can also solve the problem, but at this point it's
      only pop_wait variable in the CODEC DAI that has negative
      effects by not being unique.
      Signed-off-by: NMisael Lopez Cruz <misael.lopez@ti.com>
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      9bffb1fb
  23. 02 12月, 2012 1 次提交
  24. 23 11月, 2012 3 次提交
  25. 20 11月, 2012 1 次提交
  26. 06 11月, 2012 1 次提交
  27. 01 11月, 2012 1 次提交
  28. 30 10月, 2012 1 次提交
  29. 23 10月, 2012 1 次提交
    • P
      ALSA: core: add hooks for audio timestamps · 4eeaaeae
      Pierre-Louis Bossart 提交于
      ALSA did not provide any direct means to infer the audio time for A/V
      sync and system/audio time correlations (eg. PulseAudio).
      Applications had to track the number of samples read/written and
      add/subtract the number of samples queued in the ring buffer.  This
      accounting led to small errors, typically several samples, due to the
      two-step process.  Computing the audio time in the kernel is more
      direct, as all the information is available in the same routines.
      
      Also add new .audio_wallclock routine to enable fine-grain synchronization
      between monotonic system time and audio hardware time.
      Using the wallclock, if supported in hardware, allows for a
      much better sub-microsecond precision and a common drift tracking for
      all devices sharing the same wall clock (master clock).
      Signed-off-by: NPierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      4eeaaeae