Re: Trouble with a USB 2.0 device with xhci_hcd

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 23 Jan 2013, Sarah Sharp wrote:

> > So I guess my next question is: What are you plans, if any, to add the
> > "new" enumeration scheme to xHCI? Is this a huge amount of work?
> 
> Not a huge amount of work, but it does require an API change to the USB
> host controller driver functions, so the patch itself is not likely to
> get backported to stable kernels.  And I have no idea how the current
> batch of USB 3.0 devices will react to an enumeration sequence change.

I thought this wasn't possible at all, because the xHCI hardware 
automatically assigns an address to the device when a reset completes.

"Old" scheme:

	Reset
	Get device descriptor (8 bytes)
	Set address
	Get device descriptor (18 bytes)

"New" scheme:

	Reset
	Get device descriptor (64 bytes)
	Reset
	Set address
	Get device descriptor (18 bytes)

Given the way the hardware behaves, it's not really possible to do 
either of these.

Alan Stern

--
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


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux