From: Daniel Mack <zonque@gmail.com>
To: Torstein Hegge <hegge@resisty.net>
Cc: Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, Clemens Ladisch <clemens@ladisch.de>
Subject: Re: [PATCH v5] ALSA: usb: Work around CM6631 sample rate change bug
Date: Wed, 27 Mar 2013 12:52:14 +0100 [thread overview]
Message-ID: <5152DD6E.6040707@gmail.com> (raw)
In-Reply-To: <20130327114703.GE18838@pvv.ntnu.no>
On 27.03.2013 12:47, Torstein Hegge wrote:
> On Wed, Mar 27, 2013 at 11:09:01 +0100, Clemens Ladisch wrote:
>> Torstein Hegge wrote:
>>> The C-Media CM6631 USB receiver doesn't respond to changes in sample rate
>>> while the interface is active. The same behavior is observed in other UAC2
>>> hardware like the VIA VT1731.
>>
>> Might it be possible that these devices have reset the interface (see
>> UAC2 section 3.16.3), and that the driver hasn't noticed this because it
>> doesn't handle Active Alternate Setting Control interrupts?
>
> If that was the case, wouldn't the device be in altsetting zero after
> the sample rate set and not be able to output sound at all? And as long
> as the current altsetting supports the target sample rate as reported in
> /proc/asound/card1/stream0, Active Alternate Setting Control shouldn't
> have to be invoked.
You could just try and catch that currently unhandled interrupt. We
should support that anyway at some point ...
Daniel
next prev parent reply other threads:[~2013-03-27 11:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 21:10 [PATCH v5] ALSA: usb: Work around CM6631 sample rate change bug Torstein Hegge
2013-03-27 10:09 ` Clemens Ladisch
2013-03-27 11:47 ` Torstein Hegge
2013-03-27 11:52 ` Daniel Mack [this message]
2013-03-27 12:46 ` Torstein Hegge
2013-04-03 9:47 ` Takashi Iwai
2013-04-03 10:15 ` Clemens Ladisch
2013-04-03 17:22 ` Takashi Iwai
2013-04-03 21:22 ` Eldad Zack
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5152DD6E.6040707@gmail.com \
--to=zonque@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=hegge@resisty.net \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.