| /linux/Documentation/sphinx/ |
| A D | parse-headers.pl | 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};
|
| /linux/Documentation/ABI/testing/ |
| 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.
102 sysfs rather than via ioctls.
111 sysfs rather than via ioctls.
[all …]
|
| /linux/Documentation/userspace-api/media/v4l/ |
| 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.
|
| A D | tuner.rst | 26 :ref:`VIDIOC_S_TUNER <VIDIOC_G_TUNER>` ioctls, respectively. The
35 determined by the current video input. Drivers must support both ioctls
69 current video output. Drivers must support both ioctls and set the
83 ioctls are used for TV and radio devices alike. Drivers must support
84 both ioctls when the tuner or modulator ioctls are supported, or when
|
| A D | dv-timings.rst | 15 due to the limited bits available, a new set of ioctls was added to
18 These ioctls deal with the detailed digital video timings that define
28 :ref:`VIDIOC_DV_TIMINGS_CAP` ioctls. To set
38 video ioctls can be used with the given input or output.
|
| A D | video.rst | 25 :ref:`VIDIOC_G_OUTPUT <VIDIOC_G_OUTPUT>` ioctls return the index of
28 :ref:`VIDIOC_S_OUTPUT <VIDIOC_G_OUTPUT>` ioctls. Drivers must
29 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.
|
| A D | dev-sdr.rst | 45 the :ref:`tuner` ioctls. Tuner ioctls are used for setting the
62 The SDR device uses the :ref:`format` ioctls to select the
65 basic :ref:`format` ioctls, the
69 To use the :ref:`format` ioctls applications set the ``type``
|
| A D | dev-radio.rst | 32 the :ref:`tuner or modulator <tuner>` ioctls.
36 parameter, or overlay ioctls. All other ioctls and I/O methods are
|
| A D | hist-v4l2.rst | 50 1998-11-12: The read/write directon of some ioctls was misdefined.
56 :ref:`VIDIOC_S_CTRL <VIDIOC_G_CTRL>` ioctls under names starting
142 driver private data streams without adding new ioctls.
144 This change obsoletes the following ioctls: ``VIDIOC_S_INFMT``,
157 ``VIDIOC_S_OUTPARM`` ioctls.
231 2001-03-02: Certain V4L ioctls which pass data in both direction
239 :ref:`VIDIOC_S_FREQUENCY <VIDIOC_G_FREQUENCY>` ioctls were added.
245 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctls may fail now if the
702 2. Audio output ioctls end in -AUDOUT, not -AUDIOOUT.
819 1. New ioctls :ref:`VIDIOC_G_EXT_CTRLS <VIDIOC_G_EXT_CTRLS>`,
[all …]
|
| 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
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:
426 uses the general-purpose data format negotiation ioctls
462 ``video_capture``. The equivalent V4L2 ioctls are
500 negotiation ioctls :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and
[all …]
|
| A D | pixfmt-indexed.rst | 11 :ref:`Video Output Overlays <osd>` only. There are no ioctls to access
12 the palette, this must be done with ioctls of the Linux framebuffer API.
|
| A D | audio.rst | 37 :ref:`VIDIOC_G_AUDOUT <VIDIOC_G_AUDOUT>` ioctls report the current
43 :ref:`VIDIOC_G_OUTPUT <VIDIOC_G_OUTPUT>` these ioctls return a
52 Drivers must implement all audio input ioctls when the device has
53 multiple selectable audio inputs, all audio output ioctls when the
|
| A D | standard.rst | 15 :ref:`VIDIOC_ENUMOUTPUT` ioctls, respectively.
46 The parameter of all these ioctls is a pointer to a
49 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` ioctls
68 standard ioctls can be used with the given input or output.
|
| A D | dev-meta.rst | 38 The metadata device uses the :ref:`format` ioctls to select the capture format.
40 to the basic :ref:`format` ioctls, the :c:func:`VIDIOC_ENUM_FMT` ioctl must be
43 To use the :ref:`format` ioctls applications set the ``type`` field of the
|
| A D | crop.rst | 31 <VIDIOC_G_CROP>` ioctls apply to input as well as output devices.
34 device the source is the video signal, and the cropping ioctls determine
38 and :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctls.
43 ioctls, or may be encoded in a compressed video stream. The target is
44 the video signal, and the cropping ioctls determine the area where the
49 :ref:`VIDIOC_S_CROP <VIDIOC_G_CROP>` ioctls. Their size (and position
91 ioctls to get and set this rectangle. It must lie completely within the
103 For output devices these structures and ioctls are used accordingly,
|
| /linux/Documentation/driver-api/serial/ |
| 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 */
|
| 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.
43 to TIOCSRS485 and TIOCGRS485 ioctls (see below). The rs485_config callback
50 ioctls. For instance, to set RS485 you can use the following code::
54 /* Include definition for RS485 ioctls: TIOCGRS485 and TIOCSRS485 */
|
| /linux/drivers/staging/media/av7110/ |
| A D | video.rst | 23 The ioctls that deal with SPUs (sub picture units) and navigation
26 These ioctls were also used by V4L2 to control MPEG decoders implemented
27 in V4L2. The use of these ioctls for that purpose has been made obsolete
28 and proper V4L2 ioctls or controls have been created to replace that
|
| A D | audio.rst | 17 These ioctls were also used by V4L2 to control MPEG decoders implemented
18 in V4L2. The use of these ioctls for that purpose has been made obsolete
19 and proper V4L2 ioctls or controls have been created to replace that
|
| /linux/Documentation/userspace-api/media/dvb/ |
| 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/tools/testing/selftests/vm/ |
| A D | userfaultfd.c | 352 uint64_t ioctls = UFFD_API_RANGE_IOCTLS; in get_expected_ioctls() local
355 ioctls &= ~(1 << _UFFDIO_ZEROPAGE); in get_expected_ioctls()
358 ioctls &= ~(1 << _UFFDIO_WRITEPROTECT); in get_expected_ioctls()
361 ioctls &= ~(1 << _UFFDIO_CONTINUE); in get_expected_ioctls()
363 return ioctls; in get_expected_ioctls()
369 uint64_t actual = ioctls & expected; in assert_expected_ioctls_present()
1095 uffdio_register.mode, uffdio_register.ioctls); in userfaultfd_zeropage_test()
1132 uffdio_register.mode, uffdio_register.ioctls); in userfaultfd_events_test()
1184 uffdio_register.mode, uffdio_register.ioctls); in userfaultfd_sig_test()
1241 uffdio_register.mode, uffdio_register.ioctls); in userfaultfd_minor_test()
[all …]
|
| /linux/Documentation/driver-api/media/ |
| 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
280 0x01 Log the ioctl name and error code. VIDIOC_(D)QBUF ioctls are
283 ioctls are
[all …]
|
| /linux/Documentation/translations/zh_CN/video4linux/ |
| A D | v4l2-framework.txt | 407 这些 ioctls 控制与 V4L2 中定义的一致。他们行为相同，唯一的
415 这些 ioctls 事件与 V4L2 中定义的一致。他们行为相同，唯一的
426 私有 ioctls
428 不在以上列表中的所有 ioctls 会通过 core::ioctl 操作直接传递
589 你可以在 video_device_register 被调用前通过以下函数标记这个 ioctls。
617 用于 unlocked_ioctl，但为了使用 ioctls 你通过以下函数可禁用锁定：
626 需要自行为缓冲区队列的 ioctls 实现锁定。
|
| /linux/Documentation/process/ |
| 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/gpu/ |
| A D | drm-uapi.rst | 10 drivers & device-aware applications through ioctls and sysfs files.
16 Cover generic ioctls and sysfs layout here. We only need high-level
128 set of operations (mainly ioctls). The primary node is always created
150 per device. No ioctls except PRIME-related ioctls will be allowed on
155 driver-dependent render-only ioctls as DRM_RENDER_ALLOW so render
157 privileged ioctls on render nodes.
225 TEST_ONLY, and any other ioctls either fail with ENODEV or fake
229 is expecting. This applies also to ioctls that faked success.
249 driver-specific ioctls and handling those in userspace drivers, or
292 :doc: driver specific ioctls
[all …]
|