Searched refs:ioctls (Results 1 – 25 of 205) 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 …]
18 working in both modes, and proper ioctls (see later) should be made27 ISO7816 parameters in ioctls.32 to TIOCGISO7816 and TIOCSISO7816 ioctls (see below). The iso7816_config39 ioctls. For instance, to set ISO7816 you can use the following code::43 /* Include definition for ISO7816 ioctls: TIOCSISO7816 and TIOCGISO7816 */
25 working in both modes, and proper ioctls (see later) should be made34 parameters in the platform data and in ioctls.43 to TIOCSRS485 and TIOCGRS485 ioctls (see below). The rs485_config callback50 ioctls. For instance, to set RS485 you can use the following code::54 /* Include definition for RS485 ioctls: TIOCGRS485 and TIOCSRS485 */
50 For driver debugging purposes these ioctls allow test applications to55 security, its stability and damage the hardware, both ioctls require57 with the ``CONFIG_VIDEO_ADV_DEBUG`` option to enable these ioctls.81 These ioctls are optional, not all drivers may support them. However82 when a driver supports these ioctls it must also support84 it may support ``VIDIOC_DBG_G_CHIP_INFO`` but not these ioctls.90 We recommended the v4l2-dbg utility over calling these ioctls directly.171 these ioctls.
33 :ref:`VIDIOC_S_TUNER <VIDIOC_G_TUNER>` ioctls, respectively. The42 determined by the current video input. Drivers must support both ioctls76 current video output. Drivers must support both ioctls and set the90 ioctls are used for TV and radio devices alike. Drivers must support91 both ioctls when the tuner or modulator ioctls are supported, or when
32 :ref:`VIDIOC_G_OUTPUT <VIDIOC_G_OUTPUT>` ioctls return the index of35 :ref:`VIDIOC_S_OUTPUT <VIDIOC_G_OUTPUT>` ioctls. Drivers must36 implement all the input ioctls when the device has one or more inputs,37 all the output ioctls when the device has one or more outputs.
22 due to the limited bits available, a new set of ioctls was added to25 These ioctls deal with the detailed digital video timings that define35 :ref:`VIDIOC_DV_TIMINGS_CAP` ioctls. To set45 video ioctls can be used with the given input or output.
52 the :ref:`tuner` ioctls. Tuner ioctls are used for setting the69 The SDR device uses the :ref:`format` ioctls to select the72 basic :ref:`format` ioctls, the76 To use the :ref:`format` ioctls applications set the ``type``
39 the :ref:`tuner or modulator <tuner>` ioctls.43 parameter, or overlay ioctls. All other ioctls and I/O methods are
57 1998-11-12: The read/write directon of some ioctls was misdefined.63 :ref:`VIDIOC_S_CTRL <VIDIOC_G_CTRL>` ioctls under names starting99 1999-03-31: Better compatibility for v4l memory capture ioctls. Requires133 to an integer. Where it makes sense, ioctls will return the actual135 convention in the V4L2 API. The affected ioctls are: VIDIOC_PREVIEW,155 simplify the API by eliminating several ioctls and to allow new and156 driver private data streams without adding new ioctls.158 This change obsoletes the following ioctls: ``VIDIOC_S_INFMT``,167 ``VIDIOC_S_PARM`` ioctls were merged with ``VIDIOC_G_OUTPARM`` and173 ``VIDIOC_S_OUTPARM`` ioctls.[all …]
18 :ref:`Video Output Overlays <osd>` only. There are no ioctls to access19 the palette, this must be done with ioctls of the Linux framebuffer API.
44 :ref:`VIDIOC_G_AUDOUT <VIDIOC_G_AUDOUT>` ioctls report the current50 :ref:`VIDIOC_G_OUTPUT <VIDIOC_G_OUTPUT>` these ioctls return a59 Drivers must implement all audio input ioctls when the device has60 multiple selectable audio inputs, all audio output ioctls when the
68 V4L drivers respond to V4L2 ioctls with an ``EINVAL`` error code.166 audio ioctls are described in :ref:`audio`.180 device. The equivalent V4L2 ioctls are232 V4L TV or radio device. The equivalent V4L2 ioctls are246 replaced by a whole new set of ioctls and structures described in281 :ref:`VIDIOC_S_CTRL <VIDIOC_G_CTRL>` ioctls:366 of a V4L device. The equivalent V4L2 ioctls are391 :ref:`VIDIOC_S_CTRL <VIDIOC_G_CTRL>` ioctls:430 The V4L2 ioctls equivalent to ``VIDIOCGFBUF`` and ``VIDIOCSFBUF`` are441 Instead of the special ioctls ``VIDIOCGWIN`` and ``VIDIOCSWIN`` V4L2[all …]
22 :ref:`VIDIOC_ENUMOUTPUT` ioctls, respectively.53 The parameter of all these ioctls is a pointer to a56 standard ioctls when the device has one or more video inputs or outputs.70 :ref:`VIDIOC_S_STD <VIDIOC_G_STD>`, :ref:`VIDIOC_QUERYSTD` and :ref:`VIDIOC_ENUMSTD` ioctls75 standard ioctls can be used with the given input or output.
38 <VIDIOC_G_CROP>` ioctls apply to input as well as output devices.41 device the source is the video signal, and the cropping ioctls determine45 and :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctls.50 ioctls, or may be encoded in a compressed video stream. The target is51 the video signal, and the cropping ioctls determine the area where the56 :ref:`VIDIOC_S_CROP <VIDIOC_G_CROP>` ioctls. Their size (and position98 ioctls to get and set this rectangle. It must lie completely within the110 For output devices these structures and ioctls are used accordingly,
45 The metadata device uses the :ref:`format` ioctls to select the capture format.47 to the basic :ref:`format` ioctls, the :c:func:`VIDIOC_ENUM_FMT` ioctl must be50 To use the :ref:`format` ioctls applications set the ``type`` field of the
30 The ioctls that deal with SPUs (sub picture units) and navigation33 These ioctls were also used by V4L2 to control MPEG decoders implemented34 in V4L2. The use of these ioctls for that purpose has been made obsolete35 and proper V4L2 ioctls or controls have been created to replace that
24 These ioctls were also used by V4L2 to control MPEG decoders implemented25 in V4L2. The use of these ioctls for that purpose has been made obsolete26 and proper V4L2 ioctls or controls have been created to replace that
33 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.
181 __u64 ioctls; member199 __u64 ioctls; member
407 这些 ioctls 控制与 V4L2 中定义的一致。他们行为相同，唯一的415 这些 ioctls 事件与 V4L2 中定义的一致。他们行为相同，唯一的426 私有 ioctls428 不在以上列表中的所有 ioctls 会通过 core::ioctl 操作直接传递589 你可以在 video_device_register 被调用前通过以下函数标记这个 ioctls。617 用于 unlocked_ioctl，但为了使用 ioctls 你通过以下函数可禁用锁定：626 需要自行为缓冲区队列的 ioctls 实现锁定。
2 (How to avoid) Botching up ioctls5 From: http://blog.ffwll.ch/2013/11/botching-up-ioctls.html12 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 the65 * Have a plan for extending ioctls with new flags or new fields at the end of106 * Make all your ioctls restartable. First X really loves signals and second132 the ioctls supported by the drm/i915 get this fully right, which means there's159 * Consider ditching any synchronous wait ioctls with timeouts and just deliver214 * Consider other interfaces than ioctls. A sysfs attribute is much better for223 horrible ioctls on newer iterations of your hardware, but generally it takes
8 drivers & device-aware applications through ioctls and sysfs files.14 Cover generic ioctls and sysfs layout here. We only need high-level117 set of operations (mainly ioctls). The primary node is always created131 is, no modesetting or privileged ioctls can be issued on render nodes.139 per device. No ioctls except PRIME-related ioctls will be allowed on144 driver-dependent render-only ioctls as DRM_RENDER_ALLOW so render146 privileged ioctls on render nodes.156 Besides dropping all modeset/global ioctls, render nodes also drop the171 :doc: driver specific ioctls319 The DRM core exposes two vertical blank related ioctls:
28 2) various UFFDIO_* ioctls that can manage the virtual memory regions60 uffdio_api.features and uffdio_api.ioctls two 64bit bitmasks of85 be invoked (if present in the returned uffdio_api.ioctls bitmask) to91 uffdio_register.ioctls bitmask of ioctls that are suitable to resolve92 userfaults on the range registered. Not all ioctls will necessarily be97 Userland can use the uffdio_register.ioctls to manage the virtual140 ioctls on the userfaultfd in order to map the received pages into the238 non cooperative manager, for example to allow UFFDIO_COPY ioctls to
