.\" This documentation was generated from the book titled "The Linux-USB Host Side API", which is part of the Linux kernel source. .\" .\" This documentation comes with the following legal notice: .\" .\" This documentation is free software; you can redistribute .\" it and/or modify it under the terms of the GNU General Public .\" License as published by the Free Software Foundation; either .\" version 2 of the License, or (at your option) any later .\" version. .\" .\" This program is distributed in the hope that it will be .\" useful, but WITHOUT ANY WARRANTY; without even the implied .\" warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. .\" See the GNU General Public License for more details. .\" .\" You should have received a copy of the GNU General Public .\" License along with this program; if not, write to the Free .\" Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, .\" MA 02111-1307 USA .\" .\" For more details see the file COPYING in the source .\" distribution of Linux. .\" .\" For comments on the formatting of this manpage, please contact Michael Still .\" This manpage has been automatically generated by docbook2man .\" from a DocBook document. This tool can be found at: .\" .\" Please send any bug reports, improvements, comments, patches, .\" etc. to Steve Cheng . .TH "USB_DRIVER_CLAIM_INTERFACE" "9" "13 April 2004" "" "" .SH NAME usb_driver_claim_interface \- bind a driver to an interface .SH SYNOPSIS .sp \fB .sp int usb_driver_claim_interface (struct usb_driver * \fIdriver\fB, struct usb_interface * \fIiface\fB, void* \fIpriv\fB); \fR .SH "ARGUMENTS" .TP \fB\fIdriver\fB\fR the driver to be bound .TP \fB\fIiface\fB\fR the interface to which it will be bound .TP \fB\fIpriv\fB\fR driver data associated with that interface .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's \fBprobe\fR method. .PP Callers must own the driver model's usb bus writelock. So driver \fBprobe\fR entries don't need extra locking, but other call contexts may need to explicitly claim that lock. .SH "ABOUT THIS DOCUMENT" .PP This documentation was generated with kernel version 2.6.1.