From: Clemens Ladisch <clemens@ladisch.de>
To: Torstein Hegge <hegge@resisty.net>
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, 05 Mar 2013 08:55:03 +0100 [thread overview]
Message-ID: <5135A4D7.2050301@ladisch.de> (raw)
In-Reply-To: <20130304213311.GG4452@pvv.ntnu.no>
Torstein Hegge wrote:
> On Mon, Mar 04, 2013 at 11:31:59AM +0100, Clemens Ladisch wrote:
>>>>> On 02.03.2013 14:04, Torstein Hegge wrote:
>>>>>> + 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 vaguely remember some such report. Better add this (0b05:17a8).
> I don't know what vendor/product id the Emotiva XDA-2 reports.
>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
(200c = Reloop, 054c = Sony)
Regards,
Clemens
next prev parent reply other threads:[~2013-03-05 7:55 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 [this message]
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=5135A4D7.2050301@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=hegge@resisty.net \
--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 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.