suse man page for usb_driver_claim_interface

Query: usb_driver_claim_interface

OS: suse

Section: 9

Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar

USB_DRIVER_CLAIM_INT(9) 					   USB Core APIs					   USB_DRIVER_CLAIM_INT(9)

NAME
usb_driver_claim_interface - bind a driver to an interface
SYNOPSIS
int usb_driver_claim_interface(struct usb_driver * driver, struct usb_interface * iface, void * priv);
ARGUMENTS
driver the driver to be bound iface the interface to which it will be bound; must be in the usb device's active configuration priv driver data associated with that interface
DESCRIPTION
This is used by usb device drivers that need to claim more than one interface on a device when probing (audio and acm are current examples). No device driver should directly modify internal usb_interface or usb_device structure members. Few drivers should need to use this routine, since the most natural way to bind to an interface is to return the private data from the driver's probe method. Callers must own the device lock, so driver probe entries don't need extra locking, but other call contexts may need to explicitly claim that lock.
COPYRIGHT
Kernel Hackers Manual 2.6. July 2010 USB_DRIVER_CLAIM_INT(9)
Related Man Pages
usb_match_id(9) - suse
usb_mid(7d) - opensolaris
struct_usb_interface(9) - centos
usb_match_id(9) - centos
struct_spi_driver(9) - suse
Similar Topics in the Unix Linux Community
Change directory error
SOCKS proxy & PAM configuration exposure
Docker learning Phase-I
Shopt -s histappend
32 bit process addressing more than 4GB