1USB_DRIVER_CLAIM_INT(9)          USB Core APIs         USB_DRIVER_CLAIM_INT(9)
2
3
4

NAME

6       usb_driver_claim_interface - bind a driver to an interface
7

SYNOPSIS

9       int usb_driver_claim_interface(struct usb_driver * driver,
10                                      struct usb_interface * iface,
11                                      void * priv);
12

ARGUMENTS

14       driver
15           the driver to be bound
16
17       iface
18           the interface to which it will be bound; must be in the usb
19           device's active configuration
20
21       priv
22           driver data associated with that interface
23

DESCRIPTION

25       This is used by usb device drivers that need to claim more than one
26       interface on a device when probing (audio and acm are current
27       examples). No device driver should directly modify internal
28       usb_interface or usb_device structure members.
29
30       Few drivers should need to use this routine, since the most natural way
31       to bind to an interface is to return the private data from the driver's
32       probe method.
33
34       Callers must own the device lock, so driver probe entries don't need
35       extra locking, but other call contexts may need to explicitly claim
36       that lock.
37

RETURN

39       0 on success.
40

42Kernel Hackers Manual 3.10         June 2019           USB_DRIVER_CLAIM_INT(9)
Impressum