From: Alexander Tsoy <alexander@tsoy.me>
To: Tobias <toszlanyi@yahoo.de>, alsa-devel@alsa-project.org
Subject: Re: [alsa-devel] USB Audio Interface / Denon MC7000 and MC8000 controller
Date: Mon, 20 Jan 2020 11:22:18 +0300 [thread overview]
Message-ID: <697208e751dcbcc70cf00af7b625a4109b9c66cb.camel@tsoy.me> (raw)
In-Reply-To: <9457db14-4084-c0dd-5c89-821b35c3db66@yahoo.de>
В Сб, 14/12/2019 в 09:24 +0100, Tobias пишет:
> Hello dear ALSA developers.
>
> I have purchased a MC7000 controller in order to control MIXXX on
> Ubuntu
> 16.04. According to the Denon specification the controller should
> have
> been class compliant but there is an issue with the Audio interface
> to
> work properly giving following message ...
>
> $ dmesg
> ...
> > [ 74.522831] usb 1-1.3: new high-speed USB device number 6 using
> > xhci_hcd
> [ 74.623784] usb 1-1.3: New USB device found, idVendor=15e4,
> idProduct=8004
> [ 74.623789] usb 1-1.3: New USB device strings: Mfr=1, Product=2,
> SerialNumber=3
> [ 74.623793] usb 1-1.3: Product: DENON DJ MC7000
> [ 74.623796] usb 1-1.3: Manufacturer: DENON DJ
> [ 74.623798] usb 1-1.3: SerialNumber: 201603
> [ 74.625134] usb 1-1.3: clock source 65 is not valid, cannot use
>
> "|||clock source 65 is not valid, cannot use" is repeated
> uncountable
> times then
>
Please try to add delay after each class control request in
snd_usb_ctl_msg_quirk():
if (chip->usb_id == USB_ID(0x15e4, 0x8004) &&
(requesttype & USB_TYPE_MASK) == USB_TYPE_CLASS)
msleep(20);
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2020-01-20 8:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9457db14-4084-c0dd-5c89-821b35c3db66.ref@yahoo.de>
2019-12-14 8:24 ` [alsa-devel] USB Audio Interface / Denon MC7000 and MC8000 controller Tobias
2020-01-13 13:58 ` Tobias
2020-01-14 14:16 ` Takashi Iwai
2020-01-16 11:58 ` Tobias
2020-01-16 13:47 ` Takashi Iwai
2020-01-16 17:45 ` Tobias
2020-01-16 20:28 ` Takashi Iwai
2020-01-17 8:46 ` Tobias
2020-01-20 8:22 ` Alexander Tsoy [this message]
2020-01-21 8:17 ` Tobias
2020-01-21 8:44 ` Takashi Iwai
2020-01-21 10:59 ` Alexander Tsoy
2020-01-22 8:27 ` Oszlanyi Tobias
2020-02-03 10:23 ` Tobias
2020-02-05 19:07 ` Alexander Tsoy
2020-02-06 10:06 ` Tobias
2020-02-06 22:09 ` Alexander Tsoy
2020-02-07 8:15 ` Takashi Iwai
2020-02-07 14:39 ` Tobias
2020-02-07 17:45 ` Alexander Tsoy
2020-02-07 18:49 ` Tobias
2020-02-07 19:11 ` Alexander Tsoy
2020-02-07 20:15 ` Tobias
2020-02-07 16:59 ` Alexander Tsoy
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=697208e751dcbcc70cf00af7b625a4109b9c66cb.camel@tsoy.me \
--to=alexander@tsoy.me \
--cc=alsa-devel@alsa-project.org \
--cc=toszlanyi@yahoo.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 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).