.\" This manpage has been automatically generated by docbook2man 
.\" from a DocBook document.  This tool can be found at:
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
.\" Please send any bug reports, improvements, comments, patches, 
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "USB_GET_STATUS" "9" "09 October 2005" "" ""

.SH NAME
usb_get_status \- issues a GET_STATUS call
.SH SYNOPSIS
"SYNOPSIS"
.sp
\fB
.sp
int usb_get_status  (struct usb_device * \fIdev\fB, int \fItype\fB, int \fItarget\fB, void * \fIdata\fB);
\fR
.SH "ARGUMENTS"
.TP
\fB\fIdev\fB\fR
the device whose status is being checked
.TP
\fB\fItype\fB\fR
USB_RECIP_*; for device, interface, or endpoint
.TP
\fB\fItarget\fB\fR
zero (for device), else interface or endpoint number
.TP
\fB\fIdata\fB\fR
pointer to two bytes of bitmap data
.SH "CONTEXT"
.PP
!in_interrupt ()
.SH "DESCRIPTION"
.PP
Returns device, interface, or endpoint status.  Normally only of
interest to see if the device is self powered, or has enabled the
remote wakeup facility; or whether a bulk or interrupt endpoint
is halted (``stalled'').
.PP
Bits in these status bitmaps are set using the SET_FEATURE request,
and cleared using the CLEAR_FEATURE request.  The \fBusb_clear_halt\fR
function should be used to clear halt (``stall'') status.
.PP
This call is synchronous, and may not be used in an interrupt context.
.PP
Returns the number of bytes received on success, or else the status code
returned by the underlying \fBusb_control_msg\fR call.