1. 09 3月, 2009 1 次提交
  2. 05 2月, 2009 1 次提交
  3. 25 8月, 2008 2 次提交
    • T
      ALSA: Allocate larger pages in sgbuf · 51e9f2e6
      Takashi Iwai 提交于
      Most hardwares have limited buffer-descriptor table length.  This
      also restricts the max buffer size of the sound driver.
      For example, snd-hda-intel has 1MB buffer size limit, and this is
      because it can have at most 256 BDL entries.  For supporting larger
      buffers, we need to allocate larger pages even for sg-buffers.
      
      This patch changes the sgbuf allocation code to try to allocate
      larger pages first.  At each head of the allocated pages, the
      number of allocated pages is stored in the lowest bits of the
      corresponding entry of the table addr field.  This change isn't
      visible as long as the driver uses snd_sgbuf_get_addr() helper.
      
      Also, the patch adds a new function, snd_pcm_sgbuf_get_chunk_size().
      This returns the size of the chunk on continuous pages starting at
      the given position offset.  If the chunk reaches to a non-continuous
      page, it returns the size to the boundary.
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      Signed-off-by: NJaroslav Kysela <perex@perex.cz>
      51e9f2e6
    • T
      ALSA: Clean up SG-buffer helper functions and macros · 77a23f26
      Takashi Iwai 提交于
      Clean up SG-buffer helper functions and macros.  Helpers take substream
      as arguments now.
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      Signed-off-by: NJaroslav Kysela <perex@perex.cz>
      77a23f26
  4. 13 8月, 2008 1 次提交
  5. 01 8月, 2008 2 次提交
  6. 30 7月, 2008 1 次提交
    • P
      ALSA: Fix limit of 8 PCM devices in SNDRV_CTL_IOCTL_PCM_NEXT_DEVICE · 94239690
      Pawel MOLL 提交于
      When compiled with CONFIG_SND_DYNAMIC_MINORS the ALSA core is fine
      to have more than 8 PCM devices per card, except one place - the
      SNDRV_CTL_IOCTL_PCM_NEXT_DEVICE ioctl, which will not enumerate
      devices > 7. This patch fixes the issue, changing the devices list
      organisation.
      
      Instead of adding new device to the tail, the list is now kept always
      ordered (by card number, then device number). Thus, during enumeration,
      it is easy to discover the fact that there is no more given card's
      devices. The same limit was present in OSS emulation code. It has
      been fixed as well.
      
      Additionally the device field of struct snd_pcm is now int, instead of
      unsigned int, as there is no obvious reason for keeping it unsigned.
      This caused a lot of problems with comparing this value with other
      (almost always signed) variables. There is just one more place where
      device number is unsigned - in struct snd_pcm_info, which should be
      also sorted out in future.
      Signed-off-by: NPawel MOLL <pawel.moll@st.com>
      Signed-off-by: NJaroslav Kysela <perex@perex.cz>
      94239690
  7. 26 6月, 2008 1 次提交
    • J
      [ALSA] Revert "alsa: add annotations to bitwise type snd_pcm_hw_param_t" · eabe3228
      Jaroslav Kysela 提交于
      This reverts commit 36b34d2437104f323e09d7c6af6451d3c0b9c0cd.
      
      From: Al Viro <viro@ZenIV.linux.org.uk>
      
      WIW, *all* this stuff is not bitwise at all.  For crying out loud, half
      of these types are routinely used as array indices and loop variables...
      
      If anything, we want a different set of allowed operations - subtraction
      between elements of type (yielding integer), addition/subtraction of
      integer types not bigger than ours (yielding our type), comparisons,
      assignments (=, +=, -=, passing to function as argument, return from
      function, initializers) and second/third arguments in ?:.  With 0 *not*
      being allowed as a constant of such type.
      
      It's not bitwise; we may use the same infrastructure in sparse, but it
      should be a separate class of types (__attribute__((affine))).
      
      dma_addr_t is another candidate for the same treatment, but there we'll
      need helpers for conversions to hw-acceptable form (dma_to_le32(), etc.)
      and gradual conversion of drivers.
      
      ALSA ones and pm mess are absolutely straightforward cases, though.
      Signed-off-by: NJaroslav Kysela <perex@perex.cz>
      eabe3228
  8. 19 6月, 2008 1 次提交
  9. 01 2月, 2008 3 次提交
  10. 16 10月, 2007 5 次提交
  11. 11 5月, 2007 1 次提交
  12. 13 2月, 2007 1 次提交
  13. 09 2月, 2007 3 次提交
  14. 04 12月, 2006 1 次提交
  15. 01 10月, 2006 1 次提交
    • T
      [PATCH] maximum latency tracking: ALSA support · 9442e691
      Takashi Iwai 提交于
      Add maximum latency tracking to the ALSA subsystem for PCM playback.  In
      ALSA, the playback application controls the buffer size and thus indirectly
      the period of latency that it can deal with.  This patch uses 75% of the
      total available latency as threshold to announce to the latency subsystem;
      While 75% is a crude heuristic it's a quite reasonable one; the remaining
      25% can be used for all driver processing for the next samples which is
      also proportional to the size of the buffer.
      
      With ogg123 a latency setting of about 4msec was seen (at 44Khz), while
      with the "play" command a much longer maximum tolerable latency was seen.
      Other, more multimedia oriented players as well as games, will have a lot
      smaller buffers to allow better synchronization and those will actually get
      into the latency domains where there is impact on the power management
      rules.
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      Signed-off-by: NArjan van de Ven <arjan@linux.intel.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      9442e691
  16. 23 9月, 2006 1 次提交
  17. 23 6月, 2006 3 次提交
  18. 28 4月, 2006 1 次提交
  19. 12 4月, 2006 2 次提交
  20. 31 3月, 2006 2 次提交
  21. 22 3月, 2006 1 次提交
  22. 03 1月, 2006 3 次提交
  23. 04 11月, 2005 1 次提交
  24. 12 9月, 2005 1 次提交