Lines Matching +full:in +full:- +full:and +full:- +full:around
1 .. _usb-error-codes:
6 :Revised: 2004-Oct-21
8 This is the documentation of (hopefully) all possible error codes (and
13 behave the same except for transfer speed dependent behaviors and the
20 Non-USB-specific:
26 ``-ENOMEM`` no memory for allocation of internal structures
29 USB-specific:
32 ``-EBUSY`` The URB is already active.
34 ``-ENODEV`` specified USB-device or bus doesn't exist
36 ``-ENOENT`` specified interface or endpoint does not exist or
39 ``-ENXIO`` host controller driver does not support queuing of
42 ``-EINVAL`` a) Invalid transfer type specified (or not supported)
48 ``-EXDEV`` ISO: ``URB_ISO_ASAP`` wasn't specified and all the
49 frames the URB would be scheduled in have already
52 ``-EFBIG`` Host controller driver can't schedule that many ISO
55 ``-EPIPE`` The pipe type specified in the URB doesn't match the
58 ``-EMSGSIZE`` (a) endpoint maxpacket size is zero; it is not usable
59 in the current interface altsetting.
64 ``-EBADR`` The wLength value in a control URB's setup packet does
67 ``-ENOSPC`` This request would overcommit the usb bandwidth reserved
70 ``-ESHUTDOWN`` The device or host controller has been disabled due to
71 some problem that could not be worked around.
73 ``-EPERM`` Submission failed because ``urb->reject`` was set.
75 ``-EHOSTUNREACH`` URB was rejected because the device is suspended.
77 ``-ENOEXEC`` A control URB doesn't contain a Setup packet.
80 Error codes returned by ``in urb->status`` or in ``iso_frame_desc[n].status`` (for ISO)
83 USB device drivers may only test urb status values in completion handlers.
85 these values on one CPU, and device drivers testing them on another CPU.
91 For isochronous URBs, the urb status value is non-zero only if the URB is
93 transferred length is less than the requested length and the
95 should only see ``urb->status`` set to zero, ``-ENOENT``, ``-ECONNRESET``,
96 ``-ESHUTDOWN``, or ``-EREMOTEIO``. Individual frame descriptor status fields
103 ``-ENOENT`` URB was synchronously unlinked by
106 ``-EINPROGRESS`` URB still pending, no results yet
109 ``-EPROTO`` [#f1]_, [#f2]_ a) bitstuff error
111 prescribed bus turn-around time
114 ``-EILSEQ`` [#f1]_, [#f2]_ a) CRC mismatch
116 prescribed bus turn-around time
120 not distinguish among cases a), b), and c), so
126 ``-ETIME`` [#f2]_ No response packet received within the
127 prescribed bus turn-around time. This error
129 ``-EPROTO`` or ``-EILSEQ``.
131 ``-ETIMEDOUT`` Synchronous USB message functions use this code
133 completed, and no other error was reported
136 ``-EPIPE`` [#f2]_ Endpoint stalled. For non-control endpoints,
140 ``-ECOMM`` During an IN transfer, the host controller
144 ``-ENOSR`` During an OUT transfer, the host controller
148 ``-EOVERFLOW`` [#f1]_ The amount of data returned by the endpoint was
153 ``-EREMOTEIO`` The data read from the endpoint did not fill
154 the specified buffer, and ``URB_SHORT_NOT_OK``
155 was set in ``urb->transfer_flags``.
157 ``-ENODEV`` Device was removed. Often preceded by a burst
161 ``-EXDEV`` ISO transfer only partially completed
162 (only set in ``iso_frame_desc[n].status``,
163 not ``urb->status``)
165 ``-EINVAL`` ISO madness, if this happens: Log off and
168 ``-ECONNRESET`` URB was asynchronously unlinked by
171 ``-ESHUTDOWN`` The device or host controller has been
173 be worked around, such as a physical
180 Error codes like ``-EPROTO``, ``-EILSEQ`` and ``-EOVERFLOW`` normally
188 disconnect. In the interval before the hub driver starts disconnect
193 Error codes returned by usbcore-functions
196 .. note:: expect also other submit and transfer status codes
201 ``-EINVAL`` error during registering new driver
209 ``-ETIMEDOUT`` Timeout expired before the transfer completed.