1. 08 Sep, 2010 1 commit
    • Clemens Ladisch's avatar
      ALSA: virtuoso: work around missing reset in the Xonar DS Windows driver · 4c25b932
      Clemens Ladisch authored
      For the WM8776 chip, this driver uses a different sample format and
      more features than the Windows driver.  When rebooting from Linux into
      Windows, the latter driver does not reset the chip but assumes all its
      registers have their default settings, so we get garbled sound or, if
      the output happened to be muted before rebooting, no sound.
      
      To make that driver happy, hook our driver's cleanup function into the
      shutdown notifier and ensure that the chip gets reset.
      Signed-off-by: default avatarClemens Ladisch <clemens@ladisch.de>
      Reported-and-tested-by: Nathan Schagen
      Cc: <stable@kernel.org>
      Signed-off-by: default avatarTakashi Iwai <tiwai@suse.de>
      4c25b932
  2. 03 Sep, 2010 1 commit
    • Clemens Ladisch's avatar
      ALSA: usb-audio: fix detection of vendor-specific device protocol settings · a2acad82
      Clemens Ladisch authored
      The Audio Class v2 support code in 2.6.35 added checks for the
      bInterfaceProtocol field.  However, there are devices (usually those
      detected by vendor-specific quirks) that do not have one of the
      predefined values in this field, which made the driver reject them.
      
      To fix this regression, restore the old behaviour, i.e., assume that
      a device with an unknown bInterfaceProtocol field (other than
      UAC_VERSION_2) has more or less UAC-v1-compatible descriptors.
      
      [compile warning fixes by tiwai]
      Signed-off-by: default avatarClemens Ladisch <clemens@ladisch.de>
      Cc: Daniel Mack <daniel@caiaq.de>
      Cc: <stable@kernel.org>
      Signed-off-by: default avatarTakashi Iwai <tiwai@suse.de>
      a2acad82
  3. 02 Sep, 2010 1 commit
    • Daniel Mack's avatar
      ALSA: usb-audio: Assume first control interface is for audio · 7b6717e1
      Daniel Mack authored
      For devices with more than one control interface, let's assume the first
      one contains the audio controls. Unfortunately, there is no field in any
      of the descriptors to tell us whether a control interface is for audio
      or MIDI controls, so a better check is not easy to implement.
      
      On a composite device with audio and MIDI functions, for example, the
      code currently overwrites chip->ctrl_intf, causing operations on the
      control interface to fail if they are issued after the device probe.
      Signed-off-by: default avatarDaniel Mack <daniel@caiaq.de>
      Signed-off-by: default avatarTakashi Iwai <tiwai@suse.de>
      7b6717e1
  4. 29 Aug, 2010 3 commits
  5. 28 Aug, 2010 28 commits
  6. 27 Aug, 2010 6 commits