From: Takashi Iwai <tiwai@suse.de>
To: Tobias <toszlanyi@yahoo.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [alsa-devel] USB Audio Interface / Denon MC7000 and MC8000 controller
Date: Thu, 16 Jan 2020 14:47:20 +0100 [thread overview]
Message-ID: <s5h7e1r7btj.wl-tiwai@suse.de> (raw)
In-Reply-To: <c3904fd3-5e02-fa20-bf82-46b7ee324245@yahoo.de>
On Thu, 16 Jan 2020 12:58:00 +0100,
Tobias wrote:
>
> Thank you for taking care of this...
>
> I have tried with the latest Kernel 5.4.11 in Ubuntu 16.04 and
> $ dmesg
> still shows
> "clock source 65 is not valid, cannot use"
>
> My current running stable system is
>
> $ uname -a
> $ Linux tobias-V130 4.15.0-23-generic #25~16.04.1 SMP Fri Dec 20
> 20:16:19 CET 2019 x86_64 x86_64 x86_64 GNU/Linux
>
> in where I applied the chane described in here:
> https://alsa-user.narkive.com/2tDAO87f/troubleshooting-new-usb-audio-device#post11
>
> Just for my understanding what you now need me to do...
> deleting the line in /sound/usb/clock.c that states "return -ENXIO;"
> and compile the kernel again.
Yes, and with that, the error message still remains. That's not
wrong. The question is to identify who calls this function.
So...
> Clemes mentioned in his last post to add logging but I have no idea
> what he means by that. Can you briefly guide me what I would need to
> do?
... try the patch below instead. This should work for the recent
kernels. It'll give Oops-like kernel WARNING with stack traces, so
show them. There can be multiple occurrences.
Takashi
diff --git a/sound/usb/clock.c b/sound/usb/clock.c
index 018b1ecb5404..8d92a946f978 100644
--- a/sound/usb/clock.c
+++ b/sound/usb/clock.c
@@ -219,10 +219,10 @@ static int __uac_clock_find_source(struct snd_usb_audio *chip, int entity_id,
entity_id = source->bClockID;
if (validate && !uac_clock_source_is_valid(chip, UAC_VERSION_2,
entity_id)) {
- usb_audio_err(chip,
+ WARN(1,
"clock source %d is not valid, cannot use\n",
entity_id);
- return -ENXIO;
+ /* return -ENXIO; */
}
return entity_id;
}
_______________________________________________
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-16 13:48 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 [this message]
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
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=s5h7e1r7btj.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--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