From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 203419] Logitech Group USB audio stopped working in 5.1-rc6
Date: Thu, 09 Apr 2020 12:39:05 +0000 [thread overview]
Message-ID: <bug-203419-208809-DjdMFGmoGm@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203419-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=203419
--- Comment #27 from Mathias Nyman (mathias.nyman@linux.intel.com) ---
Created attachment 288295
--> https://bugzilla.kernel.org/attachment.cgi?id=288295&action=edit
testpatch that doesn't clear TT buffer after protocol STALL
Adding same patch and comment here as in bug #207065, it might
help in this case as well.
"Traces show its related to Clearing TT buffer after a STALL on
endpoint 0.
The first stall looks like a protocol stall, not a function stall, meaning that
endpoint isn't really halted, just that the device does not support the
request in the control transfer.
Anyway, xhci starts clearing what it assumes is a halted endpoint,
including clearing the hub TT buffer.
Specs are a bit unclear if TT should be cleared in this case,
or at least I couldn't find it."
Attached is a tespatch that doesn't clear TT buffer on protocol stalls,
withexcessive tracing and debugging.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-04-09 12:39 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-203419-208809@https.bugzilla.kernel.org/>
2020-04-01 13:10 ` [Bug 203419] Logitech Group USB audio stopped working in 5.1-rc6 bugzilla-daemon
2020-04-01 16:00 ` Alan Stern
2020-04-01 16:00 ` bugzilla-daemon
2020-04-01 19:22 ` bugzilla-daemon
2020-04-02 13:34 ` bugzilla-daemon
2020-04-08 9:43 ` bugzilla-daemon
2020-04-08 10:00 ` bugzilla-daemon
2020-04-08 10:04 ` bugzilla-daemon
2020-04-08 12:49 ` bugzilla-daemon
2020-04-08 16:30 ` bugzilla-daemon
2020-04-09 12:39 ` bugzilla-daemon [this message]
2020-04-10 18:04 ` bugzilla-daemon
2020-07-02 14:13 ` bugzilla-daemon
2020-07-02 14:15 ` bugzilla-daemon
2020-07-02 19:10 ` bugzilla-daemon
2020-07-03 11:23 ` bugzilla-daemon
2020-07-09 9:22 ` bugzilla-daemon
2020-08-31 7:55 ` bugzilla-daemon
2020-08-31 7:56 ` bugzilla-daemon
2020-08-31 7:57 ` bugzilla-daemon
2020-09-01 6:55 ` bugzilla-daemon
2020-09-02 6:05 ` bugzilla-daemon
2020-09-02 11:34 ` bugzilla-daemon
2020-09-03 9:52 ` bugzilla-daemon
2020-09-04 12:29 ` bugzilla-daemon
2020-09-10 14:25 ` bugzilla-daemon
2020-10-06 14:22 ` bugzilla-daemon
2020-10-12 12:37 ` bugzilla-daemon
2020-12-01 4:27 ` bugzilla-daemon
2022-10-31 14:29 ` bugzilla-daemon
2022-10-31 15:15 ` bugzilla-daemon
2022-10-31 17:09 ` bugzilla-daemon
2022-10-31 19:11 ` 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-203419-208809-DjdMFGmoGm@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.