Searched refs:ioctls (Results 1 – 25 of 211) sorted by relevance
123456789
24 my %ioctls;74 $ioctls{$s} = "\\ :ref:`$s <$n>`\\ ";153 delete $ioctls{$1} if (exists($ioctls{$1}));200 $ioctls{$old} = $new if (exists($ioctls{$old}));229 print Data::Dumper->Dump([\%ioctls], [qw(*ioctls)]) if (%ioctls);260 foreach my $r (keys %ioctls) {261 my $s = $ioctls{$r};
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.102 sysfs rather than via ioctls.111 sysfs rather than via ioctls.[all …]
43 For driver debugging purposes these ioctls allow test applications to48 security, its stability and damage the hardware, both ioctls require50 with the ``CONFIG_VIDEO_ADV_DEBUG`` option to enable these ioctls.74 These ioctls are optional, not all drivers may support them. However75 when a driver supports these ioctls it must also support77 it may support ``VIDIOC_DBG_G_CHIP_INFO`` but not these ioctls.83 We recommended the v4l2-dbg utility over calling these ioctls directly.164 these ioctls.
26 :ref:`VIDIOC_S_TUNER <VIDIOC_G_TUNER>` ioctls, respectively. The35 determined by the current video input. Drivers must support both ioctls69 current video output. Drivers must support both ioctls and set the83 ioctls are used for TV and radio devices alike. Drivers must support84 both ioctls when the tuner or modulator ioctls are supported, or when
15 due to the limited bits available, a new set of ioctls was added to18 These ioctls deal with the detailed digital video timings that define28 :ref:`VIDIOC_DV_TIMINGS_CAP` ioctls. To set38 video ioctls can be used with the given input or output.
25 :ref:`VIDIOC_G_OUTPUT <VIDIOC_G_OUTPUT>` ioctls return the index of28 :ref:`VIDIOC_S_OUTPUT <VIDIOC_G_OUTPUT>` ioctls. Drivers must29 implement all the input ioctls when the device has one or more inputs,30 all the output ioctls when the device has one or more outputs.
32 the :ref:`tuner or modulator <tuner>` ioctls.36 parameter, or overlay ioctls. All other ioctls and I/O methods are
45 the :ref:`tuner` ioctls. Tuner ioctls are used for setting the62 The SDR device uses the :ref:`format` ioctls to select the65 basic :ref:`format` ioctls, the69 To use the :ref:`format` ioctls applications set the ``type``
11 :ref:`Video Output Overlays <osd>` only. There are no ioctls to access12 the palette, this must be done with ioctls of the Linux framebuffer API.
32 The metadata device uses the :ref:`format` ioctls to select the capture format.34 to the basic :ref:`format` ioctls, the :c:func:`VIDIOC_ENUM_FMT` ioctl must be37 To use the :ref:`format` ioctls applications set the ``type`` field of the
37 :ref:`VIDIOC_G_AUDOUT <VIDIOC_G_AUDOUT>` ioctls report the current43 :ref:`VIDIOC_G_OUTPUT <VIDIOC_G_OUTPUT>` these ioctls return a52 Drivers must implement all audio input ioctls when the device has53 multiple selectable audio inputs, all audio output ioctls when the
50 1998-11-12: The read/write directon of some ioctls was misdefined.56 :ref:`VIDIOC_S_CTRL <VIDIOC_G_CTRL>` ioctls under names starting92 1999-03-31: Better compatibility for v4l memory capture ioctls. Requires126 to an integer. Where it makes sense, ioctls will return the actual128 convention in the V4L2 API. The affected ioctls are: VIDIOC_PREVIEW,148 simplify the API by eliminating several ioctls and to allow new and149 driver private data streams without adding new ioctls.151 This change obsoletes the following ioctls: ``VIDIOC_S_INFMT``,160 ``VIDIOC_S_PARM`` ioctls were merged with ``VIDIOC_G_OUTPARM`` and166 ``VIDIOC_S_OUTPARM`` ioctls.[all …]
61 V4L drivers respond to V4L2 ioctls with an ``EINVAL`` error code.159 audio ioctls are described in :ref:`audio`.173 device. The equivalent V4L2 ioctls are225 V4L TV or radio device. The equivalent V4L2 ioctls are239 replaced by a whole new set of ioctls and structures described in274 :ref:`VIDIOC_S_CTRL <VIDIOC_G_CTRL>` ioctls:359 of a V4L device. The equivalent V4L2 ioctls are384 :ref:`VIDIOC_S_CTRL <VIDIOC_G_CTRL>` ioctls:423 The V4L2 ioctls equivalent to ``VIDIOCGFBUF`` and ``VIDIOCSFBUF`` are434 Instead of the special ioctls ``VIDIOCGWIN`` and ``VIDIOCSWIN`` V4L2[all …]
15 :ref:`VIDIOC_ENUMOUTPUT` ioctls, respectively.46 The parameter of all these ioctls is a pointer to a49 standard ioctls when the device has one or more video inputs or outputs.63 :ref:`VIDIOC_S_STD <VIDIOC_G_STD>`, :ref:`VIDIOC_QUERYSTD` and :ref:`VIDIOC_ENUMSTD` ioctls68 standard ioctls can be used with the given input or output.
20 :ref:`VIDIOC_S_PRIORITY <VIDIOC_G_PRIORITY>` ioctls to request and23 V4L2 and drivers not supporting these ioctls. Applications requiring a
21 Finally these ioctls can be used to determine the number of buffers used32 These ioctls are optional, drivers need not implement them. If so, they
23 The ioctls that deal with SPUs (sub picture units) and navigation26 These ioctls were also used by V4L2 to control MPEG decoders implemented27 in V4L2. The use of these ioctls for that purpose has been made obsolete28 and proper V4L2 ioctls or controls have been created to replace that
17 These ioctls were also used by V4L2 to control MPEG decoders implemented18 in V4L2. The use of these ioctls for that purpose has been made obsolete19 and proper V4L2 ioctls or controls have been created to replace that
3 botching-up-ioctls.txt4 - how to avoid botching up ioctls
21 working in both modes, and proper ioctls (see later) should be made29 parameters in the platform data and in ioctls.38 to TIOCSRS485 and TIOCGRS485 ioctls (see below). The rs485_config callback44 ioctls. For instance, to set RS485 you can use the following code:48 /* Include definition for RS485 ioctls: TIOCGRS485 and TIOCSRS485 */
32 bool "enable the DVB ioctls abuse on ivtv driver"36 Enable the usage of the a DVB set of ioctls that were abused by39 Those ioctls were not needed for a long time, as IVTV implements40 the proper V4L2 ioctls since kernel 3.3.
7 ioctls LIRC_GET_MIN_TIMEOUT and LIRC_GET_MAX_TIMEOUT47 both ioctls will return the same value even though the timeout
181 __u64 ioctls; member199 __u64 ioctls; member
71 is used for the queuing ioctls (``VIDIOC_REQBUFS``, ``CREATE_BUFS``,75 to wait for other ioctls. This queue pointer is also used by the104 your :c:type:`v4l2_ioctl_ops` should be ignored. You can mark such ioctls by135 ioctls and locking141 serialize all ioctls.146 to serialize all queuing ioctls (see the previous section147 for the full list of those ioctls).149 The advantage of using a different lock for the queuing ioctls is that for some152 ioctls. That way your ``VIDIOC_DQBUF`` doesn't stall because the driver is busy278 0x01 Log the ioctl name and error code. VIDIOC_(D)QBUF ioctls are[all …]
8 drivers & device-aware applications through ioctls and sysfs files.14 Cover generic ioctls and sysfs layout here. We only need high-level115 set of operations (mainly ioctls). The primary node is always created129 is, no modesetting or privileged ioctls can be issued on render nodes.137 per device. No ioctls except PRIME-related ioctls will be allowed on142 driver-dependent render-only ioctls as DRM_RENDER_ALLOW so render144 privileged ioctls on render nodes.154 Besides dropping all modeset/global ioctls, render nodes also drop the169 :doc: driver specific ioctls306 The DRM core exposes two vertical blank related ioctls:
