usb_driver_claim_interface man page on Scientific

usb_driver_claim_interface man page on Scientific

Man page or keyword search:
man Server 26626 pages
apropos Keyword Search (all sections)
Output format

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.	 November 2013	       USB_DRIVER_CLAIM_INT(9)

[top]

List of man pages available for Scientific

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]

Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................

Vote for polarhome