Lines Matching full:hub

85 	this structure, even the root hub. The controller itself does not
117 root hub attached to it. This hub, which is itself a USB device, can provide
119 possible to power up a hub and find out which of its ports have devices
122 Devices are given addresses starting at 1. The root hub is always address 1,
126 USB devices are enumerated by finding a device on a particular hub, and
140 newer (XHCI). If you connect a super-speed device to a high-speed hub, you
173 are attached to a parent hub (or controller in the case of the root hub) and
200 (only) device that is attached to the controller - a root hub
244 Note that the first device is always a root hub, and this must be scanned to
245 find any devices. The above steps will have created a hub (UCLASS_USB_HUB),
248 For hubs, the hub uclass has a post_probe() method. This means that after
249 any hub is probed, the uclass gets to do some processing. In this case
252 - usb_hub_post_probe() calls usb_hub_scan() to scan the hub, which in turn
254 - hub power is enabled
255 - we loop through each port on the hub, performing the same steps for each
260 device ready for use. If it is a hub, it will scan that hub before it
262 - once all hub ports are scanned in this way, the hub is ready for use and
269 - most logic is in the USB controller and hub uclasses; the actual device
272 - hub scanning happens automatically after a hub is probed
341 for a hub and a flash stick. These are enough to create a pretend USB bus
352 		hub {
353 			compatible = "usb-hub";
355 			hub-emul {
356 				compatible = "sandbox,usb-hub";
368 This defines a single controller, containing a root hub (which is required).
369 The hub is emulated by a hub emulator, and the emulated hub has a single
375  usb_hub     [ + ]        `-- hub
376  usb_emul    [ + ]            |-- hub-emul
392 embedded system. In fact anything other than a root hub is uncommon. Still
398 root hub at first, then only progress to the next 'level' when a device is