URB (reference) in projects: Linux-v5.4

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

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

/Linux-v5.4/Documentation/usb/
D	usbip_protocol.rst	36 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 258 Submit an URB 263 \| 0 \| 4 \| 0x00000001 \| command: Submit an URB \| 265 \| 4 \| 4 \| \| seqnum: the sequence number of the URB to submit \| 277 \| \| \| \| URB transfer type, see below \| 293 \| 0x30 \| \| \| URB data. For ISO transfers the padding between \| 318 Reply for submitting an URB 325 \| 4 \| 4 \| \| seqnum: URB sequence number \| [all …]
D	usbmon.rst	119 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 …]
D	ehci.rst	`215 Such URB queuing should work with all the USB 1.1 HC drivers too.`
/Linux-v5.4/Documentation/driver-api/usb/
D	URB.rst	3 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 …]
D	error-codes.rst	24 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
D	anchors.rst	`33 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.`
D	index.rst	`13 URB`
D	bulk-streams.rst	`65 To queue an URB for a specific stream, set the urb->stream_id value. If the`
D	usb.rst	`101 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`
D	power-management.rst	`398 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`
D	gadget.rst	`55 host side's current URB framework exposes a number of implementation`
/Linux-v5.4/drivers/media/usb/dvb-usb/
D	cxusb-analog.c	468 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-v5.4/drivers/staging/wusbcore/Documentation/
D	wusb-design-overview.rst	`389 we issue another URB to read into the destination buffer the chunk of 400 The main xfer descriptor, wa_xfer (equivalent to a URB) contains an 405 For OUT xfers, there is an array of segments, one URB for each, another 406 one of buffer URB. When submitting, we submit URBs for segment request 414 URB mapping into xfers 425 called--this will call the URB callback.`
/Linux-v5.4/arch/powerpc/xmon/
D	ppc-opc.c	877 #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-v5.4/Documentation/media/dvb-drivers/
D	dvb-usb.rst	`23 - Transport Stream URB handling in conjunction with dvb-demux-feed-control`
/Linux-v5.4/drivers/usb/host/
D	Kconfig	`676 devices that just queue one ISO frame per URB, then ISO transfers`
/Linux-v5.4/Documentation/sound/
D	alsa-configuration.rst	`2216 Max. number of packets per URB (default: 8) 2244 the mixer element such as URB error -22. This happens on some`
/Linux-v5.4/Documentation/admin-guide/
D	kernel-parameters.txt	`4985 [USB] Maximum number of bytes to snoop in each URB`