Home
last modified time | relevance | path

Searched refs:URB (Results 1 – 17 of 17) sorted by relevance

/Linux-v4.19/Documentation/usb/
Dusbip_protocol.txt30 to transfer the URB traffic between the client and the server. The client may
31 send two types of packets: the USBIP_CMD_SUBMIT to submit an URB, and
32 USBIP_CMD_UNLINK to unlink a previously submitted URB. The answers of the
236 USBIP_CMD_SUBMIT: Submit an URB
240 0 | 4 | 0x00000001 | command: Submit an URB
242 4 | 4 | | seqnum: the sequence number of the URB to submit
252 | | | URB transfer type, see below
268 0x30 | | | URB data. For ISO transfers the padding between
283 USBIP_RET_SUBMIT: Reply for submitting an URB
289 4 | 4 | | seqnum: URB sequence number
[all …]
Dusbmon.txt104 Any text format data consists of a stream of events, such as URB submission,
105 URB callback, submission error. Every event is a text line, which consists
111 - URB Tag. This is used to identify URBs, and is normally an in-kernel address
112 of the URB structure in hexadecimal, but can be a sequence number or any
119 - Event Type. This type refers to the format of the event, not URB type.
123 colons: URB type and direction, Bus number, Device address, Endpoint number.
132 - URB Status word. This is either a letter, or several numbers separated
133 by colons: URB status, interval, start frame, and error count. Unlike the
140 a "status" field of the URB. This field makes no sense for submissions, but
158 of them in an URB is printed first, then a word per descriptor, up to a
[all …]
DWUSB-Design-overview.txt372 we issue another URB to read into the destination buffer the chunk of
383 The main xfer descriptor, wa_xfer (equivalent to a URB) contains an
388 For OUT xfers, there is an array of segments, one URB for each, another
389 one of buffer URB. When submitting, we submit URBs for segment request
397 *URB mapping into xfers*
407 called--this will call the URB callback.
Dehci.txt201 Such URB queuing should work with all the USB 1.1 HC drivers too.
/Linux-v4.19/Documentation/driver-api/usb/
DURB.rst3 USB Request Block (URB)
20 Basic concept or 'What is an URB?'
24 called USB Request Block, or URB for short.
26 - An URB consists of all relevant information to execute any USB transaction
29 - Execution of an URB is inherently an asynchronous operation, i.e. the
33 - Transfers for one URB can be canceled with :c:func:`usb_unlink_urb`
36 - Each URB has a completion handler, which is called after the action
37 has been successfully completed or canceled. The URB also contains a
47 The URB structure
92 How to get an URB?
[all …]
Derror-codes.rst24 0 URB submission went fine
32 ``-EBUSY`` The URB is already active.
49 frames the URB would be scheduled in have already
55 ``-EPIPE`` The pipe type specified in the URB doesn't match the
72 ``-EHOSTUNREACH`` URB was rejected because the device is suspended.
74 ``-ENOEXEC`` A control URB doesn't contain a Setup packet.
88 For isochronous URBs, the urb status value is non-zero only if the URB is
100 ``-ENOENT`` URB was synchronously unlinked by
103 ``-EINPROGRESS`` URB still pending, no results yet
165 ``-ECONNRESET`` URB was asynchronously unlinked by
Danchors.rst33 an URB is finished by (successful) completion. Thus disassociation
80 Returns the oldest anchored URB of an anchor. The URB is unanchored
83 first submitted URB is returned.
Dindex.rst13 URB
Dbulk-streams.rst65 To queue an URB for a specific stream, set the urb->stream_id value. If the
Dusb.rst101 faults (including software-induced ones like unlinking an URB) isn't yet
137 asynchronous: drivers submit requests in the form of an URB, and the
138 URB's completion callback handles the next step. All USB transfer types
619 These requests are packaged into a structure that resembles the URB used
Dpower-management.rst394 such as an URB's completion handler, but when they return the
465 the I/O request routine and the URB completion handler; it should
Dgadget.rst55 host side's current URB framework exposes a number of implementation
/Linux-v4.19/arch/powerpc/xmon/
Dppc-opc.c889 #define URB URA + 1 macro
892 #define URC URB + 1
3535 {"udi0fcm.", APU(4, 515,0), APU_MASK, PPC405|PPC440, PPC476, {URT, URA, URB}},
3536 {"udi0fcm", APU(4, 515,1), APU_MASK, PPC405|PPC440, PPC476, {URT, URA, URB}},
3565 {"udi1fcm.", APU(4, 547,0), APU_MASK, PPC405|PPC440, PPC476, {URT, URA, URB}},
3566 {"udi1fcm", APU(4, 547,1), APU_MASK, PPC405|PPC440, PPC476, {URT, URA, URB}},
3605 {"udi2fcm.", APU(4, 579,0), APU_MASK, PPC405|PPC440, PPC476, {URT, URA, URB}},
3606 {"udi2fcm", APU(4, 579,1), APU_MASK, PPC405|PPC440, PPC476, {URT, URA, URB}},
3621 {"udi3fcm.", APU(4, 611,0), APU_MASK, PPC405|PPC440, PPC476, {URT, URA, URB}},
3623 {"udi3fcm", APU(4, 611,1), APU_MASK, PPC405|PPC440, PPC476, {URT, URA, URB}},
[all …]
/Linux-v4.19/Documentation/media/dvb-drivers/
Ddvb-usb.rst21 - Transport Stream URB handling in conjunction with dvb-demux-feed-control
/Linux-v4.19/drivers/usb/host/
DKconfig686 devices that just queue one ISO frame per URB, then ISO transfers
/Linux-v4.19/Documentation/sound/
Dalsa-configuration.rst2214 Max. number of packets per URB (default: 8)
2242 the mixer element such as URB error -22. This happens on some
/Linux-v4.19/Documentation/admin-guide/
Dkernel-parameters.txt4605 [USB] Maximum number of bytes to snoop in each URB