'\" t
.\"     Title: usb_driver_claim_interface
.\"    Author: [FIXME: author] [see http://docbook.sf.net/el/author]
.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\"      Date: January 2017
.\"    Manual: USB Core APIs
.\"    Source: Kernel Hackers Manual 4.8.15
.\"  Language: English
.\"
.TH "USB_DRIVER_CLAIM_INT" "9" "January 2017" "Kernel Hackers Manual 4\&.8\&." "USB Core APIs"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.\" http://bugs.debian.org/507673
.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.ie \n(.g .ds Aq \(aq
.el       .ds Aq '
.\" -----------------------------------------------------------------
.\" * set default formatting
.\" -----------------------------------------------------------------
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.ad l
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
.SH "NAME"
usb_driver_claim_interface \- bind a driver to an interface
.SH "SYNOPSIS"
.HP \w'int\ usb_driver_claim_interface('u
.BI "int usb_driver_claim_interface(struct\ usb_driver\ *\ " "driver" ", struct\ usb_interface\ *\ " "iface" ", void\ *\ " "priv" ");"
.SH "ARGUMENTS"
.PP
\fIdriver\fR
.RS 4
the driver to be bound
.RE
.PP
\fIiface\fR
.RS 4
the interface to which it will be bound; must be in the usb device\*(Aqs active configuration
.RE
.PP
\fIpriv\fR
.RS 4
driver data associated with that interface
.RE
.SH "DESCRIPTION"
.PP
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\&.
.PP
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\*(Aqs
\fBprobe\fR
method\&.
.PP
Callers must own the device lock, so driver
\fBprobe\fR
entries don\*(Aqt need extra locking, but other call contexts may need to explicitly claim that lock\&.
.SH "RETURN"
.PP
0 on success\&.
.SH "COPYRIGHT"
.br