Searched full:bulk (Results 1 – 25 of 65) sorted by relevance
123
| /Documentation/w1/masters/ |
| D | ds2490.rst | 49 - The ds2490 specification doesn't cover short bulk in reads in
51 available, the bulk read will return an error and the hardware will
52 clear the entire bulk in buffer. It would be possible to read the
63 most of the time one of the bulk out or in, and usually the bulk in
64 would fail. qemu sets a 50ms timeout and the bulk in would timeout
65 even when the status shows data available. A bulk out write would
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-w1_therm | 75 * If a bulk read has been triggered, it will directly
76 return the temperature computed when the bulk read
80 * If no bulk read has been triggered, it will trigger
115 (RW) trigger a bulk read conversion. read the status
124 no bulk operation. Reading temperature will
128 'trigger': trigger a bulk read on all supporting
131 Note that if a bulk read is sent but one sensor is not read
134 of the bulk read command (not the current temperature).
|
| D | sysfs-class-firmware-attributes | 395 to allow a user to bulk set the attributes, and then trigger a final save. This allows
398 Read the attribute to check what save mode is enabled (single or bulk).
403 Write the attribute with 'bulk' to enable bulk save mode.
407 # echo bulk > /sys/class/firmware-attributes/thinklmi/attributes/save_settings
409 When in bulk mode write 'save' to trigger a save of all currently modified attributes.
410 Note, once a save has been triggered, in bulk mode, attributes can no longer be set and
|
| D | configfs-usb-gadget-sourcesink | 14 bulk_qlen depth of queue for bulk
|
| D | configfs-usb-gadget-mass-storage | 8 stall Set to permit function to halt bulk endpoints.
|
| /Documentation/driver-api/usb/ |
| D | bulk-streams.rst | 1 USB bulk streams
7 Bulk endpoint streams were added in the USB 3.0 specification. Streams allow a
8 device driver to overload a bulk endpoint so that multiple transfers can be
41 ID for the bulk IN and OUT endpoints used in a Bi-directional command sequence.
46 declares how many stream IDs it can support, and each bulk endpoint on a
|
| D | index.rst | 10 bulk-streams
|
| D | writing_usb_driver.rst | 154 bulk-in and bulk-out. We create buffers to hold the data that will be
185 created (this size depends on the size of the bulk out end point that
205 /* send the data out the bulk port */
233 /* do an immediate bulk read to get data from the device */
298 sent almost exactly as bulk data is, with a few minor exceptions.
|
| D | usb.rst | 49 - USB supports four kinds of data transfers (control, bulk, interrupt,
50 and isochronous). Two of them (control and bulk) use bandwidth as
75 type and direction of data transfer such as "bulk out" or "interrupt
81 flagging the end of bulk transfers using "short" (including zero
84 - The Linux USB API supports synchronous calls for control and bulk
151 wrappers for single-buffer control and bulk transfers (which are awkward
153 streaming i/o (bulk or interrupt).
308 control, bulk, or other kinds of USB transfers. The IOCTLs are
345 interface. *Bulk* transfers are easiest to use, but only their sibling
492 Resets the data toggle value for an endpoint (bulk or interrupt) to
[all …]
|
| D | URB.rst | 72 // (OUT) sometimes only part of CTRL/BULK/INTR transfer_buffer is used
101 you want to schedule. For CTRL/BULK/INT, use 0. The mem_flags parameter
242 Besides the fields present on a bulk transfer, for ISO, you also
|
| /Documentation/usb/ |
| D | ehci.rst | 58 At this writing the driver should comfortably handle all control, bulk,
125 and bulk transfers. Shows each active qh and the qtds
160 Bulk transfers are most often used where throughput is an issue. It's
161 good to keep in mind that bulk transfers are always in 512 byte packets,
165 So more than 50 MByte/sec is available for bulk transfers, when both
195 you issue a control or bulk request you can often expect to learn that
203 or using bulk queuing if a series of small requests needs to be issued.
213 I/O be efficient, it's better to just queue up several (bulk) requests
|
| D | gadget_serial.rst | 89 with bulk in and bulk out endpoints, and it is treated similarly
93 or any driver that can talk to a device with a simple bulk in/out
122 To load it as a vendor specific bulk in/out device, do this::
150 serial is loaded as a bulk in/out device, you will want to use the
209 E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
210 E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
239 E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
240 E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
|
| D | mass-storage.rst | 15 Its requirements are modest; only a bulk-in and a bulk-out endpoint
21 a single memory/DMA buffer will be usable for bulk-in and bulk-out
140 Specifies whether the gadget is allowed to halt bulk endpoints.
242 supported. MSG always uses SCSI protocol with bulk only
|
| D | acm.rst | 91 E: Ad=85(I) Atr=02(Bulk) MxPS= 64 Ivl= 0ms
92 E: Ad=04(O) Atr=02(Bulk) MxPS= 64 Ivl= 0ms
98 E: Ad=85(I) Atr=02(Bulk) MxPS= 64 Ivl= 0ms
99 E: Ad=04(O) Atr=02(Bulk) MxPS= 64 Ivl= 0ms
|
| D | usbmon.rst | 145 Bi Bo Bulk input and output
205 An output bulk transfer to send a SCSI command 0x28 (READ_10) in a 31-byte
206 Bulk wrapper to a storage device at address 5::
221 unsigned char xfer_type; /* ISO (0), Intr, Control, Bulk (3) */
|
| D | raw-gadget.rst | 88 enabling endpoints; allow providing ``stream_id`` for bulk transfers).
|
| /Documentation/w1/slaves/ |
| D | w1_therm.rst | 42 A bulk read of all devices on the bus could be done writing ``trigger``
48 ``therm_bulk_read`` will return 0 if no bulk conversion pending,
52 may return empty if conversion is still in progress. Note that if a bulk
55 time of issue of the bulk read command (not the current temperature).
|
| /Documentation/fb/ |
| D | udlfb.rst | 15 pixels line-by-line via USB bulk transfers.
17 Because of the efficiency of bulk transfers and a protocol on top that
22 Mode setting, EDID read, etc are other bulk or control transfers. Mode
46 Writes need to be detected and encoded into USB bulk transfers by the CPU.
|
| /Documentation/driver-api/soundwire/ |
| D | error_handling.rst | 8 mechanism (sync loss after two errors) and short CRCs used for the Bulk
|
| D | summary.rst | 28 transport. Data Port0 is dedicated to transport of Bulk control information,
190 (1) Bulk Register Access (BRA) transfers.
|
| /Documentation/devicetree/bindings/usb/ |
| D | snps,dwc3.yaml | 331 Maximum Bulk IN burst the DWC_usb3 core can perform. When the system
334 size that the core can perform. It only applies to SS Bulk,
362 In Host mode, it only applies to SS Bulk, Isochronous, and Interrupt
|
| /Documentation/networking/device_drivers/ethernet/intel/ |
| D | e1000e.rst | 77 "Bulk traffic", for large amounts of packets of normal size; "Low latency",
84 However, this is generally not suitable for bulk throughput traffic due
93 4000 for traffic that falls in class "Bulk traffic". If traffic falls in
|
| D | e1000.rst | 124 "Bulk traffic", for large amounts of packets of normal size; "Low latency",
130 for traffic that falls in class "Bulk traffic". If traffic falls in the "Low
148 for bulk throughput traffic.
|
| /Documentation/driver-api/media/drivers/ |
| D | dvb-usb.rst | 24 (bulk and isoc are supported)
31 functions for bulk-control-commands)
|
| /Documentation/accel/qaic/ |
| D | aic100.rst | 319 * Bit(3) indicates if this request is a linked list transfer(0) or a bulk
326 source address for a bulk transfer, or the address of the linked list.
329 destination address for a bulk transfer.
332 length of the bulk transfer. Note that the size of this field
|
123