From: Sarah Sharp <sarah.a.sharp@linux.intel.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: jerome huang <jerome.syno@gmail.com>,
"Xu, Andiry" <Andiry.Xu@amd.com>,
linux-usb@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: rt8192cu on USB3
Date: Thu, 22 Mar 2012 15:31:07 -0700 [thread overview]
Message-ID: <20120322223107.GA8877@xanatos> (raw)
In-Reply-To: <4F59800B.80407@lwfinger.net>
On Thu, Mar 08, 2012 at 09:59:07PM -0600, Larry Finger wrote:
> On 03/08/2012 09:28 PM, jerome huang wrote:
> >
> >It still got no any result if I wait for 30 sec (or longer) between
> >(original) step 2 and 3.
> >I double confirmed that it always does not work for steps: plugin ->
> >up -> scanning
> >and always works for steps: plugin -> up -> down -> up -> scanning.
> >
> >And sometimes it works for next down->up->scanning, sometimes it doesn't.
> >
> >Is the change of firmware loading in kernel 3.3 made by rtlwifi only,
> >or ring expansion in xhci is also necessary?
>
> The only changes are in the rtlwifi drivers. I don't have a USB 3
> device, thus I have no idea what might work there. I wrote something
> incorrect earlier. The new code is not in mainline 3.3, but it is in
> the wireless-testing git tree. If you want to try this, and don't
> want to get the whole tree, the new code is in the bleeding-edge
> compat-wireless package. Otherwise, I could send you the patches.
Larry, if the driver doesn't cancel an URB that the device doesn't
respond to, then it will just be left on the endpoint ring. If the
driver then tries to queue new transfers to that same endpoint, but the
device keeps NAKing the uncancelled transfer, then the endpoint ring
would fill up with unanswered transfers.
Perhaps some userspace or kernel portion is forgetting to cancel URBs
before moving onto the next thing? You said you moved to asynchronous
transfers, so maybe the problem lies there?
Jerome, the xHCI ring expansion patches have been merged for 3.4, so you
can test with Linus' latest tree and see if they help. If the ring
expands indefinitely, then there's probably an issue with the rtlwifi
drivers.
Sarah Sharp
next prev parent reply other threads:[~2012-03-22 22:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 2:03 rt8192cu on USB3 jerome huang
2012-03-08 2:16 ` jerome huang
2012-03-08 2:35 ` Larry Finger
2012-03-08 6:35 ` jerome huang
2012-03-08 7:06 ` Andiry Xu
2012-03-08 7:11 ` Andiry Xu
[not found] ` <2A76B9D36150BE4293842BC2FE8FF165016A31@SCYBEXDAG04.amd.com>
2012-03-08 10:32 ` jerome huang
2012-03-08 11:26 ` jerome huang
2012-03-08 17:56 ` Larry Finger
2012-03-09 3:28 ` jerome huang
2012-03-09 3:59 ` Larry Finger
2012-03-09 7:39 ` jerome huang
2012-03-09 15:04 ` Larry Finger
2012-03-09 16:02 ` jerome huang
2012-03-22 22:31 ` Sarah Sharp [this message]
2012-03-23 2:24 ` Larry Finger
2012-03-23 20:34 ` Sarah Sharp
2012-03-24 2:16 ` Richard Farina
2012-03-24 4:59 ` Larry Finger
2012-04-05 22:49 ` Sarah Sharp
2012-03-24 4:55 ` Larry Finger
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=20120322223107.GA8877@xanatos \
--to=sarah.a.sharp@linux.intel.com \
--cc=Andiry.Xu@amd.com \
--cc=Larry.Finger@lwfinger.net \
--cc=jerome.syno@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@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).