From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 208357] snd-usb-audio broken for 06f8:b000 since 4.9.189
Date: Thu, 09 Jul 2020 16:47:19 +0000 [thread overview]
Message-ID: <bug-208357-208809-ab16KfFTqT@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-208357-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=208357
--- Comment #4 from Alan Stern (stern@rowland.harvard.edu) ---
Well, the problem is clear enough:
Interface 5 uses endpoint 1-OUT in alternate setting 1, 1-IN in
alternate setting 2, and both 1-OUT and 1-IN in alternate setting 3.
At the same time, interface 7 alternate setting 1 uses endpoint 1-OUT
and interface 8 alternate setting 1 uses endpoint 1-IN.
According to the USB spec, different interfaces are not allowed to use the same
endpoints. (The exact statement, in section 9.6.3 of the USB-2.0
specification, is: "An endpoint is not shared among interfaces within a single
configuration unless the endpoint is used by alternate settings of the same
interface." IMO the word "unless" should have been "except when".)
This device would never pass the USB validation suite and would not be allowed
to use the USB logo.
Under the circumstances, it looks like interface 5 is not intended for general
use, since it is described as Vendor-Specific. Does it get used in your
system? The answer can be found in the /sys/kernel/debug/usb/devices file
(with the device plugged in under an earlier kernel where it works okay).
It may turn out that the way to deal with this problem is to add
ENDPOINT_IGNORE quirks for interface 5 on this device.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-07-09 16:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-208357-208809@https.bugzilla.kernel.org/>
2020-07-09 14:08 ` [Bug 208357] snd-usb-audio broken for 06f8:b000 since 4.9.189 bugzilla-daemon
2020-07-09 15:04 ` bugzilla-daemon
2020-07-09 15:31 ` bugzilla-daemon
2020-07-09 16:47 ` bugzilla-daemon [this message]
2020-07-09 17:57 ` bugzilla-daemon
2020-07-09 19:26 ` bugzilla-daemon
2020-07-10 16:08 ` bugzilla-daemon
2020-07-14 19:11 ` bugzilla-daemon
2020-07-14 19:18 ` bugzilla-daemon
2020-10-01 9:01 ` bugzilla-daemon
2020-11-19 17:03 ` 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-208357-208809-ab16KfFTqT@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 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).