From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 212955] Possible kernel regression USB2 (not USB3) port EDIROL UA-101 (in USB 1.1 mode, not USB2) error -110
Date: Mon, 07 Jun 2021 03:47:36 +0000 [thread overview]
Message-ID: <bug-212955-208809-fyjaV1kMTE@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-212955-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=212955
--- Comment #20 from Lucas Endres (jaffa225man@gmail.com) ---
I sped through it this time with definite success:
The commit causing it was one I helped diagnose so that the UA-101's MIDI
device became available, but since I told Takashi Iwai about the issue and he
wanted me to check with you USB gurus, maybe we can help eachother in figuring
out why the snd-ua101 module doesn't work with its "Hi-SPEED" switch set to
"off" (USB1 mode) only. The snd-usb-audio module apparently did work for USB1
mode, but caused the MIDI port to be unavailable.
And, yes, its parent commit tested good
(473d5ae82d73c3b21160b725af0e247fa94d7832), and this really was tested as bad:
d763145312582c08c4e9ed99d61276cde8488256 is the first bad commit
commit d763145312582c08c4e9ed99d61276cde8488256
Author: Takashi Iwai <tiwai@suse.de>
Date: Thu Apr 8 09:56:56 2021 +0200
ALSA: usb-audio: Skip probe of UA-101 devices
UA-101 device and co are supported by another driver, snd-ua101, but
the USB audio class driver (snd-usb-audio) catches all and this
resulted in the lack of functionality like missing MIDI devices.
This patch introduces a sort of deny-listing for those devices to just
return -ENODEV at probe in snd-usb-audio driver, so that it falls back
to the probe by snd-ua101.
BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=212477
Link: https://lore.kernel.org/r/20210408075656.30184-1-tiwai@suse.de
Signed-off-by: Takashi Iwai <tiwai@suse.de>
sound/usb/card.c | 2 ++
sound/usb/quirks-table.h | 21 +++++++++++++++++++++
sound/usb/usbaudio.h | 1 +
3 files changed, 24 insertions(+)
I think it will, but can only hope that this time, it will lead to the
solution.
Thanks!
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2021-06-07 3:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 19:34 [Bug 212955] New: Possible kernel regression USB2 (not USB3) port EDIROL UA-101 (in USB 1.1 mode, not USB2) error -110 bugzilla-daemon
2021-05-05 20:20 ` [Bug 212955] " bugzilla-daemon
2021-05-06 5:12 ` bugzilla-daemon
2021-05-06 5:14 ` bugzilla-daemon
2021-05-06 5:17 ` bugzilla-daemon
2021-05-06 5:17 ` bugzilla-daemon
2021-05-06 15:45 ` bugzilla-daemon
2021-05-07 2:12 ` bugzilla-daemon
2021-05-07 2:21 ` bugzilla-daemon
2021-05-07 15:07 ` bugzilla-daemon
2021-05-08 3:10 ` bugzilla-daemon
2021-06-02 4:07 ` bugzilla-daemon
2021-06-02 4:25 ` bugzilla-daemon
2021-06-02 16:15 ` bugzilla-daemon
2021-06-02 18:15 ` bugzilla-daemon
2021-06-02 19:51 ` bugzilla-daemon
2021-06-02 19:54 ` bugzilla-daemon
2021-06-02 20:00 ` bugzilla-daemon
2021-06-03 4:42 ` bugzilla-daemon
2021-06-05 3:36 ` bugzilla-daemon
2021-06-07 3:47 ` bugzilla-daemon [this message]
2021-06-07 4:39 ` bugzilla-daemon
2021-06-07 15:16 ` bugzilla-daemon
2021-06-07 19:06 ` bugzilla-daemon
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=bug-212955-208809-fyjaV1kMTE@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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.