Query: usb_driver_claim_interface
OS: centos
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)NAMEusb_driver_claim_interface - bind a driver to an interfaceSYNOPSISint usb_driver_claim_interface(struct usb_driver * driver, struct usb_interface * iface, void * priv);ARGUMENTSdriver 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 interfaceDESCRIPTIONThis 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.RETURN0 on success.COPYRIGHTKernel Hackers Manual 3.10 June 2014 USB_DRIVER_CLAIM_INT(9)
Related Man Pages |
---|
usb_match_id(9) - suse |
struct_spi_driver(9) - centos |
struct_usb_driver(9) - centos |
usb_match_id(9) - centos |
usb_queue_reset_device(9) - centos |
Similar Topics in the Unix Linux Community |
---|
Is UNIX an open source OS ? |
Weird 'find' results |
How to increment version inside a file? |
DB2 convert digits to binary format |
Controlling user input |