Lines Matching +full:frame +full:- +full:buffer

4 .. Foundation, with no Invariant Sections, no Front-Cover Texts
5 .. and no Back-Cover Texts. A copy of the license is included at
6 .. Documentation/media/uapi/fdl-appendix.rst.
8 .. TODO: replace it to GFDL-1.1-or-later WITH no-invariant-sections
10 .. _planar-apis:
13 Single- and multi-planar APIs
16 Some devices require data for each input or output video frame to be
17 placed in discontiguous memory buffers. In such cases, one video frame
19 per "plane". A plane is a sub-buffer of the current frame. For examples
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
30 buffer types are suffixed with an ``_MPLANE`` string. For a list 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
42 in multi-planar API structures), while the single-planar API cannot
43 handle multi-planar formats.
46 Calls that distinguish between single and multi-planar APIs
50     Two additional multi-planar capabilities are added. They can be set
51     together with non-multi-planar ones for devices that handle both
52     single- and multi-planar formats.
55     New structures for describing multi-planar formats are added: struct
58     Drivers may define new multi-planar formats, which have distinct
59     FourCC codes from the existing single-planar ones.
68     Will allocate multi-planar buffers as requested.