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: Tue, 5 Mar 2013 22:24:24 +0100 [thread overview]
Message-ID: <20130305212423.GC20417@pvv.ntnu.no> (raw)
In-Reply-To: <5135CA77.2000805@ladisch.de>
On Tue, Mar 05, 2013 at 11:35:35AM +0100, Clemens Ladisch wrote:
> Torstein Hegge wrote:
> > On Tue, Mar 05, 2013 at 08:55:03AM +0100, Clemens Ladisch wrote:
> >> From that driver's .inf file:
> >>
> >> %CMUACWO.DeviceDesc%=CMUACWO,USB\VID_0D8C&PID_0301&MI_00
> >> %CMUACWO.DeviceDesc%=CMUACWO,USB\VID_0D8C&PID_0302&MI_00
> >> %CMUACWO.DeviceDesc%=CMUACWO,USB\VID_0D8C&PID_0304&MI_00
> >> %CMUACWO.DeviceDesc%=CMUACWO,USB\VID_0D8C&PID_0305&MI_00
> >> %CMUACWO.DeviceDesc%=CMUACWO,USB\VID_0D8C&PID_0306&MI_00
> >> %CMUACWO.DeviceDesc%=CMUACWO,USB\VID_0D8C&PID_0309&MI_00
> >> %CMUACWO.DeviceDesc%=CMUACWO,USB\VID_0D8C&PID_0310&MI_00
> >> %CMUACWO.DeviceDesc%=CMUACWO,USB\VID_0D8C&PID_0311&MI_00 ;CM6610A
> >> %CMUACWO.DeviceDesc%=CMUACWO,USB\VID_0D8C&PID_0312&MI_00 ;CM6620A
> >> %CMUACWO.DeviceDesc%=CMUACWO,USB\VID_0D8C&PID_0313&MI_00 ;CM6630A
> >> %CMUACWO.DeviceDesc%=CMUACWO,USB\VID_0D8C&PID_0314&MI_00 ;CM6631A
> >> %CMUACWO.DeviceDesc%=CMUACWO,USB\VID_0D8C&PID_0319&MI_00 ;CM6631A
> >> %CMUACWO.DeviceDesc%=CMUACWO,USB\VID_0D8C&PID_0315&MI_00 ;CM6632A
> >> %CMUACWO.DeviceDesc%=CMUACWO,USB\VID_200C&PID_1030&MI_00
> >> %CMUACWO.DeviceDesc%=CMUACWO,USB\VID_054C&PID_06CF&MI_00
> >
> > I'm not quite sure how to interpret that. I guess most of those are
> > similar devices that doesn't necessarily need this workaround?
>
> Those are all the IDs that the C-Media driver attaches to. The
> hardware is always the same; I would be surprised if the firmware
> did not have the same bug.
The ids listed covers CM6610, CM6620 and CM6631, which are distinct
pieces of hardware, or at least they are sold as if they were. It might
be a fair assumption that all current C-Media UAC V2.0 devices have this
issue. However, I'm not able to test with anything other than CM6631.
The complete list then looks like:
switch (chip->usb_id) {
/* C-Media CM6610/CM6620/CM6631 */
case USB_ID(0x054c, 0x06cf): /* Sony */
case USB_ID(0x0b05, 0x17a8): /* Asus Xonar Essence One */
case USB_ID(0x0d8c, 0x0301):
case USB_ID(0x0d8c, 0x0302):
case USB_ID(0x0d8c, 0x0304): /* CM6631 (Schiit) */
case USB_ID(0x0d8c, 0x0305):
case USB_ID(0x0d8c, 0x0306):
case USB_ID(0x0d8c, 0x0309): /* CM6631 */
case USB_ID(0x0d8c, 0x0310):
case USB_ID(0x0d8c, 0x0311): /* CM6610A */
case USB_ID(0x0d8c, 0x0312): /* CM6620A */
case USB_ID(0x0d8c, 0x0313): /* CM6630A */
case USB_ID(0x0d8c, 0x0314): /* CM6631A */
case USB_ID(0x0d8c, 0x0315): /* CM6632A */
case USB_ID(0x0d8c, 0x0319): /* CM6631A */
case USB_ID(0x200c, 0x1030): /* Reloop */
[...]
}
Torstein
next prev parent reply other threads:[~2013-03-05 21:24 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
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 [this message]
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=20130305212423.GC20417@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).