1. 16 10月, 2015 1 次提交
  2. 28 5月, 2015 1 次提交
  3. 22 5月, 2015 2 次提交
  4. 28 4月, 2015 1 次提交
    • J
      ALSA: jack: implement kctl creating for jack devices · 9058cbe1
      Jie Yang 提交于
      Currently the ALSA jack core registers only input devices for each jack
      registered. These jack input devices are not readable by userspace devices
      that run as non root. This patch series will implement kctls inside the
      core jack part, including kctls creating, status changing report, for both
      HD-Audio and ASoC jack. This allows non root userspace to read jack status
      and act on it.
      
      This patch adds a new API called snd_jack_add_new_kctl(), which will create
      a kcontrol, add it to the card, and also attach it to the jack kctl list.
      
      This patch also initialises the jack kctl list after jack is newed, and
      reports kctl status when jack insertion/removal events occur.
      
      snd_jack_new() is updated in the following patches to also support creating
      phantom jacks and jack kcontrols. We then remove these duplicated features
      from HDA jack and have jack kctls handled by core throughout HDA and ASoC.
      Signed-off-by: NLiam Girdwood <liam.r.girdwood@linux.intel.com>
      Modified-by: NJie Yang <yang.jie@intel.com>
      Signed-off-by: NJie Yang <yang.jie@intel.com>
      Reveiwed-by: NMark Brown <broonie@kernel.org>
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      9058cbe1
  5. 24 4月, 2015 1 次提交
  6. 04 11月, 2014 1 次提交
    • T
      ALSA: pcm: Replace PCM hwptr tracking with tracepoints · f5914908
      Takashi Iwai 提交于
      ALSA PCM core has a mechanism tracking the PCM hwptr updates for
      analyzing XRUNs.  But its log is limited (up to 10) and its log output
      is a kernel message, which is hard to handle.
      
      In this patch, the hwptr logging is moved to the tracing
      infrastructure instead of its own.  Not only the hwptr updates but
      also XRUN and hwptr errors are recorded on the trace log, so that user
      can see such events at the exact timing.
      
      The new "snd_pcm" entry will appear in the tracing events:
        # ls -F /sys/kernel/debug/tracing/events/snd_pcm
        enable  filter  hw_ptr_error/  hwptr/  xrun/
      
      The hwptr is for the regular hwptr update events.  An event trace
      looks like:
      
        aplay-26187 [004] d..3  4012.834761: hwptr: pcmC0D0p/sub0: POS: pos=488, old=0, base=0, period=1024, buf=16384
      
      "POS" shows the hwptr update by the explicit position update call and
      "IRQ" means the hwptr update by the interrupt,
      i.e. snd_pcm_period_elapsed() call.  The "pos" is the passed
      ring-buffer offset by the caller, "old" is the previous hwptr, "base"
      is the hwptr base position, "period" and "buf" are period- and
      buffer-size of the target PCM substream.
      (Note that the hwptr position displayed here isn't the ring-buffer
       offset.  It increments up to the PCM position boundary.)
      
      The XRUN event appears similarly, but without "pos" field.
      The hwptr error events appear with the PCM identifier and its reason
      string, such as "Lost interrupt?".
      
      The XRUN and hwptr error reports on kernel message are still left, can
      be turned on/off via xrun_debug proc like before.  But the bit 3, 4, 5
      and 6 bits of xrun_debug proc are dropped by this patch.  Also, along
      with the change, the message strings have been reformatted to be a bit
      more consistent.
      
      Last but not least, the hwptr reporting is enabled only when
      CONFIG_SND_PCM_XRUN_DEBUG is set.
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      f5914908
  7. 09 1月, 2014 1 次提交
  8. 15 8月, 2013 1 次提交
  9. 23 12月, 2011 1 次提交
  10. 16 11月, 2011 1 次提交
  11. 08 7月, 2009 1 次提交
    • T
      ALSA: Fix SG-buffer DMA with non-coherent architectures · cc6a8acd
      Takashi Iwai 提交于
      Using SG-buffers with dma_alloc_coherent() is often very inefficient
      on non-coherent architectures because a tracking record could be
      allocated in addition for each dma_alloc_coherent() call.
      Instead, simply disable SG-buffers but just allocate normal continuous
      buffers on non-supported (currently all but x86) architectures.
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      cc6a8acd
  12. 25 10月, 2008 1 次提交
  13. 30 7月, 2008 1 次提交
    • M
      ALSA: Build jack detection · 0d94e41a
      Mark Brown 提交于
      Since jack detection requires the input subsystem which may not be
      desired on small systems it is not built unless required by a driver
      that is being built. Drivers using jack detection should use a pattern
      like this:
      
      config SND_FOO
              tristate "..."
              ...
              select SND_JACK if INPUT=y || INPUT=SND
      
      to ensure that the jack detection API is enabled if the input subsystem
      is.  If the input subsystem is not enabled then a stub version of the
      API is provided.
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      Signed-off-by: NJaroslav Kysela <perex@perex.cz>
      0d94e41a
  14. 24 4月, 2008 1 次提交
  15. 16 10月, 2007 3 次提交
  16. 04 11月, 2005 1 次提交
  17. 24 8月, 2005 1 次提交
  18. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4