Lines Matching full:more

24 -  Flexible enough to expose more complex USB device capabilities such
32    API. This helps the OTG support, and looks forward to more-symmetric
42 embedded systems are more likely to have USB peripheral hardware. To
43 distinguish drivers running inside such hardware from the more familiar
141     -  ... and more
152 side stack, with ``usbcore``, one or more *Host Controller Drivers*
159 viewed as a more battery-friendly kind of device wakeup protocol.
170 hardware-specific, any more than network protocols like X11, HTTP, or
180 involves enabling one or more of the struct usb_ep objects exposed by
181 the gadget, and submitting one or more struct usb_request buffers to
224 of USB messages: I/O requests are in terms of one or more "packets", and
228 secondary stations) more than asynchronous ones (tty style: 8 data bits
270    ``usb_gadget_vbus_draw`` to let more power be drawn from VBUS, as
337 (with more than one function in a given configuration), and also
338 multi-configuration devices (also more than one function, but not
343 which in turn provides one or more struct usb_configuration
376 (``lh7a40x_udc``), and more. Most of those are full speed controllers.
416 on more slightly USB hardware (but less than the CDC subset). However,
428 can stream data with only slightly more overhead than a kernel driver.