usb_ep_set_halt(9) [centos man page]

USB_EP_SET_HALT(9)					      Kernel Mode Gadget API						USB_EP_SET_HALT(9)

NAME

       usb_ep_set_halt - sets the endpoint halt feature.

SYNOPSIS

       int usb_ep_set_halt(struct usb_ep * ep);

ARGUMENTS

       ep
	   the non-isochronous endpoint being stalled

DESCRIPTION

       Use this to stall an endpoint, perhaps as an error report. Except for control endpoints, the endpoint stays halted (will not stream any
       data) until the host clears this feature; drivers may need to empty the endpoint's request queue first, to make sure no inappropriate
       transfers happen.

       Note that while an endpoint CLEAR_FEATURE will be invisible to the gadget driver, a SET_INTERFACE will not be. To reset endpoints for the
       current altsetting, see usb_ep_clear_halt. When switching altsettings, it's simplest to use usb_ep_enable or usb_ep_disable for the
       endpoints.

       Returns zero, or a negative error code. On success, this call sets underlying hardware state that blocks data transfers. Attempts to halt
       IN endpoints will fail (returning -EAGAIN) if any transfer requests are still queued, or if the controller hardware (usually a FIFO) still
       holds bytes that the host hasn't collected.

AUTHOR

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

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014							USB_EP_SET_HALT(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)