From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 207065] C-media USB audio device stops working from 5.2.0-rc3 onwards
Date: Thu, 09 Apr 2020 14:01:41 +0000 [thread overview]
Message-ID: <bug-207065-208809-g3C6ph6dOQ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-207065-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=207065
--- Comment #6 from Alan Stern (stern@rowland.harvard.edu) ---
On Thu, 9 Apr 2020 bugzilla-daemon@bugzilla.kernel.org wrote:
> --- Comment #4 from Mathias Nyman (mathias.nyman@linux.intel.com) ---
> Thanks, 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.
TTs should be cleared when an error occurs in the protocol. STALL
isn't an error; a real error would be a timeout or CRC mismatch or URB
cancellation, things like that -- things that might leave the TT in a
busy state (because it hasn't sent its final status back to the host)
when it ought to be idle. Sending a STALL isn't a protocol error and
it does clear the TT status.
This is discussed (not as explicitly as one might want) in sections
11.17.3 and 11.17.5 of the USB-2.0 specification.
Alan Stern
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-04-09 14:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 15:57 [Bug 207065] New: C-media USB audio device stops working from 5.2.0-rc3 onwards bugzilla-daemon
2020-04-02 16:00 ` [Bug 207065] " bugzilla-daemon
2020-04-02 16:01 ` bugzilla-daemon
2020-04-08 10:08 ` bugzilla-daemon
2020-04-09 12:32 ` bugzilla-daemon
2020-04-09 14:01 ` Alan Stern
2020-04-09 12:34 ` bugzilla-daemon
2020-04-09 14:01 ` bugzilla-daemon [this message]
2020-04-10 17:58 ` bugzilla-daemon
2020-04-14 10:07 ` bugzilla-daemon
2020-04-14 16:30 ` bugzilla-daemon
2020-04-14 16:30 ` bugzilla-daemon
2020-04-14 16:34 ` bugzilla-daemon
2020-04-16 13:00 ` bugzilla-daemon
2020-09-29 10:58 ` bugzilla-daemon
2020-09-29 10:59 ` bugzilla-daemon
2020-09-29 11:02 ` bugzilla-daemon
2020-09-29 11:50 ` bugzilla-daemon
2020-09-29 11:53 ` 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-207065-208809-g3C6ph6dOQ@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.