Home
last modified time | relevance | path

Searched full:formats (Results 1 – 25 of 176) sorted by relevance

12345678

/Documentation/media/uapi/v4l/
Dpixfmt-intro.rst11 Standard Image Formats
15 necessary to have standard image data formats which both sides will
16 interpret the same way. V4L2 includes several such formats, and this
18 image data formats in V4L2.
20 V4L2 drivers are not limited to these formats, however. Driver-specific
21 formats are possible. In that case the application may depend on a codec
22 to convert images to one of the standard formats when needed. But the
29 Even so, ultimately, some standard formats are needed, so the V4L2
31 formats.
33 The V4L2 standard formats are mainly uncompressed formats. The pixels
[all …]
Dpixfmt.rst13 Image Formats
20 version (see :ref:`planar-apis`). Image formats are negotiated with
22 focus on video capturing and output, for overlay frame buffer formats
35 yuv-formats
36 hsv-formats
37 depth-formats
39 sdr-formats
40 tch-formats
41 meta-formats
Dvidioc-g-dv-timings.rst61 the formats in the :ref:`cea861` and :ref:`vesadmt` standards. If
100 formats the height of the active video in each field is
126 - Vertical front porch in lines. For interlaced formats this refers
130 - Vertical sync length in lines. For interlaced formats this refers
134 - Vertical back porch in lines. For interlaced formats this refers
139 interlaced field formats. Must be 0 for progressive formats.
143 interlaced field formats. Must be 0 for progressive formats.
147 interlaced field formats. Must be 0 for progressive formats.
259 - CEA-861 specific: set for CEA-861 formats with a framerate that is
260 a multiple of six. These formats can be optionally played at 1 /
[all …]
Ddev-subdev.rst37 - negotiate image formats on individual pads
77 .. _pad-level-formats:
79 Pad-level Formats
84 Pad-level formats are only applicable to very complex devices that
94 Image formats are typically negotiated on video capture and output
122 configured differently. Applications need to configure the formats at
130 negotiate formats on a per-pad basis.
134 formats. The pipeline is checked for formats mismatch at
147 Acceptable formats on pads can (and usually do) depend on a number of
148 external parameters, such as formats on other pads, active links, or
[all …]
Dplanar-apis.rst20 of such formats see :ref:`pixfmt`.
35 Multi-planar formats
38 Multi-planar API introduces new multi-planar formats. Those formats use
41 can handle all single-planar formats as well (as long as they are passed
43 handle multi-planar formats.
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
Dformat.rst13 Data Formats
22 within one kind many different formats are possible, in particular there is an
23 abundance of image formats. Although drivers must provide a default and
31 A single mechanism exists to negotiate all data formats using the
37 format. The data formats supported by the V4L2 API are covered in the
39 image formats see :ref:`pixfmt`.
82 enumerate all image formats supported by video capture, overlay or
90 Drivers are not supposed to convert image formats in kernel space.
91 They must enumerate only formats directly supported by the hardware.
96 Enumerating formats an application has no a-priori knowledge of
Dvidioc-subdev-enum-mbus-code.rst19 VIDIOC_SUBDEV_ENUM_MBUS_CODE - Enumerate media bus formats
42 To enumerate media bus formats available at a given sub-device pad
49 formats are enumerable by beginning at index zero and incrementing by
52 Available media bus formats may depend on the current 'try' formats at
55 information about the try formats.
Dtch-formats.rst10 .. _tch-formats:
13 Touch Formats
16 These formats are used for :ref:`touch` interface only.
Dsdr-formats.rst10 .. _sdr-formats:
13 SDR Formats
16 These formats are used for :ref:`SDR <sdr>` interface only.
Dhsv-formats.rst10 .. _hsv-formats:
13 HSV Formats
16 These formats store the color information of the image
Dmeta-formats.rst10 .. _meta-formats:
13 Metadata Formats
16 These formats are used for the :ref:`metadata` interface only.
Dvidioc-enum-fmt.rst19 VIDIOC_ENUM_FMT - Enumerate image formats
42 To enumerate image formats applications initialize the ``type`` and
46 formats are enumerable by beginning at index zero and incrementing by
52 formats may be different.
99 Several image formats are already defined by this specification in
137 formats only. This flag is valid for stateful decoders only.
145 compressed formats only. It is also only applies to stateful codecs.
Dpixfmt-bayer.rst13 Raw Bayer Formats
19 The raw Bayer formats are used by image sensors before much if any processing is
20 performed on the image. The formats contain green, red and blue components, with
Dpixfmt-v4l2.rst34 for interlaced formats).
37 planar formats the ``width`` and ``height`` applies to the largest
43 For compressed formats that contain the resolution information encoded
52 RGB formats in :ref:`pixfmt-rgb`, YUV formats in
53 :ref:`yuv-formats`, and reserved codes in
54 :ref:`reserved-formats`
90 For compressed formats the ``bytesperline`` value makes no sense.
Dvidioc-subdev-g-fmt.rst64 to ``V4L2_SUBDEV_FORMAT_TRY``. When set, 'try' formats are not applied
65 to the device by the driver, but are changed exactly as active formats
76 Try formats do not depend on active formats, but can depend on the
125 - Try formats, used for querying device capabilities.
128 - Active formats, applied to the hardware.
Ddepth-formats.rst10 .. _depth-formats:
13 Depth Formats
Ddev-decoder.rst105 a processing unit in image and video compression formats based on linear
120 uncompressed format containing raw pixel data (e.g. YUV, RGB formats).
210 1. To enumerate the set of coded formats supported by the decoder, the
213 * The full set of supported formats will be returned, regardless of the
220 2. To enumerate the set of supported raw formats, the client may call
223 * Only the formats supported for the format currently active on ``OUTPUT``
226 * In order to enumerate raw formats supported by a given coded format,
228 enumerate formats on ``CAPTURE``.
281 However, for coded formats that include stream resolution information,
348 4. **This step only applies to coded formats that contain resolution information
[all …]
Dpixfmt-srggb10alaw8.rst22 10-bit Bayer formats compressed to 8 bits
28 These four pixel formats are raw sRGB / Bayer formats with 10 bits per
Ddev-touch.rst57 The formats supported by touch devices are documented in
58 :ref:`Touch Formats <tch-formats>`.
Dpixfmt-srggb10.rst23 10-bit Bayer formats expanded to 16 bits
29 These four pixel formats are raw sRGB / Bayer formats with 10 bits per
35 these formats:
Dpixfmt-packed-yuv.rst13 Packed YUV formats
19 Similar to the packed RGB formats these formats store the Y, Cb and Cr
29 .. _packed-yuv-formats:
33 .. flat-table:: Packed YUV Image Formats
376 :ref:`Video Output Overlay <osd>` for the formats Y444, YUV555 and
377 YUV4. However, for formats AYUV32 and VUYA32, the alpha component is
379 and applications. And, the formats XYUV32 and VUYX32 contain undefined
/Documentation/devicetree/bindings/media/
Drenesas,fdp1.txt6 YCbCr/YUV formats and RGB formats. Only YCbCr/YUV formats are supported as
/Documentation/sound/designs/
Dcompress-offload.rst39 - separation between byte counts and time. Compressed formats may have
47 - Handling of multiple formats. PCM data only requires a specification
49 contrast, compressed data comes in a variety of formats. Audio DSPs
54 - Focus on main formats. This API provides support for the most
55 popular formats used for audio and video capture and playback. It is
56 likely that as audio compression technology advances, new formats
63 formats.
104 This routine returns the list of audio formats supported. Querying the
115 that a specific combination of profiles/channels/formats may not be
145 - Addition of FLAC and IEC formats
/Documentation/fb/
Dapi.rst39 When supported, formats are configured using a FOURCC instead of manually
46 Pixels are stored in memory in hardware-dependent formats. Applications need
50 Formats are described by frame buffer types and visuals. Some visuals require
240 for applications when using RGB and grayscale formats, as well as legacy
241 non-standard formats.
247 - For grayscale formats, applications set the grayscale field to one. The red,
252 - For pseudocolor formats, applications set the grayscale field to zero. The
257 - For truecolor and directcolor formats, applications set the grayscale field
284 formats. Drivers are also encouraged to implement the FOURCC-based API for RGB
285 and grayscale formats.
[all …]
/Documentation/gpu/bridge/
Ddw-hdmi.rst11 Supported Input Formats and Encodings
15 :doc: Supported input formats and encodings

12345678