On Fri, Aug 16, 2013 at 10:33:04AM -0500, Felipe Balbi wrote: > On Fri, Aug 16, 2013 at 08:19:02AM -0700, Greg Kroah-Hartman wrote: > > On Fri, Aug 16, 2013 at 09:58:25AM -0500, Felipe Balbi wrote: > > > Hi, > > > > > > On Thu, Aug 15, 2013 at 09:28:20PM -0700, Greg Kroah-Hartman wrote: > > > > > But should be also met for ARM SOC which use dwc3 controller as xHCI > > > > > controller. Because DWC3 driver register xHCI as platform driver by > > > > > default. So this issue can be reproduce. > > > > > > > > Which system can I reproduce this on? Do you know of a board with a > > > > dwc3 controller running in xHCI mode that I can get to test with (I > > > > would _love_ to get an ARM board running in xHCI mode for testing.) > > > > > > omap5432 uEVM which can be ordered from SVTronics. It's supported in > > > mainline just fine: > > > > > > https://www.svtronics.com/index.php?route=product/product&product_id=33 > > > > Very nice, thanks for the link. This is one of those "BIG.little" > > processors as well, right? That might be good to get for that reason > > alone. > > correct. > > > > final patches are heading to v3.12 merge window, after that USB should > > > work out of the box. > > > > So you have no objection for this patch waiting for 3.12? > > not really, as of today we need out of tree patches to get that board > booting anyway :-( Ok, I'll queue this patch for usb-next and 3.12 as well. Sarah Sharp -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
