Lines Matching refs:of
4 used to collect traces of I/O on the USB bus. This function is analogous
98 of '1t' format.
104 Any text format data consists of a stream of events, such as URB submission,
106 of whitespace separated words. The number or position of words may depend
107 on the event type, but there is a set of words, common for all types.
109 Here is the list of words, from left to right:
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.
122 - "Address" word (formerly a "pipe"). It consists of four fields, separated by
130 have leading zeros, for the sake of human readers.
140 a "status" field of the URB. This field makes no sense for submissions, but
144 In case of a submission of a Control packet, this field contains a Setup Tag
145 instead of an group of numbers. It is easy to tell whether the Setup Tag is
146 present because it is never a number. Thus if scripts find a set of numbers
151 - Setup packet, if present, consists of 5 words: one of each for bmRequestType,
156 - Number of isochronous frame descriptors and descriptors themselves.
157 If an Isochronous transfer event has a set of descriptors, a total number
158 of them in an URB is printed first, then a word per descriptor, up to a
159 total of 5. The word consists of 3 colon-separated decimal numbers for
172 The length of collected data is limited and can be less than the data length
173 reported in the Data Length word. In the case of an Isochronous input (Zi)
174 completion where the received data is sparse in the buffer, the length of
194 The overall architecture of the API is about the same as the one above,
210 unsigned int length; /* 32: Length of data (submitted or actual) */
221 unsigned int xfer_flags; /* 56: copy of URB's transfer_flags */
222 unsigned int ndesc; /* 60: Actual number of ISO descriptors */
241 This call returns the length of data in the next event. Note that majority of
254 The member "queued" refers to the number of events currently queued in the
255 buffer (and not to the number of events processed since the last reset).
257 The member "dropped" is the number of events lost since the last call
264 size is out of [unspecified] bounds for this kernel, the call fails with
269 This call returns the current size of the buffer in bytes.
281 size_t alloc; /* Length of data (can be zero) */
296 uint32_t *offvec; /* Vector of events fetched */
297 uint32_t nfetch; /* Number of events to fetch (out: fetched) */
298 uint32_t nflush; /* Number of events to flush */
304 The actual number of events discarded is returned in nflush.
310 them into the offvec. The actual number of event offsets is stored into
315 This call removes a number of events from the kernel buffer. Its argument
316 is the number of events to remove. If the buffer contains fewer events
324 In addition to ioctl(2) and read(2), the special file of binary API can
327 * Memory-mapped access of the kernel buffer for the binary API
355 the end of the buffer, so the above pseudo-code does not need any gathering.