Home
last modified time | relevance | path

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

12

/Linux-v4.19/Documentation/media/uapi/v4l/
Ddev-output.rst67 and call the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl with a pointer
77 of :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, and call the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`
79 parameters and finally return the actual parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`
82 Like :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` the :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl
89 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` and :ref:`VIDIOC_TRY_FMT <VI…
90 details. Video output devices must implement both the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`
91 and :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, even if :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ignores all
92 requests and always returns default parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does.
93 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` is optional.
Ddev-capture.rst70 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl with a pointer to this
80 of :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, and call the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`
82 parameters and finally return the actual parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`
85 Like :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` the :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl
92 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` and :ref:`VIDIOC_TRY_FMT <VI…
93 details. Video capture devices must implement both the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`
94 and :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, even if :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ignores all
95 requests and always returns default parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does.
96 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` is optional.
Dvidioc-g-fmt.rst6 ioctl VIDIOC_G_FMT, VIDIOC_S_FMT, VIDIOC_TRY_FMT
12 VIDIOC_G_FMT - VIDIOC_S_FMT - VIDIOC_TRY_FMT - Get or set the data format, try a format
18 .. c:function:: int ioctl( int fd, VIDIOC_G_FMT, struct v4l2_format *argp )
19 :name: VIDIOC_G_FMT
48 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl with a pointer to this structure the driver fills
61 application. When the application calls the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl with
68 prepare for data exchange. Finally the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl returns
69 the current format parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does. Very simple,
72 application must implement the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and :ref:`VIDIOC_S_FMT <VIDIOC_G_…
74 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.
107 (:ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`) or overlay
127 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl. The driver fills the
134 call the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl. The driver
136 parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does. Like :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`, the
137 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl can be used to learn
139 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` this also works after the overlay has been enabled.
148 (:ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`) may fail with an ``EBUSY`` error
196 contents after calling :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`
203 after calling :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` are undefined. When clip lists are
[all …]
Ddev-raw-vbi.rst31 applications must call the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl.
74 the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl with a pointer to this
83 of :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, and call the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`
97 VBI devices must implement both the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and
98 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, even if :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ignores all re…
99 and always returns default parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does.
100 :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.rst24 initiating video overlay with the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`
34 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` and :ref:`VIDIOC_REQBUFS` would permit this to some
Dvidioc-create-bufs.rst51 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` or
52 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctls to ensure that the
Dvidioc-g-fbuf.rst158 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, using the ``field``
283 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`) will be used. Only one
288 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`. If this flag is set for a
297 and negotiated with the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`
301 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, see :ref:`overlay`
316 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, see :ref:`overlay`
330 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, see :ref:`overlay`
Ddiff-v4l.rst123 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, respectively. The
162 were removed. Calling the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` or
163 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl with the desired
351 be selected with the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl.
436 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and
437 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`. They take a pointer to a struct
491 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl.
512 negotiation ioctls :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and
513 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`. They take a pointer to a struct
540 with the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl. When no
Ddev-sliced-vbi.rst24 calling the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl as defined
63 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl when the number of VBI
73 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl fills the ``fmt.sliced``
79 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl with a pointer to the
93 The :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl modifies the parameters
128 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` or
129 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>`, the ``service_lines``
282 a side effect). The :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl may
354 been negotiated with the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` or
355 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl. When the line numbers are
Dlibv4l-introduction.rst94 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>`,
95 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`,
96 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`,
Dpixfmt.rst14 the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl. (The explanations here
Dfield-order.rst51 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl. If this is not desired it
76 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` or
77 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>`. struct
Dhist-v4l2.rst145 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and
146 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl taking a union and a
255 compatibility* as the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and
256 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctls may fail now if the struct
289 error codes with the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl was
430 9. The :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl was added to
432 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`, but without the overhead of
437 image format negotiations are now possible with ``VIDIOC_G_FMT``,
931 :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.rst101 :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");
Dopen.rst116 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl) and other applications are
/Linux-v4.19/drivers/media/v4l2-core/
Dv4l2-dev.c595 set_bit(_IOC_NR(VIDIOC_G_FMT), valid_ioctls); in determine_valid_ioctls()
638 set_bit(_IOC_NR(VIDIOC_G_FMT), valid_ioctls); in determine_valid_ioctls()
655 set_bit(_IOC_NR(VIDIOC_G_FMT), valid_ioctls); in determine_valid_ioctls()
665 set_bit(_IOC_NR(VIDIOC_G_FMT), valid_ioctls); in determine_valid_ioctls()
Dv4l2-compat-ioctl32.c1179 case VIDIOC_G_FMT32: cmd = VIDIOC_G_FMT; break; in do_video_ioctl()
1238 case VIDIOC_G_FMT: in do_video_ioctl()
1401 case VIDIOC_G_FMT: in do_video_ioctl()

12