Searched full:format (Results 1 – 25 of 916) sorted by relevance
12345678910>>...37
| /Documentation/userspace-api/media/v4l/ |
| D | pixfmt-reserved.rst | 6 Reserved Format Identifiers
11 register your own format, send an e-mail to the linux-media mailing list
14 format with other developers add a link to your documentation and send a
16 you think your format should be listed in a standard format section
41 - Compressed format of the ET61X251 driver.
46 - 8 bit RGB format used by the BTTV driver.
51 - YUV 4:2:0 format used by the IVTV driver.
53 The format is documented in the kernel sources in the file
59 - YUV format used by the gspca cpia1 driver.
64 - JPEG-Light format (Pegasus Lossless JPEG) used in Divio webcams NW
[all …]
|
| D | vidioc-subdev-g-fmt.rst | 13 VIDIOC_SUBDEV_G_FMT - VIDIOC_SUBDEV_S_FMT - Get or set the data format on a subdev pad
38 These ioctls are used to negotiate the frame format at specific subdev
41 To retrieve the current format applications set the ``pad`` field of a
46 driver fills the members of the ``format`` field.
48 To change the current format applications set both the ``pad`` and
49 ``which`` fields and all members of the ``format`` field. When they call
51 driver verifies the requested format, adjusts it based on the hardware
54 format as would be returned by a ``VIDIOC_SUBDEV_G_FMT`` call.
62 For instance, to try a format at the output pad of a sub-device,
63 applications would first set the try format at the sub-device input with
[all …]
|
| D | dev-subdev.rst | 83 need to expose low-level format configuration to user space. Generic
89 For the purpose of this section, the term *format* means the
90 combination of media bus data format, frame width and frame height.
93 devices using the format and
96 to the requested format at the pipeline input and/or output.
111 Image Format Negotiation on Pipelines
124 can expose pad-level image format configuration to applications. When
136 Pad-level image format configuration support can be tested by calling
138 0. If the driver returns an ``EINVAL`` error code pad-level format
142 Format Negotiation
[all …]
|
| D | vidioc-create-bufs.rst | 47 The ``format`` field specifies the image format that the buffers must be
52 requested format is supported by the driver. Based on the format's
59 defined by the ``format.pix.sizeimage`` field (or the corresponding
60 fields for other format types). Usually if the ``format.pix.sizeimage``
61 field is less than the minimum required for the given format, then an
90 ``format.type``. If those are invalid -1 is returned and errno is
100 - ``format``
113 ``V4L2_MEMORY_MMAP`` and ``format.type`` to the buffer type.
131 The buffer type (``format.type`` field), requested I/O method
132 (``memory``) or format (``format`` field) is not valid.
|
| D | dev-stateless-decoder.rst | 42 irrespective of the format currently set on the ``CAPTURE`` queue.
51 * The driver must return only the formats supported for the format currently
54 * Depending on the currently set ``OUTPUT`` format, the set of supported raw
62 resolutions for a given format, passing desired pixel format in
65 4. Supported profiles and levels for the current ``OUTPUT`` format, if
72 1. Set the coded format on the ``OUTPUT`` queue via :c:func:`VIDIOC_S_FMT`.
80 a coded pixel format.
90 Changing the ``OUTPUT`` format may change the currently set ``CAPTURE``
91 format. The driver will derive a new ``CAPTURE`` format from the
92 ``OUTPUT`` format being set, including resolution, colorimetry
[all …]
|
| D | dev-encoder.rst | 91 format set on ``OUTPUT``.
96 * Only the formats supported for the format currently active on ``CAPTURE``
99 * In order to enumerate raw formats supported by a given coded format,
100 the client must first set that coded format on ``CAPTURE`` and then
104 resolutions for a given format, passing the desired pixel format in
108 format will include all possible coded resolutions supported by the
109 encoder for the given coded pixel format.
111 * Values returned by :c:func:`VIDIOC_ENUM_FRAMESIZES` for a raw pixel format
113 encoder for the given raw pixel format and coded format currently set on
117 frame intervals for a given format and resolution, passing the desired pixel
[all …]
|
| D | dev-meta.rst | 35 Data Format Negotiation
38 The metadata device uses the :ref:`format` ioctls to select the capture format.
39 The metadata buffer content format is bound to that selected format. In addition
40 to the basic :ref:`format` ioctls, the :c:func:`VIDIOC_ENUM_FMT` ioctl must be
43 To use the :ref:`format` ioctls applications set the ``type`` field of the
61 - The data format, set by the application. This is a little endian
|
| D | dev-decoder.rst | 60 coded format
61 encoded/compressed video bytestream format (e.g. H.264, VP8, etc.); see
62 also: raw format.
77 coded format includes a feature of frame reordering; for decoders,
119 raw format
120 uncompressed format containing raw pixel data (e.g. YUV, RGB formats).
214 format set on ``CAPTURE``.
216 about the decoder's capabilities with respect to each coded format.
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,
[all …]
|
| D | vidioc-g-fmt.rst | 13 VIDIOC_G_FMT - VIDIOC_S_FMT - VIDIOC_TRY_FMT - Get or set the data format, try a format
42 These ioctls are used to negotiate the format of data (typically image
43 format) exchanged between driver and application.
58 To change the current format parameters applications initialize the
71 the current format parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does. Very simple,
87 The format as returned by :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` must be identical to what
105 - Definition of an image format, see :ref:`pixfmt`, used by video
109 - Definition of an image format, see :ref:`pixfmt`, used by video
127 - Definition of a data format, see :ref:`pixfmt`, used by SDR
131 - Definition of a metadata format, see :ref:`meta-formats`, used by
[all …]
|
| D | pixfmt-compressed.rst | 30 - MPEG multiplexed stream. The actual format is determined by
59 This format is adapted for stateless video decoders that implement an
72 with this pixel format. The output buffer must contain the
76 The syntax for this format is documented in :ref:`h264`, section
82 This format is not yet part of the public kernel API and it
113 This format is adapted for stateless video decoders that implement a
121 this pixel format. The output buffer must contain the appropriate number
156 This format is adapted for stateless video decoders that implement a
162 this pixel format. The output buffer must contain the appropriate number
168 This format is not yet part of the public kernel API and it
[all …]
|
| D | vidioc-subdev-enum-mbus-code.rst | 63 - Number of the format in the enumeration, set by the application.
66 - The media bus format code, as defined in
67 :ref:`v4l2-mbus-format`.
70 - Media bus format codes to be enumerated, from enum
71 :ref:`v4l2_subdev_format_whence <v4l2-subdev-format-whence>`.
97 See :ref:`v4l2-mbus-format` on how to do this.
104 See :ref:`v4l2-mbus-format` on how to do this.
111 See :ref:`v4l2-mbus-format` on how to do this.
118 See :ref:`v4l2-mbus-format` on how to do this.
125 See :ref:`v4l2-mbus-format` on how to do this.
|
| D | dev-sdr.rst | 59 Data Format Negotiation
62 The SDR device uses the :ref:`format` ioctls to select the
63 capture and output format. Both the sampling resolution and the data
64 streaming format are bound to that selectable format. In addition to the
65 basic :ref:`format` ioctls, the
69 To use the :ref:`format` ioctls applications set the ``type``
76 Content of the ``pixelformat`` is V4L2 FourCC code of the data format.
92 - The data format or type of compression, set by the application.
|
| D | pixfmt-v4l2-mplane.rst | 4 Multi-planar format structures
8 and layout for each of the planes in a multi-planar format. The
12 describing all planes of that format.
74 - The pixel format. Both single- and multi-planar four character
86 - An array of structures describing format of each plane this pixel
87 format consists of. The number of valid entries in this array has
91 - Number of planes (i.e. separate memory buffers) for this format
95 - Flags set by the application or driver, see :ref:`format-flags`.
|
| /Documentation/translations/it_IT/process/ |
| D | clang-format.rst | 3 :Original: :ref:`Documentation/process/clang-format.rst <clangformat>`
8 clang-format
10 ``clang-format`` è uno strumento per formattare codice C/C++/... secondo
14 ``clang-format`` può essere usato per diversi fini:
28 Il suo file di configurazione è ``.clang-format`` e si trova nella cartella
35 potete sovrascriverle scrivendole in un altro file ``.clang-format`` in
39 Linux più popolari. Cercate ``clang-format`` nel vostro repositorio.
64 clang-format -i kernel/*.[ch]
70 le nuove funzionalità/versioni di ``clang-format``.
72 ``clang-format`` è in grado di leggere diversi diff unificati, quindi
[all …]
|
| /Documentation/process/ |
| D | clang-format.rst | 3 clang-format
6 ``clang-format`` is a tool to format C/C++/... code according to
10 ``clang-format`` can be used for several purposes:
22 Its configuration file is ``.clang-format`` in the root of the kernel tree.
28 another ``.clang-format`` file in a subfolder.
31 Linux distributions for a long time. Search for ``clang-format`` in
55 clang-format -i kernel/*.[ch]
61 ``clang-format`` features/versions.
63 ``clang-format`` also supports reading unified diffs, so you can review
68 To avoid ``clang-format`` formatting some portion of a file, you can do::
[all …]
|
| /Documentation/userspace-api/media/dvb/ |
| D | video-set-format.rst | 22 ``int ioctl(fd, VIDEO_SET_FORMAT, video_format_t format)``
45 - video_format_t format
47 - video format of TV as defined in section ??.
52 This ioctl sets the screen format (aspect ratio) of the connected output
61 VIDEO_FORMAT_4_3, /* Select 4:3 format */
62 VIDEO_FORMAT_16_9, /* Select 16:9 format. */
82 - format is not a valid video format.
|
| D | video_types.rst | 10 .. _video-format-t:
21 VIDEO_FORMAT_4_3, /* Select 4:3 format */
22 VIDEO_FORMAT_16_9, /* Select 16:9 format. */
30 about the display format of the current video stream.
38 In case the display format of the video stream and of the display
47 VIDEO_PAN_SCAN, /* use pan and scan format */
48 VIDEO_LETTER_BOX, /* use letterbox format */
49 VIDEO_CENTER_CUT_OUT /* use center cut out format */
124 __u32 format;
202 case the source video format is not the same as the format of the output
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-mei | 7 Format: mei:<mei device name>:<device uuid>:<protocol version>
14 Format: string
21 Format: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
28 Format: %d
35 Format: %d
42 Format: %d
49 Format: %d
56 Format: %d
|
| D | sysfs-firmware-turris-mox-rwtm | 6 Format: %i
13 Format: %pM
22 Format: string
30 Format: %i
37 Format: %016X
|
| D | sysfs-class-iommu-intel-iommu | 7 Format: %llx. This allows association of a sysfs
16 of this DRHD unit. Format: %llx.
24 value of this DRHD unit. Format: %llx.
32 VT-d VER_REG. Format: %d:%d, major:minor
|
| D | sysfs-fs-xfs | 7 log. The LSN is exported in "cycle:basic block" format.
16 log. The LSN is exported in "cycle:basic block" format.
26 "cycle:bytes" format.
38 "cycle:bytes" format.
|
| /Documentation/security/ |
| D | IMA-templates.rst | 20 the measurements list would include the code for handling a new format
33 specifying the template format (a string of field identifiers separated
36 by translating the format into an array of template fields structures taken
62 descriptors by adding their identifier to the format string
69 algorithm (field format: [<hash algo>:]digest, where the digest
80 - "ima": its format is ``d|n``;
81 - "ima-ng" (default): its format is ``d-ng|n-ng``;
82 - "ima-sig": its format is ``d-ng|n-ng|sig``;
83 - "ima-buf": its format is ``d-ng|n-ng|buf``;
84 - "ima-modsig": its format is ``d-ng|n-ng|sig|d-modsig|modsig``;
[all …]
|
| /Documentation/fb/ |
| D | api.rst | 38 The driver supports the four character code (FOURCC) based format setting API.
47 to be aware of the pixel storage format in order to write image data to the
48 frame buffer memory in the format expected by the hardware.
88 Macropixels are stored in memory as described by the format FOURCC identifier
141 Pixels are encoded and interpreted as described by the format FOURCC
153 about the frame buffer device and the current format. Those information can't
155 application modifies the format::
179 about a frame buffer device, its current format and video mode, as well as
198 __u32 nonstd; /* != 0 Non standard pixel format */
231 4. Format configuration
[all …]
|
| /Documentation/devicetree/bindings/media/xilinx/ |
| D | video.txt | 20 - xlnx,video-format: This property represents a video format transmitted on an
22 Video IP and System Design Guide" [UG934]. How the format relates to the IP
25 - xlnx,video-width: This property qualifies the video format with the sample
29 - xlnx,cfa-pattern: When the video format is set to Mono/Sensor, this property
|
| /Documentation/driver-api/nvdimm/ |
| D | security.rst | 51 A nvdimm encrypted-key of format enc32 has the description format of:
55 encrypted-keys of enc32 format. TPM usage with a master trusted key is
75 is injected with the description format described from earlier in this
77 the format:
90 The security disable command format is:
98 The command format for doing a secure erase is:
106 The command format for doing an overwrite is:
120 The command format for doing a master update is:
131 The command format for doing a master erase is:
|
12345678910>>...37