Skip to content

cloud-kernel
cloud-kernel

openanolis / cloud-kernel
1 年多 前同步成功

通知 161
Star 36
Fork 7
cloud-kernel
cloud-kernel
切换分支/标签
  1. 16 10月, 2017 1 次提交
  3. 09 10月, 2017 1 次提交
  5. 21 9月, 2017 1 次提交
  7. 22 8月, 2017 1 次提交
  9. 18 8月, 2017 1 次提交
  11. 15 8月, 2017 1 次提交
  13. 13 8月, 2017 1 次提交
  15. 15 5月, 2017 1 次提交
  17. 10 1月, 2017 1 次提交
  19. 28 12月, 2016 1 次提交
  21. 13 12月, 2016 1 次提交
  23. 29 8月, 2016 1 次提交
  25. 22 8月, 2016 2 次提交
  27. 09 8月, 2016 2 次提交
  29. 12 5月, 2016 1 次提交
  31. 29 4月, 2016 1 次提交
  33. 06 4月, 2016 1 次提交
  35. 04 4月, 2016 1 次提交
  37. 01 4月, 2016 1 次提交
  39. 20 3月, 2016 1 次提交
  41. 16 3月, 2016 2 次提交
  43. 01 3月, 2016 1 次提交
  45. 30 1月, 2016 1 次提交
  47. 29 1月, 2016 3 次提交
  49. 26 1月, 2016 1 次提交
  51. 11 1月, 2016 1 次提交
  53. 14 12月, 2015 1 次提交
  55. 16 11月, 2015 1 次提交
    • C
      ALSA: usb-audio: prevent CH345 multiport output SysEx corruption · 1ca8b201
      由 Clemens Ladisch 提交于 
      The CH345 USB MIDI chip has two output ports.  However, they are
multiplexed through one pin, and the number of ports cannot be reduced
even for hardware that implements only one connector, so for those
devices, data sent to either port ends up on the same hardware output.
This becomes a problem when both ports are used at the same time, as
longer MIDI commands (such as SysEx messages) are likely to be
interrupted by messages from the other port, and thus to get lost.

It would not be possible for the driver to detect how many ports the
device actually has, except that in practice, _all_ devices built with
the CH345 have only one port.  So we can just ignore the device's
descriptors, and hardcode one output port.
Signed-off-by: NClemens Ladisch <clemens@ladisch.de>
Cc: stable@vger.kernel.org
Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      1ca8b201
  57. 09 11月, 2015 1 次提交
  59. 19 10月, 2015 1 次提交
    • R
      ALSA: USB-audio: Add quirk for Zoom R16/24 playback · e0570446
      由 Ricard Wanderlof 提交于 
      The Zoom R16/24 have a nonstandard playback format where each isochronous
packet contains a length descriptor in the first four bytes. (Curiously,
capture data does not contain this and requires no quirk.)

The quirk involves adding the extra length descriptor whenever outgoing
isochronous packets are generated, both in pcm.c (outgoing audio) and
endpoint.c (silent data).

In order to make the quirk as unintrusive as possible, for
pcm.c:prepare_playback_urb(), the isochronous packet descriptors are
initially set up in the same way no matter if the quirk is enabled or not.
Once it is time to actually copy the data into the outgoing packet buffer
(together with the added length descriptors) the isochronous descriptors
are adjusted in order take the increased payload length into account.

For endpoint.c:prepare_silent_urb() it makes more sense to modify the
actual function, partly because the function is less complex to start with
and partly because it is not as time-critical as prepare_playback_urb()
(whose bulk is run with interrupts disabled), so the (minute) additional
time spent in the non-quirk case is motivated by the simplicity of having
a single function for all cases.

The quirk is controlled by the new tx_length_quirk member in struct
snd_usb_substream and struct snd_usb_audio, which is conveyed to pcm.c
and endpoint.c from quirks.c in a similar manner to the txfr_quirk member
in the same structs.

In contrast to txfr_quirk however, the quirk is enabled directly in
quirks.c:create_standard_audio_quirk() by checking the USB ID in that
function. Another option would be to introduce a new
QUIRK_AUDIO_ZOOM_INTERFACE or somesuch, which would have made the quirk
very plain to see in the quirk table, but it was felt that the additional
code needed to implement it this way would just make the implementation
more complex with no real gain.

Tested with a Zoom R16, both by doing capture and playback separately
using arecord and aplay (8 channel capture and 2 channel playback,
respectively), as well as capture and playback together using Ardour, as
well as Audacity and Qtractor together with jackd.

The R24 is reportedly compatible with the R16 when used as an audio
interface. Both devices share the same USB ID and have the same number of
inputs (8) and outputs (2). Therefore "R16/24" is mentioned throughout the
patch.

Regression tested using an Edirol UA-5 in both class compliant (16-bit)
and "advanced" (24 bit, forces the use of quirks) modes.
Signed-off-by: NRicard Wanderlof <ricardw@axis.com>
Tested-by: NPanu Matilainen <pmatilai@laiskiainen.org>
Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      e0570446
  61. 21 8月, 2015 1 次提交
  63. 08 6月, 2015 1 次提交
  65. 30 5月, 2015 1 次提交
  67. 24 5月, 2015 1 次提交
  69. 19 5月, 2015 1 次提交