| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-tty | 30 sysfs rather than via ioctls.
39 sysfs rather than via ioctls.
48 sysfs rather than via ioctls.
57 sysfs rather than via ioctls.
66 sysfs rather than via ioctls.
75 sysfs rather than via ioctls.
84 sysfs rather than via ioctls.
93 sysfs rather than via ioctls.
105 sysfs rather than via ioctls.
114 sysfs rather than via ioctls.
[all …]
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | vidioc-dbg-g-register.rst | 43 For driver debugging purposes these ioctls allow test applications to
48 security, its stability and damage the hardware, both ioctls require
50 with the ``CONFIG_VIDEO_ADV_DEBUG`` option to enable these ioctls.
74 These ioctls are optional, not all drivers may support them. However
75 when a driver supports these ioctls it must also support
77 it may support ``VIDIOC_DBG_G_CHIP_INFO`` but not these ioctls.
83 We recommended the v4l2-dbg utility over calling these ioctls directly.
160 these ioctls.
|
| H A D | tuner.rst | 27 :ref:`VIDIOC_S_TUNER <VIDIOC_G_TUNER>` ioctls, respectively. The
36 determined by the current video input. Drivers must support both ioctls
70 current video output. Drivers must support both ioctls and set the
84 ioctls are used for TV and radio devices alike. Drivers must support
85 both ioctls when the tuner or modulator ioctls are supported, or when
|
| H A D | video.rst | 26 :ref:`VIDIOC_G_OUTPUT <VIDIOC_G_OUTPUT>` ioctls return the index of
29 :ref:`VIDIOC_S_OUTPUT <VIDIOC_G_OUTPUT>` ioctls. Drivers must
30 implement all the input ioctls when the device has one or more inputs,
31 all the output ioctls when the device has one or more outputs.
|
| H A D | dev-sdr.rst | 46 the :ref:`tuner` ioctls. Tuner ioctls are used for setting the
63 The SDR device uses the :ref:`format` ioctls to select the
66 basic :ref:`format` ioctls, the
70 To use the :ref:`format` ioctls applications set the ``type``
|
| H A D | dev-radio.rst | 33 the :ref:`tuner or modulator <tuner>` ioctls.
37 parameter, or overlay ioctls. All other ioctls and I/O methods are
|
| H A D | dv-timings.rst | 16 due to the limited bits available, a new set of ioctls was added to
19 These ioctls deal with the detailed digital video timings that define
29 :ref:`VIDIOC_DV_TIMINGS_CAP` ioctls. To set
60 video ioctls can be used with the given input or output.
|
| H A D | pixfmt-indexed.rst | 12 :ref:`Video Output Overlays <osd>` only. There are no ioctls to access
13 the palette, this must be done with ioctls of the Linux framebuffer API.
|
| H A D | hist-v4l2.rst | 50 1998-11-12: The read/write direction of some ioctls was misdefined.
56 :ref:`VIDIOC_S_CTRL <VIDIOC_G_CTRL>` ioctls under names starting
89 1999-03-31: Better compatibility for v4l memory capture ioctls. Requires
121 to an integer. Where it makes sense, ioctls will return the actual
123 convention in the V4L2 API. The affected ioctls are: VIDIOC_PREVIEW,
141 simplify the API by eliminating several ioctls and to allow new and
142 driver private data streams without adding new ioctls.
144 This change obsoletes the following ioctls: ``VIDIOC_S_INFMT``,
152 ``VIDIOC_S_PARM`` ioctls were merged with ``VIDIOC_G_OUTPARM`` and
157 ``VIDIOC_S_OUTPARM`` ioctls.
[all …]
|
| H A D | audio.rst | 38 :ref:`VIDIOC_G_AUDOUT <VIDIOC_G_AUDOUT>` ioctls report the current
44 :ref:`VIDIOC_G_OUTPUT <VIDIOC_G_OUTPUT>` these ioctls return a
53 Drivers must implement all audio input ioctls when the device has
54 multiple selectable audio inputs, all audio output ioctls when the
|
| H A D | diff-v4l.rst | 59 V4L drivers respond to V4L2 ioctls with an ``EINVAL`` error code.
163 audio ioctls are described in :ref:`audio`.
176 device. The equivalent V4L2 ioctls are
225 V4L TV or radio device. The equivalent V4L2 ioctls are
239 replaced by a whole new set of ioctls and structures described in
273 :ref:`VIDIOC_S_CTRL <VIDIOC_G_CTRL>` ioctls:
353 of a V4L device. The equivalent V4L2 ioctls are
378 :ref:`VIDIOC_S_CTRL <VIDIOC_G_CTRL>` ioctls:
414 The V4L2 ioctls equivalent to ``VIDIOCGFBUF`` and ``VIDIOCSFBUF`` are
425 Instead of the special ioctls ``VIDIOCGWIN`` and ``VIDIOCSWIN`` V4L2
[all …]
|
| H A D | standard.rst | 16 :ref:`VIDIOC_ENUMOUTPUT` ioctls, respectively.
47 The parameter of all these ioctls is a pointer to a
50 standard ioctls when the device has one or more video inputs or outputs.
64 :ref:`VIDIOC_S_STD <VIDIOC_G_STD>`, :ref:`VIDIOC_QUERYSTD` and :ref:`VIDIOC_ENUMSTD` ioctls
69 standard ioctls can be used with the given input or output.
|
| H A D | crop.rst | 32 <VIDIOC_G_CROP>` ioctls apply to input as well as output devices.
35 device the source is the video signal, and the cropping ioctls determine
39 and :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctls.
44 ioctls, or may be encoded in a compressed video stream. The target is
45 the video signal, and the cropping ioctls determine the area where the
50 :ref:`VIDIOC_S_CROP <VIDIOC_G_CROP>` ioctls. Their size (and position
92 ioctls to get and set this rectangle. It must lie completely within the
104 For output devices these structures and ioctls are used accordingly,
|
| H A D | vidioc-subdev-g-client-cap.rst | 39 These ioctls are used to get and set the client (the application using the
40 subdevice ioctls) capabilities. The client capabilities are stored in the file
87 ioctls. If this is not set (which is the default), the 'stream' fields
|
| H A D | app-pri.rst | 21 :ref:`VIDIOC_S_PRIORITY <VIDIOC_G_PRIORITY>` ioctls to request and
24 V4L2 and drivers not supporting these ioctls. Applications requiring a
|
| H A D | streaming-par.rst | 22 Finally these ioctls can be used to determine the number of buffers used
33 These ioctls are optional, drivers need not implement them. If so, they
|
| H A D | vidioc-subdev-g-routing.rst | 40 These ioctls are used to get and set the routing in a media entity.
58 ioctls to indicate how many routes the kernel can return, and is never modified
63 routes that the application stored in the ``routes`` array. For both ioctls, it
70 both ioctls. This indicates thare are more routes in the routing table than fits
|
| H A D | dev-meta.rst | 39 The metadata device uses the :ref:`format` ioctls to select the capture format.
41 to the basic :ref:`format` ioctls, the :c:func:`VIDIOC_ENUM_FMT` ioctl must be
44 To use the :ref:`format` ioctls applications set the ``type`` field of the
|
| /linux/Documentation/driver-api/serial/ |
| H A D | serial-iso7816.rst | 18 working in both modes, and proper ioctls (see later) should be made
27 ISO7816 parameters in ioctls.
32 to TIOCGISO7816 and TIOCSISO7816 ioctls (see below). The iso7816_config
39 ioctls. For instance, to set ISO7816 you can use the following code::
43 /* Include definition for ISO7816 ioctls: TIOCSISO7816 and TIOCGISO7816 */
|
| H A D | serial-rs485.rst | 25 working in both modes, and proper ioctls (see later) should be made
34 parameters in the platform data and in ioctls.
59 ioctls. For instance, to set RS485 you can use the following code::
63 /* Include definition for RS485 ioctls: TIOCGRS485 and TIOCSRS485 */
|
| /linux/Documentation/userspace-api/media/dvb/ |
| H A D | ca_high_level.rst | 17 eliminating the need for any additional ioctls.
21 array to/from the CI ioctls as defined in the Linux DVB API. No changes
66 regular ioctls.
68 All these ioctls are also valid for the High level CI interface
113 using the CA_GET_MSG and CA_SEND_MSG ioctls. An EN50221 style wrapper is
|
| /linux/Documentation/driver-api/media/ |
| H A D | v4l2-dev.rst | 73 is used for the queuing ioctls (``VIDIOC_REQBUFS``, ``CREATE_BUFS``,
77 to wait for other ioctls. This queue pointer is also used by the
106 your :c:type:`v4l2_ioctl_ops` should be ignored. You can mark such ioctls by
137 ioctls and locking
143 serialize all ioctls.
148 to serialize all queuing ioctls (see the previous section
149 for the full list of those ioctls).
151 The advantage of using a different lock for the queuing ioctls is that for some
154 ioctls. That way your ``VIDIOC_DQBUF`` doesn't stall because the driver is busy
272 0x01 Log the ioctl name and error code. VIDIOC_(D)QBUF ioctls are
[all …]
|
| /linux/Documentation/process/ |
| H A D | botching-up-ioctls.rst | 2 (How to avoid) Botching up ioctls
5 From: https://blog.ffwll.ch/2013/11/botching-up-ioctls.html
12 driver has its own set of ioctls to allocate memory and submit work to the GPU.
62 rejecting the new flags/modes or ioctls (since doing that was botched in the
65 * Have a plan for extending ioctls with new flags or new fields at the end of
106 * Make all your ioctls restartable. First X really loves signals and second
132 the ioctls supported by the drm/i915 get this fully right, which means there's
159 * Consider ditching any synchronous wait ioctls with timeouts and just deliver
214 * Consider other interfaces than ioctls. A sysfs attribute is much better for
223 horrible ioctls on newer iterations of your hardware, but generally it takes
|
| /linux/Documentation/userspace-api/media/rc/ |
| H A D | lirc-get-timeout.rst | 8 ioctls LIRC_GET_MIN_TIMEOUT and LIRC_GET_MAX_TIMEOUT
49 both ioctls will return the same value even though the timeout
|
| /linux/rust/kernel/drm/ |
| H A D | ioctl.rs | 118 let ioctls = &[$( localVariable
164 ioctls
|