Lines Matching +full:send +full:- +full:flush +full:- +full:out +full:- +full:sequence
15 The usbmon reports requests made by peripheral-specific drivers to Host
35 ----------
41 # mount -t debugfs none_debugs /sys/kernel/debug
56 ------------------------------------------------
58 Run "cat /sys/kernel/debug/usb/devices", and find the T-line which corresponds
61 /sys/kernel/debug/usb/devices outputs. The T-line will have a bus number.
77 --------------
81 # cat /sys/kernel/debug/usb/usbmon/3u > /tmp/1.mon.out
85 # cat /sys/kernel/debug/usb/usbmon/0u > /tmp/1.mon.out
92 -----------------------------------------------
98 -----------
100 Usually it's done with a keyboard interrupt (Control-C).
102 At this point the output file (/tmp/1.mon.out in this example) can be saved,
103 sent by e-mail, or inspected with a text editor. In the last case make sure
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
130 - Timestamp in microseconds, a decimal number. The timestamp's resolution
134 - Event Type. This type refers to the format of the event, not URB type.
135 Available types are: S - submission, C - callback, E - submission error.
137 - "Address" word (formerly a "pipe"). It consists of four fields, separated by
151 - URB Status word. This is either a letter, or several numbers separated
170 - Setup packet, if present, consists of 5 words: one of each for bmRequestType,
175 - Number of isochronous frame descriptors and descriptors themselves.
178 total of 5. The word consists of 3 colon-separated decimal numbers for
182 - Data Length. For submissions, this is the requested length. For callbacks,
185 - Data tag. The usbmon may not always capture data, even if length is nonzero.
188 - Data words follow, in big endian hexadecimal format. Notice that they are
205 An output bulk transfer to send a SCSI command 0x28 (READ_10) in a 31-byte
208 …dd65f0e8 4128379752 S Bo:1:005:2 -115 31 = 55534243 ad000000 00800000 80010a28 20000000 20000040 0…
219 u64 id; /* 0: URB ID - from submission to callback */
233 unsigned char setup[SETUP_LEN]; /* Only for Control S-type */
284 size is out of [unspecified] bounds for this kernel, the call fails with
285 -EINVAL.
317 uint32_t nfetch; /* Number of events to fetch (out: fetched) */
318 uint32_t nflush; /* Number of events to flush */
326 Second, it waits for an event to be present in the buffer, unless the pseudo-
347 * Memory-mapped access of the kernel buffer for the binary API
352 Then, execute a loop similar to the one written in pseudo-code below::
358 fetch.offvec = vec; // Has N 32-bit words
362 nflush = fetch.nfetch; // This many packets to flush when done
365 if (hdr->type == '@') // Filler packet
375 the end of the buffer, so the above pseudo-code does not need any gathering.