Lines Matching refs:planar

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
35 in multi-planar API structures), while the single-planar API cannot
36 handle multi-planar formats.
39 Calls that distinguish between single and multi-planar APIs
43     Two additional multi-planar capabilities are added. They can be set
44     together with non-multi-planar ones for devices that handle both
45     single- and multi-planar formats.
48     New structures for describing multi-planar formats are added: struct
51     Drivers may define new multi-planar formats, which have distinct
52     FourCC codes from the existing single-planar ones.
61     Will allocate multi-planar buffers as requested.