Home
last modified time | relevance | path

Searched refs:VIDIOC_G_FMT (Results 1 – 25 of 32) sorted by relevance

12

/linux-5.19.10/Documentation/userspace-api/media/v4l/
Ddev-output.rst65 and call the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl with a pointer
75 of :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, and call the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`
77 parameters and finally return the actual parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`
80 Like :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` the :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl
87 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` and :ref:`VIDIOC_TRY_FMT <VI…
88 details. Video output devices must implement both the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`
89 and :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, even if :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ignores all
90 requests and always returns default parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does.
91 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` is optional.
Ddev-capture.rst68 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl with a pointer to this
78 of :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, and call the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`
80 parameters and finally return the actual parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`
83 Like :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` the :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl
90 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` and :ref:`VIDIOC_TRY_FMT <VI…
91 details. Video capture devices must implement both the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`
92 and :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, even if :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ignores all
93 requests and always returns default parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does.
94 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` is optional.
Dvidioc-g-fmt.rst7 ioctl VIDIOC_G_FMT, VIDIOC_S_FMT, VIDIOC_TRY_FMT
13 VIDIOC_G_FMT - VIDIOC_S_FMT - VIDIOC_TRY_FMT - Get or set the data format, try a format
18 .. c:macro:: VIDIOC_G_FMT
20 ``int ioctl(int fd, VIDIOC_G_FMT, struct v4l2_format *argp)``
50 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl with a pointer to this structure the driver fills
63 application. When the application calls the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl with
70 prepare for data exchange. Finally the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl returns
71 the current format parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does. Very simple,
74 application must implement the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and :ref:`VIDIOC_S_FMT <VIDIOC_G_…
76 EINVAL error code on a :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` attempt. When I/O is already in
[all …]
Dformat.rst26 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and
27 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctls. Additionally the
28 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl can be used to examine
34 The :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl is a major turning-point in the
37 change controls or modify other properties. The first :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`
53 When applications omit the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl its locking side
64 *may* support a switch using :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`.
67 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl. Implementation of …
68 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` is highly recommended but optional.
Ddev-osd.rst23 the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl.
123 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl. The driver fills the
130 substructure and call the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl.
132 the actual parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does. Like :ref:`VIDIOC_S_FMT <VIDIOC_G…
133 the :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl can be used to learn
135 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` this also works after the overlay has been enabled.
Dplanar-apis.rst47 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`, :ref:`VIDIOC_TRY_FMT <VIDIO…
Ddev-overlay.rst26 the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl.
111 (:ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`) or overlay
131 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl. The driver fills the
138 call the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl. The driver
140 parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does. Like :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`, the
141 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl can be used to learn
143 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` this also works after the overlay has been enabled.
152 (:ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`) may fail with an ``EBUSY`` error
200 contents after calling :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`
207 after calling :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` are undefined. When clip lists are
[all …]
Ddev-raw-vbi.rst32 applications must call the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl.
72 the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl with a pointer to this
81 of :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, and call the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`
95 VBI devices must implement both the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and
96 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, even if :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ignores all re…
97 and always returns default parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does.
98 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` is optional.
Dcrop.rst37 overlay) is negotiated with the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`
38 and :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctls.
42 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`
128 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl however shall not change
298 if (-1 == ioctl (fd, VIDIOC_G_FMT, &format)) {
299 perror ("VIDIOC_G_FMT");
Dio.rst25 initiating video overlay with the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`
35 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` and :ref:`VIDIOC_REQBUFS` would permit this to some
Dvidioc-enum-fmt.rst200 when calling the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl with
207 device when calling the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl with
214 when calling the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl with
221 when calling the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl with
228 device when calling the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl with
Dvidioc-g-fbuf.rst157 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, using the ``field``
280 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`) will be used. Only one
285 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`. If this flag is set for a
294 and negotiated with the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`
298 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, see :ref:`overlay`
313 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, see :ref:`overlay`
327 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, see :ref:`overlay`
Ddiff-v4l.rst124 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, respectively. The
166 were removed. Calling the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` or
167 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl with the desired
346 be selected with the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl.
427 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and
428 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`. They take a pointer to a struct
481 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl.
500 negotiation ioctls :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and
501 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`. They take a pointer to a struct
526 with the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl. When no
Ddev-sliced-vbi.rst25 calling the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl as defined
61 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl when the number of VBI
71 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl fills the ``fmt.sliced``
77 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl with a pointer to the
91 The :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl modifies the parameters
125 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` or
126 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>`, the ``service_lines``
272 a side effect). The :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl may
356 been negotiated with the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` or
357 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl. When the line numbers are
Dlibv4l-introduction.rst92 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>`,
93 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`,
94 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`,
Dvidioc-create-bufs.rst50 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` or
51 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctls to ensure that the
Dpixfmt.rst14 the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl. (The explanations here
Dfield-order.rst56 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl. If this is not desired it
82 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` or
83 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>`. struct
Dhist-v4l2.rst138 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and
139 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl taking a union and a
244 compatibility* as the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and
245 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctls may fail now if the
277 error codes with the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl was
415 9. The :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl was added to
417 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`, but without the overhead of
422 image format negotiations are now possible with ``VIDIOC_G_FMT``,
879 :ref:`VIDIOC_G/S/TRY_FMT <VIDIOC_G_FMT>` ioctls, which take a
Dselection-api-configuration.rst53 the image size set by :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`.
93 specified using :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl.
Dvidioc-g-crop.rst64 :ref:`VIDIOC_G_CROP <VIDIOC_G_CROP>` and :ref:`VIDIOC_G_FMT`. When the
Dvidioc-g-sliced-vbi-cap.rst99 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl as described in
Dcapture.c.rst504 if (-1 == xioctl(fd, VIDIOC_G_FMT, &fmt))
505 errno_exit("VIDIOC_G_FMT");
Ddev-decoder.rst372 calling :c:func:`VIDIOC_G_FMT`, :c:func:`VIDIOC_S_FMT`,
405 1. Call :c:func:`VIDIOC_G_FMT` on the ``CAPTURE`` queue to get format for the
450 returned by :c:func:`VIDIOC_G_FMT` on ``CAPTURE``.
519 selected/suggested by the decoder in :c:func:`VIDIOC_G_FMT`.
531 what was returned with :c:func:`VIDIOC_G_FMT`, but it may be different
559 returned by :c:func:`VIDIOC_G_FMT` on ``CAPTURE``.
691 * query the ``CAPTURE`` format using :c:func:`VIDIOC_G_FMT` and save it
/linux-5.19.10/drivers/media/v4l2-core/
Dv4l2-dev.c617 __set_bit(_IOC_NR(VIDIOC_G_FMT), valid_ioctls); in determine_valid_ioctls()
656 SET_VALID_IOCTL(ops, VIDIOC_G_FMT, vidioc_g_fmt_meta_cap); in determine_valid_ioctls()
662 SET_VALID_IOCTL(ops, VIDIOC_G_FMT, vidioc_g_fmt_meta_out); in determine_valid_ioctls()
672 __set_bit(_IOC_NR(VIDIOC_G_FMT), valid_ioctls); in determine_valid_ioctls()
687 SET_VALID_IOCTL(ops, VIDIOC_G_FMT, vidioc_g_fmt_vid_cap); in determine_valid_ioctls()
700 SET_VALID_IOCTL(ops, VIDIOC_G_FMT, vidioc_g_fmt_sdr_cap); in determine_valid_ioctls()
706 SET_VALID_IOCTL(ops, VIDIOC_G_FMT, vidioc_g_fmt_sdr_out); in determine_valid_ioctls()

12