Searched full:buffers (Results 1 – 25 of 338) sorted by relevance
12345678910>>...14
| /Documentation/userspace-api/media/v4l/ |
| D | mmap.rst | 18 Streaming is an I/O method where only pointers to buffers are exchanged
20 mapping is primarily intended to map buffers in device memory into the
24 drivers support streaming as well, allocating buffers in DMA-able main
27 A driver can support many sets of buffers. Each set is identified by a
32 To allocate device buffers applications call the
34 of buffers and buffer type, for example ``V4L2_BUF_TYPE_VIDEO_CAPTURE``.
35 This ioctl can also be used to change the number of buffers or to free
36 the allocated memory, provided none of the buffers are still mapped.
38 Before applications can access the buffers they must map them into their
40 location of the buffers in device memory can be determined with the
[all …]
|
| D | userp.rst | 19 methods. Buffers (planes) are allocated by the application itself, and
26 No buffers (planes) are allocated beforehand, consequently they are not
27 indexed and cannot be queried like mapped buffers with the
51 :ref:`VIDIOC_QBUF <VIDIOC_QBUF>` ioctl. Although buffers are commonly
60 Filled or displayed buffers are dequeued with the
66 Applications must take care not to free buffers without dequeuing.
67 Firstly, the buffers remain locked for longer, wasting physical memory.
73 buffers, to start capturing and enter the read loop. Here the
76 and enqueue buffers, when enough buffers are stacked up output is
78 buffers it must wait until an empty buffer can be dequeued and reused.
[all …]
|
| D | dev-decoder.rst | 12 from the client to process these buffers.
50 the destination buffer queue; for decoders, the queue of buffers containing
51 decoded frames; for encoders, the queue of buffers containing an encoded
54 into ``CAPTURE`` buffers.
84 ``OUTPUT`` buffers must be queued by the client in decode order; for
85 encoders ``CAPTURE`` buffers must be returned by the encoder in decode order.
92 buffers must be queued by the client in display order; for decoders,
93 ``CAPTURE`` buffers must be returned by the decoder in display order.
117 the source buffer queue; for decoders, the queue of buffers containing
118 an encoded bytestream; for encoders, the queue of buffers containing raw
[all …]
|
| D | capture.c.rst | 51 struct buffer *buffers;
91 if (-1 == read(fd, buffers[0].start, buffers[0].length)) {
106 process_image(buffers[0].start, buffers[0].length);
132 process_image(buffers[buf.index].start, buf.bytesused);
160 if (buf.m.userptr == (unsigned long)buffers[i].start
161 && buf.length == buffers[i].length)
268 buf.m.userptr = (unsigned long)buffers[i].start;
269 buf.length = buffers[i].length;
287 free(buffers[0].start);
292 if (-1 == munmap(buffers[i].start, buffers[i].length))
[all …]
|
| D | vidioc-create-bufs.rst | 13 VIDIOC_CREATE_BUFS - Create buffers for Memory Mapped or User Pointer or DMA Buffer I/O
34 This ioctl is used to create buffers for :ref:`memory mapped <mmap>`
38 over buffers is required. This ioctl can be called multiple times to
39 create buffers of different sizes.
41 To allocate the device buffers applications must initialize the relevant
43 ``count`` field must be set to the number of requested buffers, the
47 The ``format`` field specifies the image format that the buffers must be
54 sizes (for multi-planar formats) will be used for the allocated buffers.
58 The buffers created by this ioctl will have as minimum size the size
68 will attempt to allocate up to the requested number of buffers and store
[all …]
|
| D | vidioc-reqbufs.rst | 36 Memory mapped buffers are located in device memory and must be allocated
38 space. User buffers are allocated by applications themselves, and this
40 to setup some internal structures. Similarly, DMABUF buffers are
45 To allocate device buffers applications initialize all fields of the
48 the desired number of buffers, ``memory`` must be set to the requested
51 allocate the requested number of buffers and it stores the actual number
54 number is also possible when the driver requires more buffers to
56 buffers, one displayed and one filled by the application.
62 buffers. Note that if any buffers are still mapped or exported via DMABUF,
66 If ``V4L2_BUF_CAP_SUPPORTS_ORPHANED_BUFS`` is set, then these buffers are
[all …]
|
| D | dmabuf.rst | 10 The DMABUF framework provides a generic method for sharing buffers
19 exporting V4L2 buffers as DMABUF file descriptors.
25 importing DMA buffers through DMABUF file descriptors is supported is
29 This I/O method is dedicated to sharing DMA buffers between different
31 DRM). Buffers (planes) are allocated by a driver on behalf of an
32 application. Next, these buffers are exported to the application as file
63 buffers, every plane can be associated with a different DMABUF
64 descriptor. Although buffers are commonly cycled, applications can pass
121 Captured or displayed buffers are dequeued with the
129 buffers, to start capturing and enter the read loop. Here the
[all …]
|
| D | vidioc-remove-bufs.rst | 13 VIDIOC_REMOVE_BUFS - Removes buffers from a queue
35 remove buffers from a queue.
55 - The number of buffers to be removed with indices 'index' until 'index + count - 1'.
56 All buffers in this range must be valid and in DEQUEUED state.
62 - Type of the stream or buffers, this is the same as the struct
76 buffers will be freed and one of the error codes below will be returned:
80 One or more of the buffers in the range ``index`` to ``index + count - 1`` are not
84 One or more of the buffers in the range ``index`` to ``index + count - 1`` do not
|
| D | vidioc-streamon.rst | 43 Capture hardware is disabled and no input buffers are filled (if there
44 are any empty buffers in the incoming queue) until ``VIDIOC_STREAMON``
51 If ``VIDIOC_STREAMON`` fails then any already queued buffers will remain
55 in progress, unlocks any user pointer buffers locked in physical memory,
56 and it removes all buffers from the incoming and outgoing queues. That
63 If buffers have been queued with :ref:`VIDIOC_QBUF` and
65 ``VIDIOC_STREAMON``, then those queued buffers will also be removed from
77 but ``VIDIOC_STREAMOFF`` will return queued buffers to their starting
95 The buffer ``type`` is not supported, or no buffers have been
|
| D | dev-encoder.rst | 157 desired size of ``CAPTURE`` buffers; the encoder may adjust it to
169 adjusted size of ``CAPTURE`` buffers.
307 coded video. It does *not* set the rate at which buffers arrive on the
365 buffers to be aligned to 1920x1088 for codecs with 16x16 macroblock
375 7. Allocate buffers for both ``OUTPUT`` and ``CAPTURE`` via
381 requested number of buffers to allocate; greater than zero.
393 actual number of buffers allocated.
397 The actual number of allocated buffers may differ from the ``count``
403 To allocate more than the minimum number of OUTPUT buffers (for pipeline
405 control to get the minimum number of buffers required, and pass the
[all …]
|
| D | dev-stateless-decoder.rst | 100 destination buffers parsed/decoded from the bytestream.
167 to obtain up-to-date information about the buffers size and layout.
169 6. Allocate source (bytestream) buffers via :c:func:`VIDIOC_REQBUFS` on
175 requested number of buffers to allocate; greater than zero.
186 actual number of buffers allocated.
189 minimum of required number of ``OUTPUT`` buffers for the given format and
191 to get the actual number of buffers allocated.
193 7. Allocate destination (raw format) buffers via :c:func:`VIDIOC_REQBUFS` on the
199 requested number of buffers to allocate; greater than zero. The client
200 is responsible for deducing the minimum number of buffers required
[all …]
|
| D | v4l2grab.c.rst | 67 struct buffer *buffers;
96 buffers = calloc(req.count, sizeof(*buffers));
106 buffers[n_buffers].length = buf.length;
107 buffers[n_buffers].start = v4l2_mmap(NULL, buf.length,
111 if (MAP_FAILED == buffers[n_buffers].start) {
156 fwrite(buffers[buf.index].start, buf.bytesused, 1, fout);
165 v4l2_munmap(buffers[i].start, buffers[i].length);
|
| /Documentation/userspace-api/media/dvb/ |
| D | dmx-reqbufs.rst | 38 Memory mapped buffers are located in device memory and must be allocated
40 space. User buffers are allocated by applications themselves, and this
42 to setup some internal structures. Similarly, DMABUF buffers are
47 To allocate device buffers applications initialize all fields of the
49 to the desired number of buffers, and ``size`` to the size of each
53 attempt to allocate the requested number of buffers and it stores the actual
55 number is also possible when the driver requires more buffers to
63 buffers, however this cannot succeed when any buffers are still mapped.
64 A ``count`` value of zero frees all buffers, after aborting or finishing
|
| /Documentation/ABI/testing/ |
| D | sysfs-kernel-dmabuf-buffers | 1 What: /sys/kernel/dmabuf/buffers
5 Description: The /sys/kernel/dmabuf/buffers directory contains a
7 /sys/kernel/dmabuf/buffers/<inode_number> will contain the
12 What: /sys/kernel/dmabuf/buffers/<inode_number>/exporter_name
19 What: /sys/kernel/dmabuf/buffers/<inode_number>/size
|
| /Documentation/admin-guide/media/ |
| D | cafe_ccic.rst | 37 buffers until the time comes to transfer data. If this option is set,
38 then worst-case-sized buffers will be allocated at module load time.
42 - dma_buf_size: The size of DMA buffers to allocate. Note that this
43 option is only consulted for load-time allocation; when buffers are
48 buffers. Normally, the driver tries to use three buffers; on faster
51 - min_buffers: The minimum number of streaming I/O buffers that the driver
56 - max_buffers: The maximum number of streaming I/O buffers; default is
|
| /Documentation/gpu/ |
| D | xen-front.rst | 9 Driver modes of operation in terms of display buffers used
13 :doc: Driver modes of operation in terms of display buffers used
15 Buffers allocated by the frontend driver
19 :doc: Buffers allocated by the frontend driver
21 Buffers allocated by the backend
25 :doc: Buffers allocated by the backend
|
| /Documentation/filesystems/ |
| D | relay.rst | 12 as a set of per-cpu kernel buffers ('channel buffers'), each
14 clients write into the channel buffers using efficient write
19 are associated with the channel buffers using the API described below.
21 The format of the data logged into the channel buffers is completely
36 sub-buffers. Messages are written to the first sub-buffer until it is
38 the next (if available). Messages are never split across sub-buffers.
60 read sub-buffers; thus in cases where read(2) is being used to drain
61 the channel buffers, special-purpose communication between kernel and
96 allowing both to convey the state of buffers (full, empty, amount of
98 consumes the read sub-buffers; thus in cases where read(2) is being
[all …]
|
| /Documentation/userspace-api/media/mediactl/ |
| D | request-api.rst | 21 on the media pipeline, reconfigure it for the next frame, queue the buffers to
28 specific buffers. This allows user-space to schedule several tasks ("requests")
59 instead of being immediately applied, and buffers queued to a request do not
65 Once the configuration and buffers of the request are specified, it can be
72 output buffers, not for capture buffers. Attempting to add a capture buffer
77 buffers are processed. Media controller drivers do a best effort implementation
82 It is not allowed to mix queuing requests with directly queuing buffers:
99 once all its associated buffers are available for dequeuing and all the
102 dequeue its buffers: buffers that are available halfway through a request can
135 to queue many such buffers in advance. It can also take advantage of requests'
[all …]
|
| /Documentation/arch/x86/ |
| D | mds.rst | 10 on internal buffers in Intel CPUs. The variants are:
21 buffers are partitioned between Hyper-Threads so cross thread forwarding is
25 MFBDS leaks Fill Buffer Entries. Fill buffers are used internally to manage
27 to a memory or I/O operation. Fill buffers can forward data to a load
31 be exploited under certain conditions. Fill buffers are shared between
74 thread case (SMT off): Force the CPU to clear the affected buffers.
78 the affected CPU buffers when the VERW instruction is executed.
107 hope that it might actually clear the buffers. The state is reflected
142 When transitioning from kernel to user space the CPU buffers are flushed
153 Interrupts returning to kernel don't clear CPUs buffers since the
[all …]
|
| /Documentation/sound/designs/ |
| D | compress-accel.rst | 27 - separate buffers (input + output) for each operation
29 - expose buffers using mmap to user space
50 have separate I/O buffers.
88 Creates a set of input/output buffers. The input buffer size is
92 output buffers (using 'dma_buf_export()' function). The anonymous
93 file descriptors for those buffers are passed to user space.
97 Free a set of input/output buffers. If a task is active, the stop
117 start of the new stream data. It is useful to keep the allocated buffers
|
| /Documentation/networking/device_drivers/ethernet/google/ |
| D | gve.rst | 62 Therefore, the packet buffers can be anywhere in guest memory.
125 The descriptor rings are power-of-two-sized ring buffers consisting of
131 Each queue's buffers must be registered in advance with the device as a
136 gve maps the buffers for transmit rings into a FIFO and copies the packets
141 The buffers for receive rings are put into a data ring that is the same
149 - TX and RX buffers queues, which send descriptors to the device, use MMIO
163 - TX packets have a 16 bit completion_tag and RX buffers have a 16 bit
169 A packet's buffers are DMA mapped for the device to access before transmission.
170 After the packet was successfully transmitted, the buffers are unmapped.
174 The driver posts fixed sized buffers to HW on the RX buffer queue. The packet
|
| /Documentation/driver-api/iio/ |
| D | index.rst | 15 buffers
17 triggered-buffers
|
| /Documentation/admin-guide/hw-vuln/ |
| D | tsx_async_abort.rst | 7 data which is available in various CPU internal buffers by using asynchronous
39 data into temporary microarchitectural structures (buffers). The data in
40 those buffers can be forwarded to load operations as an optimization.
54 executed loads may read data from those internal buffers and pass it to dependent
58 Because the buffers are potentially shared between Hyper-Threads cross
63 which in turn potentially leaks data stored in the buffers.
100 * - 'Vulnerable: Clear CPU buffers attempted, no microcode'
107 instructions without a guarantee that they clear the CPU buffers.
114 * - 'Mitigation: Clear CPU buffers'
115 - The microcode has been updated to clear the buffers. TSX is still enabled.
[all …]
|
| D | processor_mmio_stale_data.rst | 12 stale data into core fill buffers where the data can subsequently be inferred
29 Stale data may propagate from fill buffers (FB) into the non-coherent portion
42 response and transaction buffers may now reside in a core fill buffer.
61 processors affected by FBSDP, this may expose stale data from the fill buffers
64 Shared Buffers Data Sampling (SBDS) (CVE-2022-21125)
67 into client core fill buffers, processors affected by MFBDS can leak data from
71 Shared Buffers Data Read (SBDR) (CVE-2022-21123)
111 clear the CPU fill buffers via VERW instruction.
123 Shared Buffers Data Read (SBDR) vulnerability or the sideband stale
153 same mitigation strategy to force the CPU to clear the affected buffers before
[all …]
|
| /Documentation/networking/ |
| D | smc-sysctl.rst | 33 - 0 - Use physically contiguous buffers
34 - 1 - Use virtually contiguous buffers
35 - 2 - Mixed use of the two types. Try physically contiguous buffers first.
36 If not available, use virtually contiguous buffers then.
|
12345678910>>...14