| /linux-5.19.10/Documentation/userspace-api/media/v4l/ |
| D | planar-apis.rst | 6 Single- and multi-planar APIs
15 Initially, V4L2 API did not support multi-planar buffers and a set of
17 constitute what is being referred to as the "multi-planar API".
20 depending on whether single- or multi-planar API is being used. An
22 corresponding buffer type to its ioctl calls. Multi-planar versions of
24 available multi-planar buffer types see enum
28 Multi-planar formats
31 Multi-planar API introduces new multi-planar formats. Those formats use
33 the multi-planar API and a multi-planar format. Multi-planar API calls
34 can handle all single-planar formats as well (as long as they are passed
[all …]
|
| D | pixfmt.rst | 12 single-planar API, while the latter is used with the multi-planar
13 version (see :ref:`planar-apis`). Image formats are negotiated with
|
| D | vidioc-querybuf.rst | 47 using the :ref:`multi-planar API <planar-apis>`, the ``m.planes``
57 set to the current I/O method. For the single-planar API, the
59 device memory, the ``length`` field its size. For the multi-planar API,
|
| D | vidioc-querycap.rst | 148 - The device supports the single-planar API through the
152 - The device supports the :ref:`multi-planar API <planar-apis>`
156 - The device supports the single-planar API through the
160 - The device supports the :ref:`multi-planar API <planar-apis>`
164 - The device supports the single-planar API through the Video
168 - The device supports the :ref:`multi-planar API <planar-apis>`
|
| D | func-munmap.rst | 36 single-planar API and in the struct
38 multi-planar API.
|
| D | vidioc-expbuf.rst | 48 one. For the multi-planar API, applications set the ``plane`` field to
51 the single-planar API, applications must set ``plane`` to zero.
55 case of multi-planar API, every plane is exported separately using
137 - Index of the plane to be exported when using the multi-planar API.
|
| D | pixfmt-intro.rst | 46 and are referred to as "multi-planar formats". For example, a
50 in the 2-planar version or with each component in its own buffer in the
51 3-planar case. Those sub-buffers are referred to as "*planes*".
|
| D | pixfmt-v4l2-mplane.rst | 4 Multi-planar format structures
8 and layout for each of the planes in a multi-planar format. The
74 - The pixel format. Both single- and multi-planar four character
|
| D | func-mmap.rst | 39 single-planar API, and the same value as returned by the driver in
41 the multi-planar API.
94 the single-planar API, and the same value as returned by the driver
96 ``mem_offset`` field for the multi-planar API.
|
| D | vidioc-qbuf.rst | 58 :ref:`multi-planar API <planar-apis>`, the ``m.planes`` field must
73 multi-planar API is used, ``m.userptr`` and ``length`` members of the
87 file descriptor associated with a DMABUF buffer. When the multi-planar
132 buffer might be corrupted. When using the multi-planar API, the planes
139 and the value is only for the application convenience. When the multi-planar
|
| D | mmap.rst | 41 :ref:`VIDIOC_QUERYBUF` ioctl. In the single-planar
45 multi-planar API, struct :c:type:`v4l2_buffer` contains an
48 multi-planar API, every plane of every buffer has to be mapped
56 Example: Mapping buffers in the single-planar API
126 Example: Mapping buffers in the multi-planar API
174 /* length in struct v4l2_buffer in multi-planar API stores the size
|
| D | pixfmt-yuv-planar.rst | 3 .. planar-yuv:
12 - Semi-planar formats use two planes. The first plane is the luma plane and
16 - Fully planar formats use three planes to store the Y, Cb and Cr components
23 Some planar formats allow planes to be placed in independent memory locations.
26 and applications that support the multi-planar API, described in
27 :ref:`planar-apis`. Unless explicitly documented as supporting non-contiguous
178 Semi-planar YUV 4:2:0 formats. The chroma plane is subsampled by 2 in each
267 Semi-planar YUV 4:2:0 formats, using macroblock tiling. The chroma plane is
353 Semi-planar YUV 4:2:2 formats. The chroma plane is subsampled by 2 in the
456 Semi-planar YUV 4:4:4 formats. The chroma plane is not subsampled.
|
| D | common.rst | 57 planar-apis
|
| D | buffer.rst | 11 the Streaming I/O methods. In the multi-planar API, the data is held in
18 :ref:`VIDIOC_DQBUF <VIDIOC_QBUF>` ioctl. In the multi-planar API,
255 - For the single-planar API and when ``memory`` is
263 - For the single-planar API and when ``memory`` is
269 - When using the multi-planar API, contains a userspace pointer to
283 single-planar API. This is set by the driver based on the calls to
286 multi-planar API the application sets this to the number of
401 - Buffer of a single-planar video capture stream, see
405 - Buffer of a multi-planar video capture stream, see
409 - Buffer of a single-planar video output stream, see
[all …]
|
| D | v4l2.rst | 76 - Designed and documented the multi-planar API.
227 latest changes. Added the :ref:`multi-planar API <planar-apis>`.
|
| D | pixfmt-reserved.rst | 181 YUV420 planar in blocks of 256 pixels.
203 - Two-planar format used by Samsung S5C73MX cameras. The first plane
236 - Compressed two-planar YVU420 format used by Mediatek MT8173, MT8192,
|
| D | pixfmt-inzi.rst | 15 Proprietary multi-planar format used by Intel SR300 Depth cameras, comprise of
|
| D | vidioc-create-bufs.rst | 53 ``type`` field the requested buffer size (for single-planar) or plane
54 sizes (for multi-planar formats) will be used for the allocated buffers.
|
| D | vidioc-g-fmt.rst | 111 :ref:`multi-planar version of the API <planar-apis>`.
|
| /linux-5.19.10/Documentation/devicetree/bindings/media/i2c/ |
| D | tda1997x.txt | 8 - YUV422 semi-planar 8bit per component (16 bits total): Y[11:4] CbCr[11:4]
9 - YUV422 semi-planar 10bit per component (20 bits total): Y[11:2] CbCr[11:2]
10 - YUV422 semi-planar 12bit per component (24 bits total): - Y[11:0] CbCr[11:0]
18 - YUV422 semi-planar 12bit per component (24 bits total): Y[11:0] CbCr[11:0]
76 * The 8bpp YUV422 semi-planar mode outputs CbCr[11:4]
118 * The 8bpp YUV422 semi-planar mode outputs CbCr[11:4]
|
| /linux-5.19.10/Documentation/fb/ |
| D | pxafb.rst | 110 bpp = 24 -- for YUV444 planar
112 bpp = 16 -- for YUV422 planar (1 pixel = 1 Y + 1/2 Cb + 1/2 Cr)
114 bpp = 12 -- for YUV420 planar (1 pixel = 1 Y + 1/4 Cb + 1/4 Cr)
122 for YUV planar modes, it is a requirement for the component
151 3. for YUV planar formats, these are actually not supported within the
|
| /linux-5.19.10/drivers/staging/media/imx/ |
| D | imx-media-utils.c | 37 .planar = true,
42 .planar = true,
47 .planar = true,
52 .planar = true,
57 .planar = true,
551 if (cc->planar) in imx_media_mbus_fmt_to_pix_fmt()
565 pix->sizeimage = cc->planar ? ((stride * pix->height * cc->bpp) >> 3) : in imx_media_mbus_fmt_to_pix_fmt()
|
| /linux-5.19.10/drivers/gpu/ipu-v3/ |
| D | ipu-image-convert.c | 131 bool planar; /* planar format */ member
289 .planar = true,
295 .planar = true,
302 .planar = true,
309 .planar = true,
315 .planar = true,
605 if (fmt->planar) in tile_left_align()
641 fmt->planar && !fmt->uv_packed) ? in tile_width_align()
658 return (fmt->planar && !fmt->uv_packed) ? 8 * fmt->uv_width_dec : 8; in tile_height_align()
883 if (image->fmt->planar) { in calc_tile_dimensions()
[all …]
|
| /linux-5.19.10/drivers/staging/media/atomisp/pci/ |
| D | atomisp_common.h | 53 bool planar; member
|
| /linux-5.19.10/drivers/media/platform/marvell/ |
| D | mcam-core.c | 104 bool planar; member
111 .planar = false,
117 .planar = false,
123 .planar = true,
129 .planar = true,
135 .planar = false,
141 .planar = false,
147 .planar = false,
321 return f->planar; in mcam_fmt_is_planar()
|