usb_reset_configuration(9) [centos man page]

USB_RESET_CONFIGURAT(9) 					   USB Core APIs					   USB_RESET_CONFIGURAT(9)

NAME

       usb_reset_configuration - lightweight device reset

SYNOPSIS

       int usb_reset_configuration(struct usb_device * dev);

ARGUMENTS

       dev
	   the device whose configuration is being reset

DESCRIPTION

       This issues a standard SET_CONFIGURATION request to the device using the current configuration. The effect is to reset most USB-related
       state in the device, including interface altsettings (reset to zero), endpoint halts (cleared), and endpoint state (only for bulk and
       interrupt endpoints). Other usbcore state is unchanged, including bindings of usb device drivers to interfaces.

       Because this affects multiple interfaces, avoid using this with composite (multi-interface) devices. Instead, the driver for each interface
       may use usb_set_interface on the interfaces it claims. Be careful though; some devices don't support the SET_INTERFACE request, and others
       won't reset all the interface state (notably endpoint state). Resetting the whole configuration would affect other drivers' interfaces.

       The caller must own the device lock.

RETURN

       Zero on success, else a negative error code.

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014						   USB_RESET_CONFIGURAT(9)

USB_QUEUE_RESET_DEVI(9) 					   USB Core APIs					   USB_QUEUE_RESET_DEVI(9)

NAME

       usb_queue_reset_device - Reset a USB device from an atomic context

SYNOPSIS

       void usb_queue_reset_device(struct usb_interface * iface);

ARGUMENTS

       iface
	   USB interface belonging to the device to reset

DESCRIPTION

       This function can be used to reset a USB device from an atomic context, where usb_reset_device won't work (as it blocks).

       Doing a reset via this method is functionally equivalent to calling usb_reset_device, except for the fact that it is delayed to a
       workqueue. This means that any drivers bound to other interfaces might be unbound, as well as users from usbfs in user space.

CORNER CASES

       - Scheduling two resets at the same time from two different drivers attached to two different interfaces of the same device is possible;
       depending on how the driver attached to each interface handles ->pre_reset, the second reset might happen or not.

       - If a driver is unbound and it had a pending reset, the reset will be cancelled.

       - This function can be called during .probe or .disconnect times. On return from .disconnect, any pending resets will be cancelled.

       There is no no need to lock/unlock the reset_ws as schedule_work does its own.

NOTE

       We don't do any reference count tracking because it is not needed. The lifecycle of the work_struct is tied to the usb_interface. Before
       destroying the interface we cancel the work_struct, so the fact that work_struct is queued and or running means the interface (and thus,
       the device) exist and are referenced.

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014						   USB_QUEUE_RESET_DEVI(9)