On Wed, Apr 29, 2009 at 06:10:06PM -0700, Sarah Sharp wrote: > This patch adds a hex route string to each USB device. The route string is used > by the USB 3.0 host controller to send packets through the device tree. USB 3.0 > hubs use this string to route packets to the correct port. This is fundamental > bus change from USB 2.0, where all packets were broadcast across the bus. > > Devices (including hubs) under a root port receive the route string 0x0. Every > four bits in the route string represent a port on a hub. This length works > because USB 3.0 hubs are limited to 15 ports, and USB 2.0 hubs (with potentially > more ports) will never see packets with a route string. A port number of 0 > means the packet is destined for that hub. > > For example, a peripheral device might have a route string of 0x00097. > This means the device is connected to port 9 of the hub at depth 1. > The hub at depth 1 is connected to port 7 of a hub at depth 0. > The hub at depth 0 is connected to a root port. > > Signed-off-by: Sarah Sharp <sarah.a.sharp@xxxxxxxxxxxxxxx> > --- > > Make route string a u32 instead of an int. > Greg, please replace usb-add-route-string-to-struct-usb_device.patch > with this one. Now replaced, thanks. greg k-h -- 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
