Home
last modified time | relevance | path

Searched refs:planar (Results 1 – 25 of 78) sorted by relevance

1234

/OK3568_Linux_fs/kernel/Documentation/userspace-api/media/v4l/
H A Dplanar-apis.rst6 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 …]
H A Dpixfmt.rst12 single-planar API, while the latter is used with the multi-planar
13 version (see :ref:`planar-apis`). Image formats are negotiated with
H A Dvidioc-querycap.rst146 - The device supports the single-planar API through the
150 - The device supports the :ref:`multi-planar API <planar-apis>`
154 - The device supports the single-planar API through the
158 - The device supports the :ref:`multi-planar API <planar-apis>`
162 - The device supports the single-planar API through the Video
166 - The device supports the :ref:`multi-planar API <planar-apis>`
H A Dvidioc-querybuf.rst47 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,
H A Dpixfmt-nv16m.rst18 This is a multi-planar, two-plane version of the YUV 4:2:2 format. The
32 used only in drivers and applications that support the multi-planar API,
33 described in :ref:`planar-apis`.
H A Dpixfmt-yuv422m.rst19 This is a multi-planar format, as opposed to a packed format. The three
38 used only in drivers and applications that support the multi-planar API,
39 described in :ref:`planar-apis`.
H A Dpixfmt-yuv420m.rst19 This is a multi-planar format, as opposed to a packed format. The three
39 used only in drivers and applications that support the multi-planar API,
40 described in :ref:`planar-apis`.
H A Dpixfmt-yuv444m.rst19 This is a multi-planar format, as opposed to a packed format. The three
34 used only in drivers and applications that support the multi-planar API,
35 described in :ref:`planar-apis`.
H A Dpixfmt-nv12m.rst21 This is a multi-planar, two-plane version of the YUV 4:2:0 format. The
40 applications that support the multi-planar API, described in
41 :ref:`planar-apis`.
H A Dvidioc-expbuf.rst48 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.
H A Dfunc-munmap.rst36 single-planar API and in the struct
38 multi-planar API.
H A Dfunc-mmap.rst39 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.
H A Dvidioc-qbuf.rst58 :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
H A Dpixfmt-intro.rst46 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*".
H A Dpixfmt-v4l2-mplane.rst4 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
H A Dmmap.rst41 :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
H A Dpixfmt-yuv411p.rst17 This format is not commonly used. This is a planar format similar to the
18 4:2:2 planar format except with half as many chroma. The three
H A Dpixfmt-reserved.rst185 YUV420 planar in blocks of 256 pixels.
207 - Two-planar format used by Samsung S5C73MX cameras. The first plane
240 - Compressed two-planar YVU420 format used by Mediatek MT8173.
249 - Two-planar NV12-based format used by the video engine found on Allwinner
/OK3568_Linux_fs/kernel/drivers/gpu/drm/tegra/
H A Dplane.c346 bool tegra_plane_format_is_yuv(unsigned int format, bool *planar) in tegra_plane_format_is_yuv() argument
351 if (planar) in tegra_plane_format_is_yuv()
352 *planar = false; in tegra_plane_format_is_yuv()
364 if (planar) in tegra_plane_format_is_yuv()
365 *planar = true; in tegra_plane_format_is_yuv()
370 if (planar) in tegra_plane_format_is_yuv()
371 *planar = false; in tegra_plane_format_is_yuv()
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/media/i2c/
H A Dtda1997x.txt8 - 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]
/OK3568_Linux_fs/kernel/Documentation/fb/
H A Dpxafb.rst110 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
/OK3568_Linux_fs/kernel/drivers/gpu/ipu-v3/
H A Dipu-image-convert.c131 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 …]
/OK3568_Linux_fs/external/camera_engine_rkaiq/rkaiq/xcore/
H A Dvideo_buffer.cpp88 VideoBufferPlanarInfo &planar, const uint32_t index) const in get_planar_info() argument
91 XCamVideoBufferPlanarInfo *planar_info = &planar; in get_planar_info()
/OK3568_Linux_fs/kernel/drivers/staging/media/imx/
H A Dimx-media-utils.c37 .planar = true,
42 .planar = true,
47 .planar = true,
52 .planar = true,
57 .planar = true,
530 if (cc->planar) in imx_media_mbus_fmt_to_pix_fmt()
544 pix->sizeimage = cc->planar ? ((stride * pix->height * cc->bpp) >> 3) : in imx_media_mbus_fmt_to_pix_fmt()
/OK3568_Linux_fs/yocto/meta-openembedded/meta-multimedia/recipes-multimedia/fluidsynth/fluidsynth/
H A D0002-fluid_synth_nwrite_float-Allow-zero-pointer-for-left.patch31 - * @param left Array of float buffers to store left channel of planar audio (as many as \c synth.a…
32 - * @param right Array of float buffers to store right channel of planar audio (size: dito)
35 + * @param left Array of float buffers to store left channel of planar audio (as many as \c synth.a…
36 + * @param right Array of float buffers to store right channel of planar audio (size: dito). Since …

1234