Lines Matching refs:speed

32   overheads used for both full and high speed host controller drivers. This
41 2.Full speed bus
43 The following overheads, formulas and scheme are applicable both to full speed
44 host controllers and also to high speed hub Transaction Translators (TT),
45 which perform full/low speed transactions.
59 1 full speed bit time 83.54 ns
71 Low-speed overhead 64060 ns 97 bytes
77 Low-Speed clock* Slower than Full speed 8
90 1.Hub specific low speed overhead
93 ports. The minimum of 4 full speed bit time.
135 3.The Low-Speed clock is eight times slower than full speed i.e. 1/8th of
136 the full speed.
138 4.For non-periodic transfers, reserve for at least one low-speed device
141 one low-speed transaction takes 0x628h full speed bits (197 bytes),
220 3.High speed bus
235 1 high speed bit time 2.083 ns
267 for the non-periodic high-speed transfers, where as periodic high-speed
314 This field is used for for high, full and low speed usb device interrupt
316 frame of a given usb frame to initiate a high speed interrupt and
317 isochronous transaction. For full/low speed devices, it will tell when to
322 * For all low/full speed devices, and for high speed devices with
334 /* For high speed devices with a polling interval of 4us. */
340 /* For high speed devices with a polling interval of 2us. */
344 /* For high speed devices with a polling interval of 1us. */
349 This field is used only for full/low speed usb device interrupt and
356 /* Only full/low speed devices */
372 - The high speed host controller can support 256, 512 or 1024 periodic frame
394 - For EHCI, the bandwidth requirement is depends on the usb device speed
397 For a high speed usb device, you only need high speed bandwidth. For a
398 full/low speed device connected through a high speed hub, you need both
399 high speed bandwidth and TT (transaction translator) bandwidth.
401 High speed bandwidth information is saved in an EHCI data structure and TT
402 bandwidth is saved in the high speed hub's usb device data structure. Each
403 TT acts as a full speed host controller & its bandwidth allocation scheme
405 speed host controller. Refer to the "Full speed bus" section for more
409 store high speed bandwidth allocated in each frame and also each frame
417 High speed Non Split Transaction (for High speed devices only):
419 For a given high speed interrupt or isochronous endpoint, the EHCI host
430 - Map a given high speed endpoint's polling interval in micro seconds to an
457 High speed split transactions (for full and low speed devices only):
459 For a given full/low speed interrupt or isochronous endpoint, we need both
460 high speed and TT bandwidths. The TT bandwidth allocation is same as full
461 speed bus bandwidth allocation. Please refer to the "full speed bus"
464 The EHCI driver will go through the following steps to allocate high speed
465 bandwidth needed for this full/low speed endpoint.