28 Jun, 2013

1 commit

  • This patch is adding extensive support (beside standard usb audio class)
    for Audio Advantage Micro II usb sound card.
    Features included:
    - Access to AES bits (so now sending the IEC61937 compliant stream is
    possible).
    - Mixer SPDIF control added to turn on/off the optical transmitter.

    Signed-off-by: Przemek Rudy
    Signed-off-by: Takashi Iwai

    Przemek Rudy
     

07 Apr, 2013

1 commit

  • The usb_control_msg() function expects __u16 types and performs
    the endianness conversions by itself.
    However, in three places, a conversion is performed before it is
    handed over to usb_control_msg(), which leads to a double conversion
    (= no conversion):
    * snd_usb_nativeinstruments_boot_quirk()
    * snd_nativeinstruments_control_get()
    * snd_nativeinstruments_control_put()

    Caught by sparse:

    sound/usb/mixer_quirks.c:512:38: warning: incorrect type in argument 6 (different base types)
    sound/usb/mixer_quirks.c:512:38: expected unsigned short [unsigned] [usertype] index
    sound/usb/mixer_quirks.c:512:38: got restricted __le16 [usertype]
    sound/usb/mixer_quirks.c:543:35: warning: incorrect type in argument 5 (different base types)
    sound/usb/mixer_quirks.c:543:35: expected unsigned short [unsigned] [usertype] value
    sound/usb/mixer_quirks.c:543:35: got restricted __le16 [usertype]
    sound/usb/mixer_quirks.c:543:56: warning: incorrect type in argument 6 (different base types)
    sound/usb/mixer_quirks.c:543:56: expected unsigned short [unsigned] [usertype] index
    sound/usb/mixer_quirks.c:543:56: got restricted __le16 [usertype]
    sound/usb/quirks.c:502:35: warning: incorrect type in argument 5 (different base types)
    sound/usb/quirks.c:502:35: expected unsigned short [unsigned] [usertype] value
    sound/usb/quirks.c:502:35: got restricted __le16 [usertype]

    Signed-off-by: Eldad Zack
    Acked-by: Daniel Mack
    Cc:
    Signed-off-by: Takashi Iwai

    Eldad Zack
     

11 Feb, 2013

1 commit

  • Adds quirks and mixer support for the M-Audio Fast Track C600 USB
    audio interface. This device is very similar to the C400 - the C600
    simply has some more inputs and outputs, so the existing C400 support
    is extended to support this device as well.

    Signed-off-by: Matt Gruskin
    Signed-off-by: Takashi Iwai

    Matt Gruskin
     

10 Jan, 2013

1 commit


12 Dec, 2012

1 commit


29 Nov, 2012

3 commits

  • Add a mixer quirks for the M-Audio Fast Track C400
    and create the following:

    * Volume controls
    * Effect Type (reusing FTU controls)
    * Effect Volume
    * Effect Send/Return
    * Effect Program
    * Effect Feedback

    Signed-off-by: Eldad Zack
    Signed-off-by: Takashi Iwai

    Eldad Zack
     
  • Adds the unit ID and the control as parameters to the creation of the
    effect unit control for the M-Audio Fast Track Ultra. This allows the
    code to be shared with other devices that use different unit ID and
    control, such as the M-Audio Fast Track C400.

    Signed-off-by: Eldad Zack
    Signed-off-by: Takashi Iwai

    Eldad Zack
     
  • Currently, channel IDs exceeding 31 (0x1f) cannot be used.
    The channel ID is derived from the cmask. Extending cmask
    to a 64-bit type would only allow it to go up to 63 (0x3f).
    Some devices have channel IDs exceeding that as well.
    To address that, add an offset to the mixer element which
    is then accounted for in the UAC set/get functions.

    Signed-off-by: Eldad Zack
    Signed-off-by: Takashi Iwai

    Eldad Zack
     

30 Oct, 2012

1 commit


11 Jun, 2012

2 commits


12 May, 2012

1 commit

  • Explained by Takashi in

    > The reason is because get_min_max*() isn't called in the place you
    > created these controls, and get_min_max() would be called only for
    > integer volumes later even if uninitialized. A short cut for booleans.

    Signed-off-by: Mark Hills
    Signed-off-by: Takashi Iwai

    Mark Hills
     

24 Apr, 2012

5 commits


15 Apr, 2012

1 commit


27 Sep, 2011

1 commit

  • There are certain devices that are reportedly so slow that they need
    more than 100 ms to handle control transfers. Therefore, increase the
    timeout in mixer(_quirks).c to 1000 ms.

    The timeout parameter of snd_usb_ctl_msg() is now constant, so we can
    drop it.

    Reported-by: Felipe Balbi
    Signed-off-by: Clemens Ladisch
    Signed-off-by: Takashi Iwai

    Clemens Ladisch
     

25 May, 2011

1 commit


18 May, 2011

2 commits


14 Apr, 2011

1 commit

  • This new device by Native Instruments is also compliant to the USB
    standard v2.0, but hides this detail at when connected.

    It needs the same boot quirks than other models, and also has two
    non-class-compliant mixer controls.

    Signed-off-by: Daniel Mack
    Signed-off-by: Takashi Iwai

    Daniel Mack
     

15 Feb, 2011

2 commits

  • The number of cases has increased so use switch-case rather than
    if-statements.

    Signed-off-by: Daniel Mack
    Signed-off-by: Takashi Iwai

    Daniel Mack
     
  • The MK2 generation of Native Instruments' sound cards are in fact
    compliant to the USB audio standard of version 2 and other approved USB
    standards. However, they come up as vendor-specific device when first
    connected but can be told to come up with a new set of descriptors
    upon their next enumeration. The interfaces announced by the new
    descriptors will be handled by the kernel's class drivers. This is done
    by issuing a vendor specific device request and sending the device to
    reset.

    There are also some vendor-specific USB requests for some mixer elements
    that can't be exported in a standard compliant way. The driver now
    supports them with quirks handling mechanisms.

    Signed-off-by: Daniel Mack
    Signed-off-by: Takashi Iwai

    Daniel Mack
     

02 Nov, 2010

1 commit

  • This patch adds support for Power/Status LED on Creative USB X-Fi S51.
    There is just one LED on the device. The LED can either be On or it
    can be set to Blink. There doesn't seem to be a way to switch it off.
    The control message to change LED status is similar to that of
    audigy2nx except that the index is to be set to 0 and value is 1 for
    Blink and 0 for On.

    The 'Power LED' control in alsamixer when muted will cause the LED to
    Blink continuously. When unmuted the LED will stay On. The Creative
    driver under Windows sets the LED to blink whenever audio is muted.
    This LED can be treated as the CMSS LED but I figured since there is
    just one LED, it should be treated as the Power LED. Is that alright?

    I've also changed the comment "Usb X-Fi" to "Usb X-Fi S51" as there
    are other external X-Fi devices from Creative like Usb X-Fi Go and
    Xmod. The volume knob and LED support patch doesn't apply to them.

    Signed-off-by: Mandar Joshi
    Signed-off-by: Takashi Iwai

    Mandar Joshi
     

24 Oct, 2010

1 commit


29 Mar, 2010

1 commit


12 Mar, 2010

2 commits