alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Torstein Hegge <hegge@resisty.net>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: Takashi Iwai <tiwai@suse.de>,
	alsa-devel@alsa-project.org, Daniel Mack <zonque@gmail.com>
Subject: Re: [PATCH] ALSA: usb: Work around CM6631 sample rate change bug
Date: Mon, 4 Mar 2013 22:33:11 +0100	[thread overview]
Message-ID: <20130304213311.GG4452@pvv.ntnu.no> (raw)
In-Reply-To: <5134781F.4050607@ladisch.de>

On Mon, Mar 04, 2013 at 11:31:59AM +0100, Clemens Ladisch wrote:
> Takashi Iwai wrote:
> > Torstein Hegge wrote:
> >> On Sat, Mar 02, 2013 at 02:12:33PM +0100, Daniel Mack wrote:
> >>> On 02.03.2013 14:04, Torstein Hegge wrote:
> >>>> The C-Media CM6631 USB-to-S/PDIF receiver doesn't respond to changes in
> >>>> sampling frequency while the interface is active.
> 
> >>>> +	case USB_ID(0x0d8c, 0x0304): /* C-Media - Schiit USB Interface */
> >>>> +	case USB_ID(0x0d8c, 0x0309): /* C-Media CM6631 */
> 
> There are other CM6631-based devices.

Most CM6631 devices with sample rate change problems reported has one of those
two ids, as far as I can see. The Asus Xonar Essence One uses the CM6631, but
it is listed in the wiki as supported, without any comments about any such
issue. I don't know what vendor/product id the Emotiva XDA-2 reports. Did you
think of any device in particular?

> > If the reset of interface is needed only when *changing* SRC, we can
> > check the current rate against the previous rate and skip the reset?
> 
> Or, if we want to be more similar to what many Windows drivers do, reset
> the interface to altsetting zero before setting it again.

I see that is done other places in the usb module where the intention is
to reset the device. It doesn't seem to make any difference one way or
the other in this case. I'll do a reset to altsetting zero first in the
next version of this patch.

Thanks.

Torstein

  reply	other threads:[~2013-03-04 21:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-02 13:04 [PATCH] ALSA: usb: Work around CM6631 sample rate change bug Torstein Hegge
2013-03-02 13:12 ` Daniel Mack
2013-03-03 19:29   ` Torstein Hegge
2013-03-04  8:53     ` Takashi Iwai
2013-03-04 10:31       ` Clemens Ladisch
2013-03-04 21:33         ` Torstein Hegge [this message]
2013-03-05  7:55           ` Clemens Ladisch
2013-03-05 10:22             ` Torstein Hegge
2013-03-05 10:35               ` Clemens Ladisch
2013-03-05 21:24                 ` Torstein Hegge
2013-03-05 21:39                   ` Clemens Ladisch
2013-03-04 21:29       ` Torstein Hegge

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=20130304213311.GG4452@pvv.ntnu.no \
    --to=hegge@resisty.net \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    --cc=tiwai@suse.de \
    --cc=zonque@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).