Searched full:transmit (Results 1 – 25 of 213) sorted by relevance
123456789
| /Documentation/userspace-api/media/cec/ |
| D | cec-ioc-receive.rst | 14 CEC_RECEIVE, CEC_TRANSMIT - Receive or transmit a CEC message
52 2. the transmit result of an earlier non-blocking transmit (the ``sequence``
55 3. the reply to an earlier non-blocking transmit (the ``sequence`` field will
61 ``CEC_CAP_TRANSMIT`` is set. If there is no more room in the transmit
63 The transmit queue has enough room for 18 messages (about 1 second worth
66 idea to fully fill up the transmit queue.
68 If the file descriptor is in non-blocking mode then the transmit will
69 return 0 and the result of the transmit will be available via
70 :ref:`ioctl CEC_RECEIVE <CEC_RECEIVE>` once the transmit has finished.
71 If a non-blocking transmit also specified waiting for a reply, then
[all …]
|
| D | cec-pin-error-inj.rst | 55 # tx-custom-pulse transmit the custom pulse once the bus is idle
103 transmit or receive.
141 Clear all transmit error injections
150 Clear all transmit error injections for the given opcode.
183 to transmit mode and it will transmit a POLL message. By default this is
196 Transmit Messages
201 as soon as the receiver NACKs a byte the transmit will stop, but the
212 (End-Of-Message) bit set. With this command the transmit will just stop
227 have the value of the byte position in the message. So if you transmit a
329 Transmit a single custom pulse as soon as the CEC bus is idle.
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-net-queues | 24 Indicates the number of transmit timeout events seen by this
25 network interface transmit queue.
41 Transmit Packet Steering packet processing flow for this
42 network device transmit queue. Possible values depend on the
51 into the Transmit Packet Steering packet processing flow for this
52 network device transmit queue. Possible values depend on the
62 of this particular network device transmit queue.
71 network device transmit queue.
79 on this network device transmit queue. This value is clamped
88 queued on this network device transmit queue. See
[all …]
|
| /Documentation/networking/ |
| D | oa-tc6-framework.rst | 58 SPI data transactions consist of an equal number of transmit (TX) and
59 receive (RX) chunks. Chunks in both transmit and receive directions may
64 Each transmit data chunk begins with a 32-bit data header followed by a
65 data chunk payload on MOSI. The data header indicates whether transmit
160 the MAC-PHY will be converted into multiple transmit data chunks. Each
161 transmit data chunk will have a 4 bytes header which contains the
163 transmit frame data within the 64 bytes data chunk payload.
182 even/odd transmit data chunk sequence to the MAC-PHY.
198 whether the current chunk contains valid transmit frame data
205 transmit data chunk payload. Otherwise, this bit shall be
[all …]
|
| D | tc-queue-filters.rst | 8 to a single queue on both the transmit and receive side.
10 On the transmit side:
17 2) TC filter directs traffic to a transmit queue with the action
19 for transmit queue is executed in software only and cannot be
|
| D | scaling.rst | 21 - XPS: Transmit Packet Steering
27 Contemporary NICs support multiple receive and transmit descriptor queues
452 XPS: Transmit Packet Steering
455 Transmit Packet Steering is a mechanism for intelligently selecting
456 which transmit queue to use when transmitting a packet on a multi-queue
459 to hardware transmit queue(s).
464 exclusively to a subset of CPUs, where the transmit completions for
469 transmit queue). Secondly, cache miss rate on transmit completion is
475 This mapping is used to pick transmit queue based on the receive
477 queues can be mapped to a set of transmit queues (many:many), although
[all …]
|
| D | ppp_generic.rst | 38 responsible for splitting datagrams on transmit and recombining them
90 (e.g. an ioctl) to transmit this back to user-space, as user-space
152 that it buffers in the transmit direction. It maintains a queue of
153 transmit packets for the PPP unit (network interface device) plus a
154 queue of transmit packets for each attached channel. Normally the
155 transmit queue for the unit will contain at most one packet; the
159 called netif_stop_queue(), which only happens on a transmit timeout.
161 is asked to transmit.
163 Transmit packets are dequeued from the PPP unit transmit queue and
185 to transmit. The channel may still refuse a fragment; in this case
[all …]
|
| D | netdev-features.rst | 106 * Transmit checksumming
114 * Transmit TCP segmentation offload
119 * Transmit UDP segmentation offload
126 * Transmit DMA from high memory
131 * Transmit scatter-gather
|
| /Documentation/devicetree/bindings/ata/ |
| D | imx-sata.yaml | 44 fsl,transmit-level-mV:
46 description: transmit voltage level, in millivolts.
48 fsl,transmit-boost-mdB:
50 description: transmit boost level, in milli-decibels.
52 fsl,transmit-atten-16ths:
54 description: transmit attenuation, in 16ths.
|
| /Documentation/devicetree/bindings/phy/ |
| D | transmit-amplitude.yaml | 4 $id: http://devicetree.org/schemas/phy/transmit-amplitude.yaml#
7 title: Common PHY and network PCS transmit amplitude property
10 Binding describing the peak-to-peak transmit amplitude for common PHYs
19 Transmit amplitude voltages in microvolts, peak-to-peak. If this property
|
| D | fsl,imx8qm-lvds-phy.yaml | 16 transmit clock is transmitted in parallel with each group of
17 data streams over a fifth LVDS link. Every cycle of the transmit
20 transmit clocks, the two groups of LVDS data streams form two
|
| /Documentation/driver-api/media/ |
| D | cec-core.rst | 192 To transmit a new message::
198 attempts for the transmit.
202 depends on whether this transmit is a retry, a message from a new initiator or
210 To pass on the result of a canceled non-blocking transmit::
216 non-blocking transmit with sequence number msg->sequence. This is
217 called if the transmit was aborted, the transmit timed out (i.e. the
218 hardware never signaled that the transmit finished), or the transmit
241 When a transmit finished (successfully or otherwise)::
254 the transmit was successful.
273 result of a transmit, i.e. there is no way to differentiate
[all …]
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | cirrus,clps711x-intc.txt | 24 12: UTXINT1 UART1 transmit FIFO half empty
30 18: SS2TX SSI2 transmit FIFO less than half empty
31 28: UTXINT2 UART2 transmit FIFO half empty
|
| /Documentation/devicetree/bindings/sound/ |
| D | adi,axi-i2s.txt | 3 The core can be generated with transmit (playback), only receive
15 the core. The core expects two dma channels if both transmit and receive are
17 - dma-names : "tx" for the transmit channel, "rx" for the receive channel.
|
| D | cirrus,cs35l41.yaml | 72 0 = Logic 0 during unused slots, and while all transmit channels disabled
73 1 = Hi-Z during unused slots but logic 0 while all transmit channels disabled
74 2 = (Default) Logic 0 during unused slots, but Hi-Z while all transmit channels disabled
75 3 = Hi-Z during unused slots and while all transmit channels disabled
|
| /Documentation/networking/device_drivers/ethernet/altera/ |
| D | altera_tse.rst | 42 The SGDMA supports only a single transmit or receive operation at a time, and
80 4.1. Transmit process
82 When the driver's transmit routine is called by the kernel, it sets up a
83 transmit descriptor by calling the underlying DMA transmit routine (SGDMA or
84 MSGDMA), and initiates a transmit operation. Once the transmit is complete, an
85 interrupt is driven by the transmit DMA logic. The driver handles the transmit
87 resource required to send and track the requested transmit operation.
103 for transmit operations, but will be added in a future maintenance release.
|
| /Documentation/devicetree/bindings/net/ |
| D | motorcomm,yt8xxx.yaml | 97 Use original or inverted RGMII Transmit PHY Clock to drive the RGMII
98 Transmit PHY Clock delay train configuration when speed is 10Mbps.
103 Use original or inverted RGMII Transmit PHY Clock to drive the RGMII
104 Transmit PHY Clock delay train configuration when speed is 100Mbps.
109 Use original or inverted RGMII Transmit PHY Clock to drive the RGMII
110 Transmit PHY Clock delay train configuration when speed is 1000Mbps.
|
| D | marvell-orion-net.txt | 42 - marvell,tx-queue-size: size of the transmit ring buffer.
43 - marvell,tx-sram-addr: address of transmit descriptor buffer located in SRAM.
44 - marvell,tx-sram-size: size of transmit descriptor buffer located in SRAM.
|
| /Documentation/networking/device_drivers/ethernet/neterion/ |
| D | s2io.rst | 58 b. Offloads. Supports checksum offload(TCP/UDP/IP) on transmit
73 f. Multi-FIFO/Ring. Supports up to 8 transmit queues and receive rings,
80 Number of transmit queues
94 Size of each transmit queue
133 Transmit performance:
157 b. Ensure Transmit Checksum offload is enabled. Use ethtool to set/verify this
|
| /Documentation/userspace-api/media/rc/ |
| D | lirc-set-send-duty-cycle.rst | 14 IR transmit.
36 Get/set the duty cycle of the carrier signal for IR transmit.
|
| D | lirc-get-send-mode.rst | 14 LIRC_GET_SEND_MODE/LIRC_SET_SEND_MODE - Get/set current transmit mode.
39 Get/set current transmit mode.
|
| /Documentation/devicetree/bindings/spi/ |
| D | microchip,spi-pic32.txt | 7 of <fault-irq>, <receive-irq>, <transmit-irq>.
18 named "spi-tx" for transmit and named "spi-rx" for receive.
|
| /Documentation/networking/devlink/ |
| D | octeontx2.rst | 41 - Use to set the quantum which hardware uses for scheduling among transmit queues.
42 Hardware uses weighted DWRR algorithm to schedule among all transmit queues.
|
| /Documentation/devicetree/bindings/net/can/ |
| D | renesas,rcar-canfd.yaml | 124 - description: CAN0 transmit interrupt
125 - description: CAN0 transmit/receive FIFO receive completion interrupt
127 - description: CAN1 transmit interrupt
128 - description: CAN1 transmit/receive FIFO receive completion interrupt
|
| /Documentation/networking/caif/ |
| D | linux_caif.rst | 82 CAIF payload with receive and transmit functions.
173 layer->dn->transmit(layer->dn, packet);
183 'struct cflayer', just like the rest of the CAIF stack. In this way, transmit and
184 receive of packets is handled as by the rest of the layers: the 'dn->transmit()'
185 function is called in order to transmit data.
|
123456789