Lines Matching defs:driver
5 * driver, except for the hardware-specific bus glue. One USB host can
46 * @list: For use by the gadget driver.
51 * or when the driver disabled the endpoint.
61 * hardware's driver can add extra per-request data to the memory it returns,
139 * @driver_data:for use by the gadget driver. all other fields are
142 * the bus controller driver lists all the general purpose endpoints in
144 * and is accessed only in response to a driver setup() callback.
165 * when configurations are set, or when interface settings change, the driver
167 * endpoint may be used for i/o until the driver receives a disconnect() from
284 * @gfp_flags: GFP_* flags to use in case the lower level driver couldn't
290 * routine is called to return the request to the driver. Any endpoint
292 * request queued; they complete in FIFO order. Once a gadget driver
294 * is given back to that driver through the completion callback.
296 * Each request is turned into one or more packets. The controller driver
317 * Control endpoints ... after getting a setup() callback, the driver queues
327 * arranges to poll once per interval, and the gadget driver usually will
370 * gadget driver, a SET_INTERFACE will not be. To reset endpoints for the
411 * the IN data written by the gadget driver (and reported by a request
412 * completion). The gadget driver may not have collected all the data
465 * driver setup() requests
472 * Gadgets have a mostly-portable "gadget driver" implementing device
475 * That insulates the gadget driver from hardware details, and packages
479 * Except for the driver data, all fields in this structure are
480 * read-only to the gadget driver. That driver data is part of the
481 * "driver model" infrastructure in 2.5 (and later) kernels, and for
486 /* readonly to gadget driver */
552 * this affects the device status reported by the hardware driver
569 * this affects the device status reported by the hardware driver.
587 * struct usb_gadget_driver - driver for usb 'slave' devices
589 * @speed: Highest speed the driver handles.
590 * @bind: Invoked when the driver is bound to a gadget, usually
591 * after registering the driver.
596 * the hardware level driver. Most calls must be handled by
597 * the gadget driver, including descriptor and configuration
605 * @unbind: Invoked when the driver is unbound from a gadget,
611 * Devices are disabled till a gadget driver successfully bind()s, which
612 * means the driver will handle setup() requests needed to enumerate (and
619 * Except for ep0 implementation, most driver code shouldn't need change to
623 * The usb controller driver handles a few standard usb requests. Those
627 * Accordingly, the driver's setup() callback must always implement all
633 * The driver's setup() callback must also implement set_configuration,
664 } driver;
671 /* driver modules register and unregister, as usual.
675 * usb bus interface driver, which will only support a single driver.
679 * usb_gadget_register_driver - register a gadget driver
680 * @driver:the driver being registered
682 * Call this in your gadget driver's module initialization function,
683 * to tell the underlying usb controller driver about your driver.
684 * The driver's bind() function will be called to bind it to a
687 int usb_gadget_register_driver (struct usb_gadget_driver *driver);
690 * usb_gadget_unregister_driver - unregister a gadget driver
691 * @driver:the driver being unregistered
693 * Call this in your gadget driver's module cleanup function,
694 * to tell the underlying usb controller that your driver is
696 * it will first disconnect(). The driver is also requested
701 int usb_gadget_unregister_driver (struct usb_gadget_driver *driver);