<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/sound, branch v3.4.50</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/sound?h=v3.4.50</id>
<link rel='self' href='https://git.amat.us/linux/atom/sound?h=v3.4.50'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2013-06-13T16:44:53Z</updated>
<entry>
<title>ALSA: usb-audio - Fix invalid volume resolution on Logitech HD webcam c270</title>
<updated>2013-06-13T16:44:53Z</updated>
<author>
<name>Takashi Iwai</name>
<email>tiwai@suse.de</email>
</author>
<published>2013-06-05T06:35:26Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=395801f773ba978d4c0d3cb0675e534624ade228'/>
<id>urn:sha1:395801f773ba978d4c0d3cb0675e534624ade228</id>
<content type='text'>
commit 11e7064f35bb87da8f427d1aa4bbd8b7473a3993 upstream.

USB audio driver spews an error message when probing Logitech HD
webcam c270:
  ALSA mixer.c:1300 usb_audio: Warning! Unlikely big volume range (=6144), cval-&gt;res is probably wrong.
  ALSA mixer.c:1304 usb_audio: [5] FU [Mic Capture Volume] ch = 1, val = 1536/7680/1

Obviously the device needs a fixed volume resolution (cval-&gt;res = 384)
like other Logitech devices.

Bugzilla: https://bugzilla.novell.com/show_bug.cgi?id=821735

Reported-and-tested-by: Cristian Rodríguez &lt;crrodriguez@opensuse.org&gt;
Signed-off-by: Takashi Iwai &lt;tiwai@suse.de&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>ALSA: usb-audio - Apply Logitech QuickCam Pro 9000 quirk only to audio iface</title>
<updated>2013-06-13T16:44:53Z</updated>
<author>
<name>Takashi Iwai</name>
<email>tiwai@suse.de</email>
</author>
<published>2013-06-04T14:02:54Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=8e411de6df1711a8d930373bbccf044ba4573bcc'/>
<id>urn:sha1:8e411de6df1711a8d930373bbccf044ba4573bcc</id>
<content type='text'>
commit 8eafc0a161123d90617c9ca2eddfe87b382b1b89 upstream.

... instead of applying to all interfaces.

Reference: http://forums.gentoo.org/viewtopic-p-6886404.html

Signed-off-by: Takashi Iwai &lt;tiwai@suse.de&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>ALSA: usb-audio: fix Roland/Cakewalk UM-3G support</title>
<updated>2013-06-13T16:44:52Z</updated>
<author>
<name>Clemens Ladisch</name>
<email>clemens@ladisch.de</email>
</author>
<published>2013-06-02T17:49:07Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=6ba9458dbba742c68f123b7281bd2e382366b400'/>
<id>urn:sha1:6ba9458dbba742c68f123b7281bd2e382366b400</id>
<content type='text'>
commit a0c6d309c6df14655f9962f666d1da96318b0b7c upstream.

Commit 927c9423dd5f2d1c0b93d5e694ab84b4a5559713 (ALSA: usb-audio: add
Edirol UM-3G support) used a wrong quirk type, which would make the
driver refuse to attach with the error message "MIDIStreaming interface
descriptor not found".

Signed-off-by: Clemens Ladisch &lt;clemens@ladisch.de&gt;
Signed-off-by: Takashi Iwai &lt;tiwai@suse.de&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>ALSA: HDA: Fix Oops caused by dereference NULL pointer</title>
<updated>2013-05-19T17:54:36Z</updated>
<author>
<name>Wang YanQing</name>
<email>udknight@gmail.com</email>
</author>
<published>2013-05-07T03:27:33Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a85550214614cd7e66d995592dbd54b14db50c01'/>
<id>urn:sha1:a85550214614cd7e66d995592dbd54b14db50c01</id>
<content type='text'>
commit 2195b063f6609e4c6268f291683902f25eaf9aa6 upstream.

The interrupt handler azx_interrupt will call azx_update_rirb,
which may call snd_hda_queue_unsol_event, snd_hda_queue_unsol_event
will dereference chip-&gt;bus pointer.

The problem is we alloc chip-&gt;bus in azx_codec_create
which will be called after we enable IRQ and enable unsolicited
event in azx_probe.

This will cause Oops due dereference NULL pointer. I meet it, good luck:)

[Rearranged the NULL check before the tracepoint and added another
 NULL check of bus-&gt;workq -- tiwai]

Signed-off-by: Wang YanQing &lt;udknight@gmail.com&gt;
Signed-off-by: Takashi Iwai &lt;tiwai@suse.de&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>ASoC: wm8994: missing break in wm8994_aif3_hw_params()</title>
<updated>2013-05-19T17:54:34Z</updated>
<author>
<name>Dan Carpenter</name>
<email>dan.carpenter@oracle.com</email>
</author>
<published>2013-04-30T07:24:41Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=3fbe1888cace5d821aa59f804737c90ac6eb4542'/>
<id>urn:sha1:3fbe1888cace5d821aa59f804737c90ac6eb4542</id>
<content type='text'>
commit 4495e46fe18f198366961bb2b324a694ef8a9b44 upstream.

The missing break here means that we always return early and the
function is a no-op.

Signed-off-by: Dan Carpenter &lt;dan.carpenter@oracle.com&gt;
Signed-off-by: Mark Brown &lt;broonie@opensource.wolfsonmicro.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>ASoC: max98088: Fix logging of hardware revision.</title>
<updated>2013-05-08T02:51:55Z</updated>
<author>
<name>Dylan Reid</name>
<email>dgreid@chromium.org</email>
</author>
<published>2013-04-17T03:02:34Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a91a9f1e121a879f742f4c1718d58ba94e046dee'/>
<id>urn:sha1:a91a9f1e121a879f742f4c1718d58ba94e046dee</id>
<content type='text'>
commit 98682063549bedd6e2d2b6b7222f150c6fbce68c upstream.

The hardware revision of the codec is based at 0x40.  Subtract that
before convering to ASCII.  The same as it is done for 98095.

Signed-off-by: Dylan Reid &lt;dgreid@chromium.org&gt;
Signed-off-by: Mark Brown &lt;broonie@opensource.wolfsonmicro.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>ALSA: usb-audio: Fix autopm error during probing</title>
<updated>2013-05-08T02:51:55Z</updated>
<author>
<name>Takashi Iwai</name>
<email>tiwai@suse.de</email>
</author>
<published>2013-04-25T05:38:15Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=8a70ddb052fe8b95e31d76a940e48838bc6dc991'/>
<id>urn:sha1:8a70ddb052fe8b95e31d76a940e48838bc6dc991</id>
<content type='text'>
commit 60af3d037eb8c670dcce31401501d1271e7c5d95 upstream.

We've got strange errors in get_ctl_value() in mixer.c during
probing, e.g. on Hercules RMX2 DJ Controller:

  ALSA mixer.c:352 cannot get ctl value: req = 0x83, wValue = 0x201, wIndex = 0xa00, type = 4
  ALSA mixer.c:352 cannot get ctl value: req = 0x83, wValue = 0x200, wIndex = 0xa00, type = 4
  ....

It turned out that the culprit is autopm: snd_usb_autoresume() returns
-ENODEV when called during card-&gt;probing = 1.

Since the call itself during card-&gt;probing = 1 is valid, let's fix the
return value of snd_usb_autoresume() as success.

Reported-and-tested-by: Daniel Schürmann &lt;daschuer@mixxx.org&gt;
Signed-off-by: Takashi Iwai &lt;tiwai@suse.de&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>ALSA: usb-audio: disable autopm for MIDI devices</title>
<updated>2013-05-08T02:51:55Z</updated>
<author>
<name>Clemens Ladisch</name>
<email>clemens@ladisch.de</email>
</author>
<published>2013-04-15T13:59:51Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=b01ae289a30eb22f54d64951032f2a2b1d6bd532'/>
<id>urn:sha1:b01ae289a30eb22f54d64951032f2a2b1d6bd532</id>
<content type='text'>
commit cbc200bca4b51a8e2406d4b654d978f8503d430b upstream.

Commit 88a8516a2128 (ALSA: usbaudio: implement USB autosuspend)
introduced autopm for all USB audio/MIDI devices.  However, many MIDI
devices, such as synthesizers, do not merely transmit MIDI messages but
use their MIDI inputs to control other functions.  With autopm, these
devices would get powered down as soon as the last MIDI port device is
closed on the host.

Even some plain MIDI interfaces could get broken: they automatically
send Active Sensing messages while powered up, but as soon as these
messages cease, the receiving device would interpret this as an
accidental disconnection.

Commit f5f165418cab (ALSA: usb-audio: Fix missing autopm for MIDI input)
introduced another regression: some devices (e.g. the Roland GAIA SH-01)
are self-powered but do a reset whenever the USB interface's power state
changes.

To work around all this, just disable autopm for all USB MIDI devices.

Reported-by: Laurens Holst
Signed-off-by: Clemens Ladisch &lt;clemens@ladisch.de&gt;
Signed-off-by: Takashi Iwai &lt;tiwai@suse.de&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>ALSA: snd-usb: try harder to find USB_DT_CS_ENDPOINT</title>
<updated>2013-05-08T02:51:55Z</updated>
<author>
<name>Daniel Mack</name>
<email>zonque@gmail.com</email>
</author>
<published>2013-04-24T17:38:42Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=919fa1da0caf8b0fd323124257262654589057b2'/>
<id>urn:sha1:919fa1da0caf8b0fd323124257262654589057b2</id>
<content type='text'>
commit ebfc594c02148b6a85c2f178cf167a44a3c3ce10 upstream.

The USB_DT_CS_ENDPOINT class-specific endpoint descriptor is usually
stuffed directly after the standard USB endpoint descriptor, and this is
where the driver currently expects it to be.

There are, however, devices in the wild that have it the other way
around in their descriptor sets, so the USB_DT_CS_ENDPOINT comes
*before* the standard enpoint. Devices known to implement it that way
are "Sennheiser BTD-500" and Plantronics USB headsets.

When the driver can't find the USB_DT_CS_ENDPOINT, it won't be able to
change sample rates, as the bitmask for the validity of this command is
storen in bmAttributes of that descriptor.

Fix this by searching the entire interface instead of just the extra
bytes of the first endpoint, in case the latter fails.

Signed-off-by: Daniel Mack &lt;zonque@gmail.com&gt;
Reported-and-tested-by: Torstein Hegge &lt;hegge@resisty.net&gt;
Reported-and-tested-by: Yves G &lt;alsa-user@vivigatt.com&gt;
Signed-off-by: Takashi Iwai &lt;tiwai@suse.de&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>vm: convert snd_pcm_lib_mmap_iomem() to vm_iomap_memory() helper</title>
<updated>2013-04-26T04:19:56Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2013-04-19T17:01:04Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=ada37d85783ec8e314bd9b020b89d8a63a7587f2'/>
<id>urn:sha1:ada37d85783ec8e314bd9b020b89d8a63a7587f2</id>
<content type='text'>
commit 0fe09a45c4848b5b5607b968d959fdc1821c161d upstream.

This is my example conversion of a few existing mmap users.  The pcm
mmap case is one of the more straightforward ones.

Acked-by: Takashi Iwai &lt;tiwai@suse.de&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
</feed>
