2 .\" Copyright (c) 2004, Sun Microsystems, Inc., All Rights Reserved
3 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
4 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
5 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
6 .TH USB_COMPLETION_REASON 9S "Jan 5, 2004"
8 usb_completion_reason \- USB completion reason definitions
12 #include <sys/usb/usba.h>
18 Solaris DDI specific (Solaris DDI)
22 If an error occurs during execution of a USB request, the USBA framework calls
23 a client driver's exception callback handler to relay what happened. The host
24 controller reports transport errors to the exception callback handler through
25 the handler's request argument's completion reason (usb_cr_t) field. A
26 completion reason of USB_CR_OK means the transfer completed with no errors
30 The usb_cr_t enumerated type contains the following definitions:
37 The transfer completed without any errors being detected.
46 CRC error was detected.
52 \fBUSB_CR_BITSTUFFING\fR
55 Bit stuffing violation was detected.
61 \fBUSB_CR_DATA_TOGGLE_MM\fR
64 Data toggle packet identifier did not match expected value.
73 The device endpoint indicated that it is stalled. If autoclearing is enabled
74 for the request (request attributes has USB_ATTRS_AUTOCLEARING set), check the
75 callback flags (usb_cb_flags_t) in the callback handler to determine whether
76 the stall is a functional stall (USB_CB_FUNCTIONAL_STALL) or a protocol stall
77 (USB_CB_PROTOCOL_STALL). Please see \fBusb_request_attributes\fR(9S) for more
78 information on autoclearing.
84 \fBUSB_CR_DEV_NOT_RESP\fR
87 Host controller timed out while waiting for device to respond.
93 \fBUSB_CR_PID_CHECKFAILURE\fR
96 Check bits on the packet identifier returned from the device were
103 \fBUSB_CR_UNEXP_PID\fR
106 Packet identifier received was not valid.
112 \fBUSB_CR_DATA_OVERRUN\fR
115 Amount of data returned exceeded either the maximum packet size of the endpoint
116 or the remaining buffer size.
122 \fBUSB_CR_DATA_UNDERRUN\fR
125 Amount of data returned was not sufficient to fill the specified buffer and the
126 USB_ATTRS_SHORT_XFER_OK attribute was not set. Please see
127 \fBusb_request_attributes\fR(9S) for more information on allowance of short
134 \fBUSB_CR_BUFFER_OVERRUN\fR
137 A device sent data faster than the system could digest it.
143 \fBUSB_CR_BUFFER_UNDERRUN\fR
146 The host controller could not get data from the system fast enough to keep up
147 with the required USB data rate.
156 A timeout specified in a control, bulk, or one-time interrupt request has
163 \fBUSB_CR_NOT_ACCESSED\fR
166 Request was not accessed nor processed by the host controller.
172 \fBUSB_CR_NO_RESOURCES\fR
175 No resources were available to continue servicing a periodic interrupt or
182 \fBUSB_CR_STOPPED_POLLING\fR
185 Servicing of the current periodic request cannot continue because polling on an
186 interrupt-IN or isochronous-IN endpoint has stopped.
192 \fBUSB_CR_PIPE_CLOSING\fR
195 Request was not started because the pipe to which it was queued was closing or
202 \fBUSB_CR_PIPE_RESET\fR
205 Request was not started because the pipe to which it was queued was reset.
211 \fBUSB_CR_NOT_SUPPORTED\fR
214 Request or command is not supported.
223 Request was not completed because the pipe to which it was queued went to an
224 error state, became stalled, was reset or was closed.
230 \fBUSB_CR_HC_HARDWARE_ERR\fR
233 Request could not be completed due to a general host controller
240 See attributes(5) for descriptions of the following attributes:
248 ATTRIBUTE TYPE ATTRIBUTE VALUE
250 Architecture PCI-based systems
252 Interface stability Committed
258 \fBusb_alloc_request\fR(9F), \fBusb_pipe_bulk_xfer\fR(9F),
259 \fBusb_pipe_ctrl_xfer\fR(9F), \fBusb_pipe_intr_xfer\fR(9F),
260 \fBusb_pipe_isoc_xfer\fR(9F), \fBusb_bulk_request\fR(9S),
261 \fBusb_ctrl_request\fR(9S), \fBusb_intr_request\fR(9S),
262 \fBusb_isoc_request\fR(9S)