Searched full:frames (Results 1 – 25 of 192) sorted by relevance
12345678
| /Documentation/networking/device_drivers/can/freescale/ |
| D | flexcan.rst | 10 On/off RTR frames reception
19 and i.MX53 SOCs) only receive RTR frames if the controller is
22 The RX FIFO mode uses a hardware FIFO with a depth of 6 CAN frames,
24 CAN frames. With the help of the bigger buffer, the mailbox mode
27 As reception of RTR frames is part of the CAN standard, all flexcan
30 With the "rx-rtr" private flag the ability to receive RTR frames can
35 Receive RTR frames. (default)
37 The CAN controller can and will receive RTR frames.
39 On some IP cores the controller cannot receive RTR frames in the
45 Waive ability to receive RTR frames. (not supported on all IP cores)
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-tee | 6 RPMB frames can be routed to the RPMB device via the
9 will route the RPMB frames via user space. Conversely,
10 "kernel" means that the frames are routed via the RPMB
12 should be assumed that RPMB frames are routed via user
|
| D | sysfs-driver-hid-ntrig | 6 (RW) Number of contact frames ignored before acknowledging the
15 (RW) Number of empty (no contact) frames ignored before
19 number of empty frames. By holding off on deactivation for a few
20 frames false erroneous disconnects can be tolerated, where the
|
| /Documentation/networking/ |
| D | can.rst | 31 receive raw CAN frames, directly to/from the controller hardware.
32 Queueing of frames and higher-level transport protocols like ISO-TP
45 network layer as a network device, so that CAN frames from the
54 frames on different or the same CAN IDs. Several sockets listening on
55 the same interface for frames with the same CAN ID are all passed the
56 same received matching CAN frames. An application wishing to
60 CAN-IDs, frames, etc.
93 CAN frames between them, (sophisticated) queueing of CAN frames, and
142 Local Loopback of Sent Frames
160 some kind of local loopback of the sent CAN frames on the appropriate
[all …]
|
| D | iso15765-2.rst | 62 sender starts to send frames containing fragments of the data payload (called
63 Consecutive Frames - CF), stopping after every ``blocksize``-sized block to wait
159 * ``CAN_ISOTP_LISTEN_MODE``: listen only (do not send FC frames); normally
167 * ``CAN_ISOTP_TX_PADDING``: enable padding for transmitted frames, using
170 * ``CAN_ISOTP_RX_PADDING``: enable padding for the received frames, using
174 frames.
176 * ``CAN_ISOTP_CHK_PAD_DATA``: check padding bytes on the received frames
216 * ``txpad_content``: byte used as padding value for transmitted frames.
218 * ``rxpad_content``: byte used as padding value for received frames.
244 * ``bs``: blocksize provided in flow control frames.
[all …]
|
| D | mac80211-auth-assoc-deauth.txt | 22 BA session stop & deauth/disassoc frames
78 (data frames)
87 mac80211->driver: flush frames
|
| D | vxlan.rst | 68 ability to perform TCP segmentation offload of UDP encapsulated frames
71 receive side parsing of UDP encapsulated frames which allows NICs to
73 inner frames (only needed by NICs without protocol-agnostic offloads)
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | marvell,odmi-controller.txt | 17 - marvell,odmi-frames : Number of ODMI frames available. Each frame
36 marvell,odmi-frames = <4>;
|
| /Documentation/bpf/ |
| D | redirect.rst | 28 Not all drivers support transmitting frames after a redirect, and for
29 those that do, not all of them support non-linear frames. Non-linear xdp
30 bufs/frames are bufs/frames that contain more than one fragment.
|
| /Documentation/admin-guide/media/ |
| D | ipu3.rst | 23 frames in a format that is specific to the IPU3 (for consumption by the IPU3
71 Capturing frames in raw Bayer format
74 CIO2 MIPI CSI2 receiver is used to capture frames (in packed raw Bayer format)
75 from the raw sensors connected to the CSI2 ports. The captured frames are used
82 -- The IPU3 CSI2 receiver outputs the captured frames from the sensor in packed
91 frames in packed raw Bayer format to IPU3 CSI2 receiver.
129 With the above command, 10 frames are captured at 2592x1944 resolution, with
132 The captured frames are available as /tmp/frame-#.bin files.
199 The frames (in packed raw Bayer format specific to the IPU3) received by the
225 focus, auto exposure and auto white balance) statistics for the frames that are
[all …]
|
| D | rkisp1.rst | 52 - rkisp1_resizer_mainpath: used to resize and downsample frames for the
54 - rkisp1_resizer_selfpath: used to resize and downsample frames for the
60 rkisp1_mainpath, rkisp1_selfpath - Frames Capture Video Nodes
62 Those are the `mainpath` and `selfpath` capture devices to capture frames.
63 Those entities are the DMA engines that write the frames to memory.
76 can scale the frames up and down and also change the YUV sampling (for example
87 receives the frames using the CSI-2 protocol. It is responsible of configuring
98 white balance) statistics, and also histogram statistics for the frames that
130 Capturing Video Frames Example
187 Therefore the capture frames will not go through the 3A algorithms and
[all …]
|
| D | ipu6-isys.rst | 30 processes the image data from the sensors and outputs the frames to memory.
61 Capturing frames with IPU6 ISYS
64 IPU6 ISYS is used to capture frames from the camera sensors connected to the
90 media-ctl [#f1]_ and yavta [#f2]_ to transmit frames to IPU6 ISYS.
129 With the above command, 10 frames are captured at 1280x800 resolution with
130 sBGGR10 format. The captured frames are available as /tmp/frame-#.bin files.
|
| /Documentation/networking/device_drivers/can/ |
| D | can327.rst | 178 For EFF (29 bit) CAN frames, the address format is slightly different,
183 The ELM327 will receive both SFF and EFF frames - the current CAN
202 Sending RTR frames is not supported and will be dropped silently.
208 not supported, and is hard coded to ON. Thus, frames are not ACKed
211 "receive reply" mode, in which it *does* ACK any received frames.
226 The length of outgoing RTR frames cannot be set. In fact, some
228 send RTR frames at all.
261 frames, and to check whether frames are complete. While it is possible
319 We need this to tell the "length" of RTR frames.
|
| /Documentation/userspace-api/media/v4l/ |
| D | dev-stateless-decoder.rst | 10 between processed frames. This means that each frame is decoded independently
11 of any previous and future frames, and that the client is responsible for
15 has to do is to provide the raw encoded stream and dequeue decoded frames in
110 frame buffer resolution for the decoded frames.
113 pixel format for decoded frames.
201 for the stream to be properly decoded (taking e.g. reference frames
326 frames were submitted to the ``OUTPUT`` queue).
330 error, then all following decoded frames that refer to it also have the
332 produce (likely corrupted) frames.
351 target until all the frames referencing it have been decoded. The safest way to
[all …]
|
| D | vidioc-g-parm.rst | 41 repeat frames to achieve the requested frame interval.
107 - This is the desired period between successive frames captured by
112 generates video frames. If the speed is fixed, then the driver may
113 choose to skip or repeat frames in order to achieve the requested
166 - This is the desired period between successive frames output by the
170 The field is intended to repeat frames on the driver side in
177 frames are queued up to the encoder.
250 successive fields or frames to remove color edge artifacts and
|
| D | dev-encoder.rst | 9 A stateful video encoder takes raw video frames in display order and encodes
257 to 1/24 (or 24 frames per second) will produce a coded video stream
260 frames at a different rate. It can be used by the driver to help
266 which raw frames are supplied.
270 ``timeperframe`` deals with *frames*, not fields. So for interlaced
309 fast raw frames are queued on the ``OUTPUT`` queue.
313 ``timeperframe`` deals with *frames*, not fields. So for interlaced
439 * encoded frames produced after the restart must not reference any
440 frames produced before the stop, e.g. no long term references for
459 queues and memory-to-memory devices. In addition, the order of encoded frames
[all …]
|
| D | streaming-par.rst | 14 The current video standard determines a nominal number of frames per
15 second. If less than this number of frames is to be captured or output,
|
| D | dev-decoder.rst | 10 H.264/HEVC stream, raw VP8/9 stream) and decodes them into raw video frames in
51 decoded frames; for encoders, the queue of buffers containing an encoded
82 the order in which frames are decoded; may differ from display order if the
91 the order in which frames must be displayed; for encoders, ``OUTPUT``
104 stream, which clears the list of earlier reference frames (DPBs).
107 an encoded frame that does not reference frames decoded earlier, i.e.
119 frames; ``V4L2_BUF_TYPE_VIDEO_OUTPUT`` or
142 resolution in pixels of source frames being source to the encoder and
398 No decoded frames are produced during this phase.
416 frame buffer resolution for the decoded frames.
[all …]
|
| /Documentation/driver-api/surface_aggregator/ |
| D | ssh.rst | 131 Both |NAK|- and |ACK|-type frames are used to control flow of messages and
132 thus do not carry a payload. |DATA_SEQ|- and |DATA_NSQ|-type frames on the
159 ``DATA_SEQ``- or ``DATA_NSQ``-type frames with other ``DATA``- type frames.
168 where both frames have the same sequence ID (``SEQ``). Here, ``FRAME(D)``
180 to zero. For |DATA_NSQ|-type frames, both exchanges are the same:
197 only known payload type of |DATA| frames, with a payload-type value of
268 ID on the frames. Note that the sequence ID of the frames for a
309 The protocol can, in theory, handle up to ``U8_MAX`` frames in parallel,
322 carrying command being ACKed) have been observed. In any case, frames (and
324 is exceeded. This is done by the EC for frames with a timeout of one second,
[all …]
|
| /Documentation/networking/device_drivers/ethernet/intel/ |
| D | fm10k.rst | 31 Control. It will not send pause frames. This may result in dropped frames.
60 Jumbo Frames
62 Jumbo Frames support is enabled by changing the Maximum Transmission Unit (MTU)
81 NOTE: The maximum MTU setting for Jumbo Frames is 15342. This value coincides
82 with the maximum Jumbo Frames size of 15364 bytes.
|
| D | idpf.rst | 53 Jumbo Frames
55 Jumbo Frames support is enabled by changing the Maximum Transmission Unit (MTU)
65 The maximum MTU setting for jumbo frames is 9706. This corresponds to the
75 frames. If you observe a drop in performance after enabling jumbo frames,
|
| /Documentation/networking/device_drivers/fddi/ |
| D | defza.rst | 37 all-multi mode is also supported for LLC frames and it is used if
39 supports separate enables for LLC and SMT frames, but this driver
55 7. Queueing incoming/outgoing SMT frames in the driver if the SMT
|
| /Documentation/networking/device_drivers/ethernet/freescale/dpaa2/ |
| D | ethernet-driver.rst | 107 frames, but must be affine to the CPUs for the purpose of traffic distribution.
109 Frames are transmitted and received through hardware frame queues, which can be
111 enqueues TX frames on egress queues and after transmission is complete a TX
114 When frames are available on ingress queues, a data availability notification
116 queues in the same channel have available frames, only one notification is sent.
169 Hardware checksum offloading is supported for TCP and UDP over IPv4/6 frames.
176 Scatter-gather frames are supported on both RX and TX paths. On TX, SG support
179 The DPAA2 hardware can process jumbo Ethernet frames of up to 10K bytes.
|
| /Documentation/netlink/specs/ |
| D | ethtool.yaml | 480 name: rx-max-frames
486 name: rx-max-frames-irq
492 name: tx-max-frames
498 name: tx-max-frames-irq
516 name: rx-max-frames-low
522 name: tx-max-frames-low
531 name: rx-max-frames-high
537 name: tx-max-frames-high
552 name: tx-aggr-max-frames
573 name: tx-frames
[all …]
|
| /Documentation/sound/ |
| D | utimers.rst | 18 we have a network application sending frames to one snd-aloop device,
102 frames from network and sends them to snd-aloop pcm device, and another
103 application listens for frames on the other snd-aloop pcm device, it
122 the timer is going to tick every time a new period of frames is ready.
|
12345678