struct_usb_host_endpoint(9) [suse man page]

STRUCT 
USB_HOST_ENDP(9) 				  Host-Side Data Types and Macro				   STRUCT USB_HOST_ENDP(9)

NAME

       struct_usb_host_endpoint - host-side endpoint descriptor and queue

SYNOPSIS

       struct usb_host_endpoint {
	 struct usb_endpoint_descriptor desc;
	 struct list_head urb_list;
	 void * hcpriv;
	 struct ep_device * ep_dev;
	 struct usb_host_ss_ep_comp * ss_ep_comp;
	 unsigned char * extra;
	 int extralen;
	 int enabled;
       };

MEMBERS

       desc
	   descriptor for this endpoint, wMaxPacketSize in native byteorder

       urb_list
	   urbs queued to this endpoint; maintained by usbcore

       hcpriv
	   for use by HCD; typically holds hardware dma queue head (QH) with one or more transfer descriptors (TDs) per urb

       ep_dev
	   ep_device for sysfs info

       ss_ep_comp
	   companion descriptor information for this endpoint

       extra
	   descriptors following this endpoint in the configuration

       extralen
	   how many bytes of "extra" are valid

       enabled
	   URBs may be submitted to this endpoint

DESCRIPTION

       USB requests are always queued to a given endpoint, identified by a descriptor within an active interface in a given USB configuration.

COPYRIGHT

Kernel Hackers Manual 2.6.					     July 2010						   STRUCT USB_HOST_ENDP(9)

USB_EP_ENABLE(9)					      Kernel Mode Gadget API						  USB_EP_ENABLE(9)

NAME

       usb_ep_enable - configure endpoint, making it usable

SYNOPSIS

       int usb_ep_enable(struct usb_ep * ep, const struct usb_endpoint_descriptor * desc);

ARGUMENTS

       ep
	   the endpoint being configured. may not be the endpoint named "ep0". drivers discover endpoints through the ep_list of a usb_gadget.

       desc
	   descriptor for desired behavior. caller guarantees this pointer remains valid until the endpoint is disabled; the data byte order is
	   little-endian (usb-standard).

DESCRIPTION

       when configurations are set, or when interface settings change, the driver will enable or disable the relevant endpoints. while it is
       enabled, an endpoint may be used for i/o until the driver receives a disconnect from the host or until the endpoint is disabled.

       the ep0 implementation (which calls this routine) must ensure that the hardware capabilities of each endpoint match the descriptor provided
       for it. for example, an endpoint named "ep2in-bulk" would be usable for interrupt transfers as well as bulk, but it likely couldn't be used
       for iso transfers or for endpoint 14. some endpoints are fully configurable, with more generic names like "ep-a". (remember that for USB,
       "in" means "towards the USB master".)

       returns zero, or a negative error code.

AUTHOR

       David Brownell <dbrownell@users.sourceforge.net>
	   Author.

COPYRIGHT

Kernel Hackers Manual 2.6.					     July 2010							  USB_EP_ENABLE(9)