| /kernel/linux/linux-5.10/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 | 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.
78 ``OUTPUT`` buffers must be queued by the client in decode order; for
79 encoders ``CAPTURE`` buffers must be returned by the encoder in decode order.
86 buffers must be queued by the client in display order; for decoders,
87 ``CAPTURE`` buffers must be returned by the decoder in display order.
110 the source buffer queue; for decoders, the queue of buffers containing
111 an encoded bytestream; for encoders, the queue of buffers containing raw
[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 | 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-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 | 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 | 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-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 …]
|
| /kernel/linux/linux-4.19/Documentation/media/uapi/v4l/ |
| D | mmap.rst | 17 Streaming is an I/O method where only pointers to buffers are exchanged
19 mapping is primarily intended to map buffers in device memory into the
23 drivers support streaming as well, allocating buffers in DMA-able main
26 A driver can support many sets of buffers. Each set is identified by a
31 To allocate device buffers applications call the
33 of buffers and buffer type, for example ``V4L2_BUF_TYPE_VIDEO_CAPTURE``.
34 This ioctl can also be used to change the number of buffers or to free
35 the allocated memory, provided none of the buffers are still mapped.
37 Before applications can access the buffers they must map them into their
39 location of the buffers in device memory can be determined with the
[all …]
|
| D | userp.rst | 18 methods. Buffers (planes) are allocated by the application itself, and
25 No buffers (planes) are allocated beforehand, consequently they are not
26 indexed and cannot be queried like mapped buffers with the
50 :ref:`VIDIOC_QBUF <VIDIOC_QBUF>` ioctl. Although buffers are commonly
59 Filled or displayed buffers are dequeued with the
65 Applications must take care not to free buffers without dequeuing. For
66 once, the buffers remain locked until further, wasting physical memory.
72 buffers, to start capturing and enter the read loop. Here the
75 and enqueue buffers, when enough buffers are stacked up output is
77 buffers it must wait until an empty buffer can be dequeued and reused.
[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-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, however this cannot succeed when any buffers are still mapped.
63 A ``count`` value of zero frees all buffers, after aborting or finishing
[all …]
|
| D | dmabuf.rst | 9 The DMABUF framework provides a generic method for sharing buffers
18 exporting V4L2 buffers as DMABUF file descriptors.
24 importing DMA buffers through DMABUF file descriptors is supported is
28 This I/O method is dedicated to sharing DMA buffers between different
30 DRM). Buffers (planes) are allocated by a driver on behalf of an
31 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-create-bufs.rst | 12 VIDIOC_CREATE_BUFS - Create buffers for Memory Mapped or User Pointer or DMA Buffer I/O
35 This ioctl is used to create buffers for :ref:`memory mapped <mmap>`
39 over buffers is required. This ioctl can be called multiple times to
40 create buffers of different sizes.
42 To allocate the device buffers applications must initialize the relevant
44 ``count`` field must be set to the number of requested buffers, the
48 The ``format`` field specifies the image format that the buffers must be
55 sizes (for multi-planar formats) will be used for the allocated buffers.
59 The buffers created by this ioctl will have as minimum size the size
69 will attempt to allocate up to the requested number of buffers and store
[all …]
|
| /kernel/linux/linux-5.10/drivers/media/test-drivers/vivid/ |
| D | vivid-vid-common.c | 41 .buffers = 1,
50 .buffers = 1,
58 .buffers = 1,
66 .buffers = 1,
74 .buffers = 1,
82 .buffers = 1,
90 .buffers = 1,
98 .buffers = 1,
106 .buffers = 1,
114 .buffers = 1,
[all …]
|
| /kernel/linux/linux-4.19/drivers/media/platform/vivid/ |
| D | vivid-vid-common.c | 41 .buffers = 1,
50 .buffers = 1,
58 .buffers = 1,
66 .buffers = 1,
74 .buffers = 1,
82 .buffers = 1,
90 .buffers = 1,
98 .buffers = 1,
106 .buffers = 1,
114 .buffers = 1,
[all …]
|
| /kernel/linux/linux-5.10/lib/xz/ |
| D | xz_dec_test.c | 42 * Input and output buffers. The input buffer is used as a temporary safe
49 * Structure to pass the input and output buffers to the XZ decoder.
52 static struct xz_buf buffers = { variable
75 buffers.in_pos = 0; in xz_dec_test_open()
76 buffers.in_size = 0; in xz_dec_test_open()
77 buffers.out_pos = 0; in xz_dec_test_open()
120 while ((remaining > 0 || buffers.out_pos == buffers.out_size) in xz_dec_test_write()
122 if (buffers.in_pos == buffers.in_size) { in xz_dec_test_write()
123 buffers.in_pos = 0; in xz_dec_test_write()
124 buffers.in_size = min(remaining, sizeof(buffer_in)); in xz_dec_test_write()
[all …]
|
| /kernel/linux/linux-4.19/lib/xz/ |
| D | xz_dec_test.c | 42 * Input and output buffers. The input buffer is used as a temporary safe
49 * Structure to pass the input and output buffers to the XZ decoder.
52 static struct xz_buf buffers = { variable
75 buffers.in_pos = 0; in xz_dec_test_open()
76 buffers.in_size = 0; in xz_dec_test_open()
77 buffers.out_pos = 0; in xz_dec_test_open()
120 while ((remaining > 0 || buffers.out_pos == buffers.out_size) in xz_dec_test_write()
122 if (buffers.in_pos == buffers.in_size) { in xz_dec_test_write()
123 buffers.in_pos = 0; in xz_dec_test_write()
124 buffers.in_size = min(remaining, sizeof(buffer_in)); in xz_dec_test_write()
[all …]
|
| /kernel/linux/linux-5.10/drivers/media/pci/ivtv/ |
| D | ivtv-queue.c | 35 q->buffers = 0; in ivtv_queue_init()
53 q->buffers++; in ivtv_enqueue()
68 q->buffers--; in ivtv_dequeue()
82 from->buffers--; in ivtv_queue_move_buf()
88 to->buffers++; in ivtv_queue_move_buf()
93 /* Move 'needed_bytes' worth of buffers from queue 'from' into queue 'to'.
94 If 'needed_bytes' == 0, then move all buffers from 'from' into 'to'.
95 If 'steal' != NULL, then buffers may also taken from that queue if
99 also cleared if buffers need to be taken from the 'steal' queue and
107 -ENOMEM is returned if the buffers could not be obtained, 0 if all
[all …]
|
| /kernel/linux/linux-4.19/drivers/staging/media/zoran/ |
| D | zoran_driver.c | 192 fh->buffers.buffer_size = v4l_bufsize; in map_mode_raw()
193 fh->buffers.num_buffers = v4l_nbufs; in map_mode_raw()
198 fh->buffers.buffer_size = jpg_bufsize; in map_mode_jpg()
199 fh->buffers.num_buffers = jpg_nbufs; in map_mode_jpg()
207 * Allocate the V4L grab buffers
218 for (i = 0; i < fh->buffers.num_buffers; i++) { in v4l_fbuffer_alloc()
219 if (fh->buffers.buffer[i].v4l.fbuffer) in v4l_fbuffer_alloc()
226 mem = kmalloc(fh->buffers.buffer_size, in v4l_fbuffer_alloc()
236 fh->buffers.buffer[i].v4l.fbuffer = mem; in v4l_fbuffer_alloc()
237 fh->buffers.buffer[i].v4l.fbuffer_phys = virt_to_phys(mem); in v4l_fbuffer_alloc()
[all …]
|
| /kernel/linux/linux-4.19/drivers/media/pci/ivtv/ |
| D | ivtv-queue.c | 47 q->buffers = 0; in ivtv_queue_init()
65 q->buffers++; in ivtv_enqueue()
80 q->buffers--; in ivtv_dequeue()
94 from->buffers--; in ivtv_queue_move_buf()
100 to->buffers++; in ivtv_queue_move_buf()
105 /* Move 'needed_bytes' worth of buffers from queue 'from' into queue 'to'.
106 If 'needed_bytes' == 0, then move all buffers from 'from' into 'to'.
107 If 'steal' != NULL, then buffers may also taken from that queue if
111 also cleared if buffers need to be taken from the 'steal' queue and
119 -ENOMEM is returned if the buffers could not be obtained, 0 if all
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/media/ |
| D | v4l2-videobuf.rst | 21 and user space. It handles the allocation and management of buffers for
34 Not all video devices use the same kind of buffers. In fact, there are (at
37 - Buffers which are scattered in both the physical and (kernel) virtual
38 address spaces. (Almost) all user-space buffers are like this, but it
39 makes great sense to allocate kernel-space buffers this way as well when
44 - Buffers which are physically scattered, but which are virtually
45 contiguous; buffers allocated with vmalloc(), in other words. These
46 buffers are just as hard to use for DMA operations, but they can be
48 buffers are convenient.
50 - Buffers which are physically contiguous. Allocation of this kind of
[all …]
|
| /kernel/linux/linux-4.19/Documentation/media/kapi/ |
| D | v4l2-videobuf.rst | 19 and user space. It handles the allocation and management of buffers for
32 Not all video devices use the same kind of buffers. In fact, there are (at
35 - Buffers which are scattered in both the physical and (kernel) virtual
36 address spaces. (Almost) all user-space buffers are like this, but it
37 makes great sense to allocate kernel-space buffers this way as well when
42 - Buffers which are physically scattered, but which are virtually
43 contiguous; buffers allocated with vmalloc(), in other words. These
44 buffers are just as hard to use for DMA operations, but they can be
46 buffers are convenient.
48 - Buffers which are physically contiguous. Allocation of this kind of
[all …]
|
| /kernel/linux/linux-4.19/Documentation/media/uapi/dvb/ |
| D | dmx-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
47 to the desired number of buffers, and ``size`` to the size of each
51 attempt to allocate the requested number of buffers and it stores the actual
53 number is also possible when the driver requires more buffers to
61 buffers, however this cannot succeed when any buffers are still mapped.
62 A ``count`` value of zero frees all buffers, after aborting or finishing
|
| /kernel/linux/linux-5.10/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
|