Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1373601 > unrolled thread
| Started by | Chris Bainbridge <chris.bainbridge@gmail.com> |
|---|---|
| First post | 2016-04-07 19:50 +0200 |
| Last post | 2016-04-07 19:50 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH] usb: core: hub: hub_port_init lock controller instead of bus Chris Bainbridge <chris.bainbridge@gmail.com> - 2016-04-07 19:50 +0200
| From | Chris Bainbridge <chris.bainbridge@gmail.com> |
|---|---|
| Date | 2016-04-07 19:50 +0200 |
| Subject | Re: [PATCH] usb: core: hub: hub_port_init lock controller instead of bus |
| Message-ID | <rlme6-7wf-21@gated-at.bofh.it> |
On Wed, Feb 10, 2016 at 07:13:38PM +0200, Mathias Nyman wrote: > > Most likely xhci is messed up after two device slots are in default state at the same time. > This happens when both threads are in hub_port_init() have called hub_port_reset() > > The issue becomes visible when the the descriptor read and set address both fail after > the port resets. > > xhci specs 4.5.3 has one tiny note about this: > "Note: Software shall not transition more than one Device Slot to the Default State at a time" > > So to me, and from xhci pov this patch looks like the correct solution, > but I might be missing some usb core side details. > > -Mathias > Just following up to see if this patch disappeared into the void?
Back to top | Article view | linux.kernel
csiph-web