| /Linux-v5.4/Documentation/media/uapi/v4l/ |
| D | planar-apis.rst | 13 Single- and multi-planar APIs
22 Initially, V4L2 API did not support multi-planar buffers and a set of
24 constitute what is being referred to as the "multi-planar API".
27 depending on whether single- or multi-planar API is being used. An
29 corresponding buffer type to its ioctl calls. Multi-planar versions of
31 available multi-planar buffer types see enum
35 Multi-planar formats
38 Multi-planar API introduces new multi-planar formats. Those formats use
40 the multi-planar API and a multi-planar format. Multi-planar API calls
41 can handle all single-planar formats as well (as long as they are passed
[all …]
|
| D | pixfmt.rst | 19 single-planar API, while the latter is used with the multi-planar
20 version (see :ref:`planar-apis`). Image formats are negotiated with
|
| D | vidioc-querycap.rst | 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
168 - The device supports the :ref:`multi-planar API <planar-apis>`
172 - The device supports the single-planar API through the Video
176 - The device supports the :ref:`multi-planar API <planar-apis>`
|
| D | vidioc-querybuf.rst | 55 using the :ref:`multi-planar API <planar-apis>`, the ``m.planes``
65 set to the current I/O method. For the single-planar API, the
67 device memory, the ``length`` field its size. For the multi-planar API,
|
| D | pixfmt-nv16m.rst | 25 This is a multi-planar, two-plane version of the YUV 4:2:2 format. The
39 used only in drivers and applications that support the multi-planar API,
40 described in :ref:`planar-apis`.
|
| D | pixfmt-yuv422m.rst | 26 This is a multi-planar format, as opposed to a packed format. The three
45 used only in drivers and applications that support the multi-planar API,
46 described in :ref:`planar-apis`.
|
| D | pixfmt-yuv444m.rst | 26 This is a multi-planar format, as opposed to a packed format. The three
41 used only in drivers and applications that support the multi-planar API,
42 described in :ref:`planar-apis`.
|
| D | pixfmt-yuv420m.rst | 26 This is a multi-planar format, as opposed to a packed format. The three
46 used only in drivers and applications that support the multi-planar API,
47 described in :ref:`planar-apis`.
|
| D | pixfmt-nv12m.rst | 28 This is a multi-planar, two-plane version of the YUV 4:2:0 format. The
47 applications that support the multi-planar API, described in
48 :ref:`planar-apis`.
|
| D | func-munmap.rst | 45 single-planar API and in the struct
47 multi-planar API.
|
| D | vidioc-expbuf.rst | 56 one. For the multi-planar API, applications set the ``plane`` field to
59 the single-planar API, applications must set ``plane`` to zero.
63 case of multi-planar API, every plane is exported separately using
149 - Index of the plane to be exported when using the multi-planar API.
|
| D | func-mmap.rst | 48 single-planar API, and the same value as returned by the driver in
50 the multi-planar API.
103 the single-planar API, and the same value as returned by the driver
105 ``mem_offset`` field for the multi-planar API.
|
| D | pixfmt-intro.rst | 53 and are referred to as "multi-planar formats". For example, a
57 in the 2-planar version or with each component in its own buffer in the
58 3-planar case. Those sub-buffers are referred to as "*planes*".
|
| D | vidioc-qbuf.rst | 65 :ref:`multi-planar API <planar-apis>`, the ``m.planes`` field must
80 multi-planar API is used, ``m.userptr`` and ``length`` members of the
94 file descriptor associated with a DMABUF buffer. When the multi-planar
139 buffer might be corrupted. When using the multi-planar API, the planes
146 and the value is only for the application convenience. When the multi-planar
|
| D | pixfmt-v4l2-mplane.rst | 11 Multi-planar format structures
15 and layout for each of the planes in a multi-planar format. The
81 - The pixel format. Both single- and multi-planar four character
|
| D | pixfmt-yuv411p.rst | 24 This format is not commonly used. This is a planar format similar to the
25 4:2:2 planar format except with half as many chroma. The three
|
| D | mmap.rst | 47 :ref:`VIDIOC_QUERYBUF` ioctl. In the single-planar
51 multi-planar API, struct :c:type:`v4l2_buffer` contains an
54 multi-planar API, every plane of every buffer has to be mapped
62 Example: Mapping buffers in the single-planar API
133 Example: Mapping buffers in the multi-planar API
181 /* length in struct v4l2_buffer in multi-planar API stores the size
|
| D | pixfmt-reserved.rst | 193 YUV420 planar in blocks of 256 pixels.
215 - Two-planar format used by Samsung S5C73MX cameras. The first plane
248 - Compressed two-planar YVU420 format used by Mediatek MT8173.
257 - Two-planar NV12-based format used by the video engine found on Allwinner
|
| /Linux-v5.4/drivers/gpu/drm/tegra/ |
| D | plane.c | 229 bool tegra_plane_format_is_yuv(unsigned int format, bool *planar) in tegra_plane_format_is_yuv() argument
234 if (planar) in tegra_plane_format_is_yuv()
235 *planar = false; in tegra_plane_format_is_yuv()
247 if (planar) in tegra_plane_format_is_yuv()
248 *planar = true; in tegra_plane_format_is_yuv()
253 if (planar) in tegra_plane_format_is_yuv()
254 *planar = false; in tegra_plane_format_is_yuv()
|
| D | plane.h | 68 bool tegra_plane_format_is_yuv(unsigned int format, bool *planar);
|
| /Linux-v5.4/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-v5.4/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-v5.4/drivers/gpu/ipu-v3/ |
| D | ipu-image-convert.c | 131 bool planar; /* planar format */ member
273 .planar = true,
279 .planar = true,
286 .planar = true,
293 .planar = true,
299 .planar = true,
589 if (fmt->planar) in tile_left_align()
625 fmt->planar && !fmt->uv_packed) ? in tile_width_align()
642 return (fmt->planar && !fmt->uv_packed) ? 8 * fmt->uv_width_dec : 8; in tile_height_align()
867 if (image->fmt->planar) { in calc_tile_dimensions()
[all …]
|
| /Linux-v5.4/drivers/staging/media/imx/ |
| D | imx-media-utils.c | 43 .planar = true,
48 .planar = true,
53 .planar = true,
58 .planar = true,
63 .planar = true,
605 if (cc->planar) in imx_media_mbus_fmt_to_pix_fmt()
619 pix->sizeimage = cc->planar ? ((stride * pix->height * cc->bpp) >> 3) : in imx_media_mbus_fmt_to_pix_fmt()
|
| /Linux-v5.4/drivers/media/platform/marvell-ccic/ |
| D | mcam-core.c | 103 bool planar; member
110 .planar = false,
116 .planar = false,
122 .planar = true,
128 .planar = true,
134 .planar = false,
140 .planar = false,
146 .planar = false,
320 return f->planar; in mcam_fmt_is_planar()
|
