Home
last modified time | relevance | path

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

12

/Linux-v5.4/Documentation/media/uapi/v4l/
Ddev-output.rst74 and call the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl with a pointer
84 of :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, and call the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`
86 parameters and finally return the actual parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`
89 Like :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` the :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl
96 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` and :ref:`VIDIOC_TRY_FMT <VI…
97 details. Video output devices must implement both the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`
98 and :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, even if :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ignores all
99 requests and always returns default parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does.
100 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` is optional.
Ddev-capture.rst77 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl with a pointer to this
87 of :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, and call the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`
89 parameters and finally return the actual parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`
92 Like :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` the :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl
99 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` and :ref:`VIDIOC_TRY_FMT <VI…
100 details. Video capture devices must implement both the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`
101 and :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, even if :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ignores all
102 requests and always returns default parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does.
103 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` is optional.
Dvidioc-g-fmt.rst13 ioctl VIDIOC_G_FMT, VIDIOC_S_FMT, VIDIOC_TRY_FMT
19 VIDIOC_G_FMT - VIDIOC_S_FMT - VIDIOC_TRY_FMT - Get or set the data format, try a format
25 .. c:function:: int ioctl( int fd, VIDIOC_G_FMT, struct v4l2_format *argp )
26 :name: VIDIOC_G_FMT
55 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl with a pointer to this structure the driver fills
68 application. When the application calls the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl with
75 prepare for data exchange. Finally the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl returns
76 the current format parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does. Very simple,
79 application must implement the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and :ref:`VIDIOC_S_FMT <VIDIOC_G_…
81 EINVAL error code on a :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` attempt. When I/O is already in
[all …]
Dformat.rst33 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and
34 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctls. Additionally the
35 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl can be used to examine
41 The :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl is a major turning-point in the
44 change controls or modify other properties. The first :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`
60 When applications omit the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl its locking side
71 *may* support a switch using :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`.
74 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl. Implementation of …
75 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` is highly recommended but optional.
Ddev-osd.rst30 the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl.
130 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl. The driver fills the
137 substructure and call the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl.
139 the actual parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does. Like :ref:`VIDIOC_S_FMT <VIDIOC_G…
140 the :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl can be used to learn
142 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` this also works after the overlay has been enabled.
Ddev-overlay.rst33 the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl.
114 (:ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`) or overlay
134 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl. The driver fills the
141 call the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl. The driver
143 parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does. Like :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`, the
144 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl can be used to learn
146 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` this also works after the overlay has been enabled.
155 (:ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`) may fail with an ``EBUSY`` error
203 contents after calling :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`
210 after calling :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` are undefined. When clip lists are
[all …]
Dplanar-apis.rst54 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`, :ref:`VIDIOC_TRY_FMT <VIDIO…
Ddev-raw-vbi.rst38 applications must call the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl.
81 the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl with a pointer to this
90 of :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, and call the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`
104 VBI devices must implement both the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and
105 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, even if :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ignores all re…
106 and always returns default parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does.
107 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` is optional.
Dcrop.rst44 overlay) is negotiated with the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`
45 and :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctls.
49 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`
135 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl however shall not change
305 if (-1 == ioctl (fd, VIDIOC_G_FMT, &format)) {
306 perror ("VIDIOC_G_FMT");
Dio.rst31 initiating video overlay with the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`
41 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` and :ref:`VIDIOC_REQBUFS` would permit this to some
Ddev-sliced-vbi.rst31 calling the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl as defined
70 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl when the number of VBI
80 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl fills the ``fmt.sliced``
86 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl with a pointer to the
100 The :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl modifies the parameters
135 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` or
136 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>`, the ``service_lines``
289 a side effect). The :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl may
361 been negotiated with the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` or
362 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl. When the line numbers are
Dvidioc-g-fbuf.rst165 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, using the ``field``
290 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`) will be used. Only one
295 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`. If this flag is set for a
304 and negotiated with the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`
308 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, see :ref:`overlay`
323 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, see :ref:`overlay`
337 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, see :ref:`overlay`
Ddiff-v4l.rst130 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, respectively. The
169 were removed. Calling the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` or
170 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl with the desired
358 be selected with the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl.
443 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and
444 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`. They take a pointer to a struct
498 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl.
519 negotiation ioctls :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and
520 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`. They take a pointer to a struct
547 with the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl. When no
Dlibv4l-introduction.rst101 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>`,
102 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`,
103 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`,
Dvidioc-create-bufs.rst58 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` or
59 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctls to ensure that the
Dpixfmt.rst21 the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl. (The explanations here
Dfield-order.rst63 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl. If this is not desired it
89 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` or
90 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>`. struct
Dhist-v4l2.rst152 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and
153 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl taking a union and a
262 compatibility* as the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and
263 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctls may fail now if the struct
296 error codes with the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl was
437 9. The :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl was added to
439 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`, but without the overhead of
444 image format negotiations are now possible with ``VIDIOC_G_FMT``,
938 :ref:`VIDIOC_G/S/TRY_FMT <VIDIOC_G_FMT>` ioctls, which take a
Dselection-api-configuration.rst60 the image size set by :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`.
100 specified using :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl.
Dvidioc-g-sliced-vbi-cap.rst108 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl as described in
Dvidioc-g-crop.rst71 :ref:`VIDIOC_G_CROP <VIDIOC_G_CROP>` and :ref:`VIDIOC_G_FMT`. When the
Dcapture.c.rst511 if (-1 == xioctl(fd, VIDIOC_G_FMT, &fmt))
512 errno_exit("VIDIOC_G_FMT");
Ddev-decoder.rst365 calling :c:func:`VIDIOC_G_FMT`, :c:func:`VIDIOC_S_FMT`,
398 1. Call :c:func:`VIDIOC_G_FMT` on the ``CAPTURE`` queue to get format for the
443 returned by :c:func:`VIDIOC_G_FMT` on ``CAPTURE``.
512 selected/suggested by the decoder in :c:func:`VIDIOC_G_FMT`.
524 what was returned with :c:func:`VIDIOC_G_FMT`, but it may be different
552 returned by :c:func:`VIDIOC_G_FMT` on ``CAPTURE``.
684 * query the ``CAPTURE`` format using :c:func:`VIDIOC_G_FMT` and save it
/Linux-v5.4/drivers/media/v4l2-core/
Dv4l2-dev.c605 set_bit(_IOC_NR(VIDIOC_G_FMT), valid_ioctls); in determine_valid_ioctls()
650 set_bit(_IOC_NR(VIDIOC_G_FMT), valid_ioctls); in determine_valid_ioctls()
667 set_bit(_IOC_NR(VIDIOC_G_FMT), valid_ioctls); in determine_valid_ioctls()
677 set_bit(_IOC_NR(VIDIOC_G_FMT), valid_ioctls); in determine_valid_ioctls()
Dv4l2-compat-ioctl32.c1191 case VIDIOC_G_FMT32: cmd = VIDIOC_G_FMT; break; in do_video_ioctl()
1250 case VIDIOC_G_FMT: in do_video_ioctl()
1413 case VIDIOC_G_FMT: in do_video_ioctl()

12