Home
last modified time | relevance | path

Searched refs:VIDIOC_S_FMT (Results 1 – 25 of 37) sorted by relevance

12

/linux-6.1.9/Documentation/userspace-api/media/v4l/
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
22 .. c:macro:: VIDIOC_S_FMT
24 ``int ioctl(int fd, VIDIOC_S_FMT, struct v4l2_format *argp)``
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
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
80 The :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl is equivalent to :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` …
88 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` returns for the same input or output.
[all …]
Dformat.rst27 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctls. Additionally the
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 …
Ddev-output.rst75 of :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, and call the :ref:`VIDIOC_S_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…
89 and :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, even if :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ignores all
Ddev-capture.rst78 of :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, and call the :ref:`VIDIOC_S_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…
92 and :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, even if :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ignores all
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
Ddev-osd.rst23 the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl.
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…
135 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` this also works after the overlay has been enabled.
Ddev-overlay.rst26 the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl.
111 (:ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`) or overlay
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
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
228 its contents after calling :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` are
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`
Dpixfmt.rst14 the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl. (The explanations here
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
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
272 a side effect). The :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl may
357 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl. When the line numbers are
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
346 be selected with the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl.
428 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`. They take a pointer to a struct
481 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl.
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-raw-vbi.rst32 applications must call the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl.
81 of :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, and call the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`
96 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, even if :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ignores all re…
Dcapture.c.rst498 if (-1 == xioctl(fd, VIDIOC_S_FMT, &fmt))
499 errno_exit("VIDIOC_S_FMT");
501 /* Note VIDIOC_S_FMT may change width and height. */
Dcrop.rst38 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>`
213 if (-1 == ioctl (fd, VIDIOC_S_FMT, &format)) {
Dplanar-apis.rst47 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`, :ref:`VIDIOC_TRY_FMT <VIDIO…
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.
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
Dv4l2grab.c.rst81 xioctl(fd, VIDIOC_S_FMT, &fmt);
Dvidioc-g-sliced-vbi-cap.rst99 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl as described in
Ddev-stateless-decoder.rst72 1. Set the coded format on the ``OUTPUT`` queue via :c:func:`VIDIOC_S_FMT`.
132 select one of them via :c:func:`VIDIOC_S_FMT`.
149 :c:func:`VIDIOC_S_FMT` on ``CAPTURE`` queue. It is possible for the client to
Dbuffer.rst71 :c:func:`VIDIOC_S_FMT` ioctl in all cases described in this section.
93 #. VIDIOC_S_FMT
123 #. VIDIOC_S_FMT
129 response to format change (:c:func:`VIDIOC_S_FMT`) or control changes
Dlibv4l-introduction.rst94 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`,
/linux-6.1.9/drivers/media/v4l2-core/
Dv4l2-dev.c624 __set_bit(_IOC_NR(VIDIOC_S_FMT), valid_ioctls); in determine_valid_ioctls()
657 SET_VALID_IOCTL(ops, VIDIOC_S_FMT, vidioc_s_fmt_meta_cap); in determine_valid_ioctls()
663 SET_VALID_IOCTL(ops, VIDIOC_S_FMT, vidioc_s_fmt_meta_out); in determine_valid_ioctls()
677 __set_bit(_IOC_NR(VIDIOC_S_FMT), valid_ioctls); in determine_valid_ioctls()
688 SET_VALID_IOCTL(ops, VIDIOC_S_FMT, vidioc_s_fmt_vid_cap); in determine_valid_ioctls()
701 SET_VALID_IOCTL(ops, VIDIOC_S_FMT, vidioc_s_fmt_sdr_cap); in determine_valid_ioctls()
707 SET_VALID_IOCTL(ops, VIDIOC_S_FMT, vidioc_s_fmt_sdr_out); in determine_valid_ioctls()
/linux-6.1.9/drivers/staging/most/video/
Dvideo.c291 return comp_set_format(mdev, VIDIOC_S_FMT, f); in vidioc_s_fmt_vid_cap()

12