Home
last modified time | relevance | path

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

/linux-5.19.10/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
64 ``-EBADR`` The wLength value in a control URB's setup packet does
65 not match the URB's transfer_buffer_length.
75 ``-EHOSTUNREACH`` URB was rejected because the device is suspended.
77 ``-ENOEXEC`` A control URB doesn't contain a Setup packet.
91 For isochronous URBs, the urb status value is non-zero only if the URB is
103 ``-ENOENT`` URB was synchronously unlinked by
[all …]
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
143 asynchronous: drivers submit requests in the form of an URB, and the
144 URB's completion callback handles the next step. All USB transfer types
625 These requests are packaged into a structure that resembles the URB used
Dpower-management.rst398 such as an URB's completion handler, but when they return the
469 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-5.19.10/Documentation/usb/
Dusbip_protocol.rst36 to transfer the URB traffic between the client and the server. The client may
37 send two types of packets: the USBIP_CMD_SUBMIT to submit an URB, and
38 USBIP_CMD_UNLINK to unlink a previously submitted URB. The answers of the
88 For UNLINK, note that after a successful USBIP_RET_UNLINK, the unlinked URB
335 Submit an URB
343 | | | URB transfer_flags (refer to URB doc in |
344 | | | Documentation/driver-api/usb/URB.rst) |
349 | | | to function usbip_pack_cmd_submit and URB doc |
352 | | | use URB transfer_buffer_length |
354 | 0x1C | 4 | start_frame: use URB start_frame; |
[all …]
Dusbmon.rst119 Any text format data consists of a stream of events, such as URB submission,
120 URB callback, submission error. Every event is a text line, which consists
126 - URB Tag. This is used to identify URBs, and is normally an in-kernel address
127 of the URB structure in hexadecimal, but can be a sequence number or any
134 - Event Type. This type refers to the format of the event, not URB type.
138 colons: URB type and direction, Bus number, Device address, Endpoint number.
151 - URB Status word. This is either a letter, or several numbers separated
152 by colons: URB status, interval, start frame, and error count. Unlike the
159 a "status" field of the URB. This field makes no sense for submissions, but
177 of them in an URB is printed first, then a word per descriptor, up to a
[all …]
Dehci.rst215 Such URB queuing should work with all the USB 1.1 HC drivers too.
/linux-5.19.10/drivers/media/usb/dvb-usb/
Dcxusb-analog.c468 cxusb_vprintk(dvbdev, URB, "will copy field 1\n"); in cxusb_medion_v_process_auxbuf()
492 cxusb_vprintk(dvbdev, URB, "will copy field 2\n"); in cxusb_medion_v_process_auxbuf()
521 cxusb_vprintk(dvbdev, URB, "frame done\n"); in cxusb_medion_v_process_auxbuf()
523 cxusb_vprintk(dvbdev, URB, "frame skipped\n"); in cxusb_medion_v_process_auxbuf()
554 cxusb_vprintk(dvbdev, URB, "URB %u status = %d\n", urbn, urb->status); in cxusb_medion_v_complete_handle_urb()
563 cxusb_vprintk(dvbdev, URB, "URB %u data len = %lu\n", urbn, in cxusb_medion_v_complete_handle_urb()
567 cxusb_vprintk(dvbdev, URB, "appending URB\n"); in cxusb_medion_v_complete_handle_urb()
586 cxusb_vprintk(dvbdev, URB, "URB %u resubmit\n", urbn); in cxusb_medion_v_complete_handle_urb()
609 cxusb_vprintk(dvbdev, URB, "worker called, stop_streaming = %d\n", in cxusb_medion_v_complete_work()
622 cxusb_vprintk(dvbdev, URB, "rescheduling worker\n"); in cxusb_medion_v_complete_work()
[all …]
/linux-5.19.10/arch/powerpc/xmon/
Dppc-opc.c877 #define URB URA + 1 macro
880 #define URC URB + 1
3523 {"udi0fcm.", APU(4, 515,0), APU_MASK, PPC405|PPC440, PPC476, {URT, URA, URB}},
3524 {"udi0fcm", APU(4, 515,1), APU_MASK, PPC405|PPC440, PPC476, {URT, URA, URB}},
3553 {"udi1fcm.", APU(4, 547,0), APU_MASK, PPC405|PPC440, PPC476, {URT, URA, URB}},
3554 {"udi1fcm", APU(4, 547,1), APU_MASK, PPC405|PPC440, PPC476, {URT, URA, URB}},
3593 {"udi2fcm.", APU(4, 579,0), APU_MASK, PPC405|PPC440, PPC476, {URT, URA, URB}},
3594 {"udi2fcm", APU(4, 579,1), APU_MASK, PPC405|PPC440, PPC476, {URT, URA, URB}},
3609 {"udi3fcm.", APU(4, 611,0), APU_MASK, PPC405|PPC440, PPC476, {URT, URA, URB}},
3611 {"udi3fcm", APU(4, 611,1), APU_MASK, PPC405|PPC440, PPC476, {URT, URA, URB}},
[all …]
/linux-5.19.10/Documentation/driver-api/media/drivers/
Ddvb-usb.rst23 - Transport Stream URB handling in conjunction with dvb-demux-feed-control
/linux-5.19.10/drivers/usb/host/
DKconfig696 devices that just queue one ISO frame per URB, then ISO transfers
/linux-5.19.10/Documentation/sound/
Dalsa-configuration.rst2232 Max. number of packets per URB (default: 8)
2301 the mixer element such as URB error -22. This happens on some
/linux-5.19.10/Documentation/admin-guide/
Dkernel-parameters.txt6352 [USB] Maximum number of bytes to snoop in each URB