[alsa-devel] [PATCH] ALSA: usb: Work around CM6631 sample rate change bug

[Torstein Hegge]

On Tue, Mar 05, 2013 at 08:55:03AM +0100, Clemens Ladisch wrote:
> 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 got an email from a Xonar user experiencing the problem. I'll add it.

> > 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)

I'm not quite sure how to interpret that. I guess most of those are
similar devices that doesn't necessarily need this workaround?


Torstein