| /Documentation/userspace-api/media/v4l/ |
| D | func-ioctl.rst | 4 .. _func-ioctl:
7 V4L2 ioctl()
13 v4l2-ioctl - Program a V4L2 device
20 #include <sys/ioctl.h>
22 ``int ioctl(int fd, int request, void *argp)``
31 V4L2 ioctl request code as defined in the ``videodev2.h`` header
40 The :ref:`ioctl() <func-ioctl>` function is used to program V4L2 devices. The
41 argument ``fd`` must be an open file descriptor. An ioctl ``request``
44 defines specifying V4L2 ioctl requests are located in the
47 All V4L2 ioctl requests, their respective function and parameters are
[all …]
|
| D | querycap.rst | 14 The :ref:`VIDIOC_QUERYCAP` ioctl is available to
22 :ref:`VIDIOC_QUERYCAP` to check if a specific ioctl
24 provide support for an ioctl.
26 Other features can be queried by calling the respective ioctl, for
30 :ref:`VIDIOC_QUERYCAP` ioctl also allows driver
34 Applications should always call this ioctl after opening the device.
|
| D | vidioc-g-input.rst | 7 ioctl VIDIOC_G_INPUT, VIDIOC_S_INPUT
20 ``int ioctl(int fd, VIDIOC_G_INPUT, int *argp)``
24 ``int ioctl(int fd, VIDIOC_S_INPUT, int *argp)``
39 :ref:`VIDIOC_G_INPUT <VIDIOC_G_INPUT>` ioctl with a pointer to an integer where the driver
41 :c:type:`v4l2_input` ``index`` field. This ioctl will fail
45 input in an integer and call the :ref:`VIDIOC_S_INPUT <VIDIOC_G_INPUT>` ioctl with a pointer
53 :ref:`VIDIOC_ENUMINPUT` ioctl.
|
| D | vidioc-g-output.rst | 7 ioctl VIDIOC_G_OUTPUT, VIDIOC_S_OUTPUT
20 ``int ioctl(int fd, VIDIOC_G_OUTPUT, int *argp)``
24 ``int ioctl(int fd, VIDIOC_S_OUTPUT, int *argp)``
39 :ref:`VIDIOC_G_OUTPUT <VIDIOC_G_OUTPUT>` ioctl with a pointer to an integer where the driver
41 :c:type:`v4l2_output` ``index`` field. This ioctl will
46 output in an integer and call the :ref:`VIDIOC_S_OUTPUT <VIDIOC_G_OUTPUT>` ioctl with a
54 :ref:`VIDIOC_ENUMOUTPUT` ioctl.
|
| D | dev-osd.rst | 23 the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl.
32 :ref:`VIDIOC_QUERYCAP` ioctl.
42 the :ref:`VIDIOC_G_FBUF <VIDIOC_G_FBUF>` ioctl. It returns, amongst
45 The framebuffer device ioctl ``FBIOGET_FSCREENINFO`` returns the same
48 ioctl and struct :c:type:`fb_fix_screeninfo` are defined in
53 (or any other ioctl which would imply a framebuffer size change) with an
67 if (-1 == ioctl(fd, VIDIOC_G_FBUF, &fbuf)) {
91 if (0 == ioctl(fb_fd, FBIOGET_FSCREENINFO, &si)) {
123 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl. The driver fills the
130 substructure and call the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl.
[all …]
|
| /Documentation/userspace-api/media/mediactl/ |
| D | request-func-ioctl.rst | 4 .. _request-func-ioctl:
7 request ioctl()
13 request-ioctl - Control a request file descriptor
20 #include <sys/ioctl.h>
22 ``int ioctl(int fd, int cmd, void *argp)``
31 The request ioctl command code as defined in the media.h header file, for
40 The :ref:`ioctl() <request-func-ioctl>` function manipulates request
43 The ioctl ``cmd`` code specifies the request function to be called. It
47 Macros and structures definitions specifying request ioctl commands and
48 their parameters are located in the media.h header file. All request ioctl
[all …]
|
| D | media-func-ioctl.rst | 4 .. _media-func-ioctl:
7 media ioctl()
13 media-ioctl - Control a media device
20 #include <sys/ioctl.h>
22 ``int ioctl(int fd, int request, void *argp)``
31 Media ioctl request code as defined in the media.h header file, for
40 The :ref:`ioctl() <media-func-ioctl>` function manipulates media device
43 The ioctl ``request`` code specifies the media function to be called. It
47 Macros and structures definitions specifying media ioctl requests and
48 their parameters are located in the media.h header file. All media ioctl
[all …]
|
| /Documentation/userspace-api/media/cec/ |
| D | cec-func-ioctl.rst | 4 .. _cec-func-ioctl:
7 cec ioctl()
13 cec-ioctl - Control a cec device
20 #include <sys/ioctl.h>
22 ``int ioctl(int fd, int request, void *argp)``
31 CEC ioctl request code as defined in the cec.h header file, for
40 The :c:func:`ioctl()` function manipulates cec device parameters. The
43 The ioctl ``request`` code specifies the cec function to be called. It
47 Macros and structures definitions specifying cec ioctl requests and
48 their parameters are located in the cec.h header file. All cec ioctl
[all …]
|
| D | cec-ioc-adap-g-phys-addr.rst | 22 ``int ioctl(int fd, CEC_ADAP_G_PHYS_ADDR, __u16 *argp)``
26 ``int ioctl(int fd, CEC_ADAP_S_PHYS_ADDR, __u16 *argp)``
41 :ref:`ioctl CEC_ADAP_G_PHYS_ADDR <CEC_ADAP_G_PHYS_ADDR>` with a pointer to a __u16 where the
45 a __u16 and call :ref:`ioctl CEC_ADAP_S_PHYS_ADDR <CEC_ADAP_S_PHYS_ADDR>` with a pointer to
46 this integer. The :ref:`ioctl CEC_ADAP_S_PHYS_ADDR <CEC_ADAP_S_PHYS_ADDR>` is only available if
48 otherwise). The :ref:`ioctl CEC_ADAP_S_PHYS_ADDR <CEC_ADAP_S_PHYS_ADDR>` can only be called
55 If logical address types have been defined (see :ref:`ioctl CEC_ADAP_S_LOG_ADDRS <CEC_ADAP_S_LOG_AD…
56 then this ioctl will block until all
83 The :ref:`ioctl CEC_ADAP_S_PHYS_ADDR <CEC_ADAP_S_PHYS_ADDR>` can return the following
87 The ``CEC_CAP_PHYS_ADDR`` capability wasn't set, so this ioctl is not supported.
|
| /Documentation/userspace-api/ioctl/ |
| D | cdrom.rst | 2 Summary of CDROM ioctl calls
9 This document attempts to describe the ioctl(2) calls supported by
13 ioctl values are listed in <linux/cdrom.h>. As of this writing, they
83 Unless otherwise specified, all ioctl calls return 0 on success
87 Unless otherwise specified, all ioctl calls return -1 and set
105 ioctl(fd, CDROMPAUSE, 0);
126 ioctl(fd, CDROMRESUME, 0);
151 ioctl(fd, CDROMPLAYMSF, &msf);
182 ioctl(fd, CDROMPLAYTRKIND, &ti);
211 ioctl(fd, CDROMREADTOCHDR, &header);
[all …]
|
| /Documentation/driver-api/tty/ |
| D | n_gsm.rst | 26 ``TIOCSETD`` ioctl.
28 #. Configure the mux using ``GSMIOC_GETCONF_EXT``/``GSMIOC_SETCONF_EXT`` ioctl if needed.
30 #. Configure the mux using ``GSMIOC_GETCONF``/``GSMIOC_SETCONF`` ioctl.
32 #. Configure DLCs using ``GSMIOC_GETCONF_DLCI``/``GSMIOC_SETCONF_DLCI`` ioctl for non-defaults.
69 ioctl(fd, TIOCSETD, &ldisc);
72 ioctl(fd, GSMIOC_GETCONF_EXT, &ce);
76 ioctl(fd, GSMIOC_SETCONF_EXT, &ce);
78 ioctl(fd, GSMIOC_GETCONF, &c);
86 ioctl(fd, GSMIOC_SETCONF, &c);
89 ioctl(fd, GSMIOC_GETCONF_DLCI, &dc);
[all …]
|
| /Documentation/translations/zh_CN/video4linux/ |
| D | omap3isp.txt | 104 通过 VIDIOC_OMAP3ISP_STAT_REQ IOCTL 操作获取时，就会产生一个
111 这些 ioctl 的事件数据类型为 struct omap3isp_stat_event_status
117 私有 IOCTL
120 OMAP 3 ISP 驱动支持标准的 V4L2 IOCTL 以及可能存在且实用的控制。但
121 ISP 提供的许多功能都不在标准 IOCTL 之列，例如 gamma（伽马）表和统计
124 通常，会有一个私有 ioctl 用于配置每个包含硬件依赖功能的模块。
126 支持以下私有 IOCTL：
136 在 include/linux/omap3isp.h 中描述了这些 ioctl 使用的参数结构体。
140 虽然在不使用任何私有 IOCTL 的情况下使用 ISP 驱动是可能的，但这样无法
142 控制，以及图像均衡等）模块无法在未使用适当的私有 IOCTL 配置的情况下使用。
[all …]
|
| /Documentation/userspace-api/gpio/ |
| D | chardev_v1.rst | 38 Lines are requested from the chip using either gpio-get-linehandle-ioctl.rst
40 gpio-get-lineevent-ioctl.rst and the resulting line event is used to monitor
54 Get Line Handle <gpio-get-linehandle-ioctl>
55 Get Line Event <gpio-get-lineevent-ioctl>
56 Get Chip Info <gpio-get-chipinfo-ioctl>
57 Get Line Info <gpio-get-lineinfo-ioctl>
58 Watch Line Info <gpio-get-lineinfo-watch-ioctl>
59 Unwatch Line Info <gpio-get-lineinfo-unwatch-ioctl>
67 Line handles are created by gpio-get-linehandle-ioctl.rst and provide
70 :c:type:`request.fd<gpiohandle_request>` by gpio-get-linehandle-ioctl.rst.
[all …]
|
| D | chardev.rst | 43 Lines are requested from the chip using gpio-v2-get-line-ioctl.rst
58 Get Line <gpio-v2-get-line-ioctl>
59 Get Chip Info <gpio-get-chipinfo-ioctl>
60 Get Line Info <gpio-v2-get-lineinfo-ioctl>
61 Watch Line Info <gpio-v2-get-lineinfo-watch-ioctl>
62 Unwatch Line Info <gpio-get-lineinfo-unwatch-ioctl>
70 Line requests are created by gpio-v2-get-line-ioctl.rst and provide
73 :c:type:`request.fd<gpio_v2_line_request>` by gpio-v2-get-line-ioctl.rst.
86 Get Line Values <gpio-v2-line-get-values-ioctl>
87 Set Line Values <gpio-v2-line-set-values-ioctl>
[all …]
|
| /Documentation/userspace-api/media/ |
| D | gen-errors.rst | 22 - The ioctl can't be handled because the device is in state where it
24 device is sleeping and ioctl is performed to query statistics. It
25 is also returned when the ioctl would need to wait for an event,
34 - The ioctl can't be handled because the device is busy. This is
35 typically return while device is streaming, and an ioctl tried to
38 ioctl must not be retried without performing another action to fix
48 - One or more of the ioctl parameters are invalid or out of the
50 individual ioctl requests for specific causes.
62 - The ioctl is not supported by the file descriptor.
66 - On USB devices, the stream ioctl's can return this error, meaning
|
| /Documentation/input/ |
| D | uinput.rst | 73 ioctl(fd, UI_SET_EVBIT, EV_KEY);
74 ioctl(fd, UI_SET_KEYBIT, KEY_SPACE);
82 ioctl(fd, UI_DEV_SETUP, &usetup);
83 ioctl(fd, UI_DEV_CREATE);
106 ioctl(fd, UI_DEV_DESTROY);
132 ioctl(fd, UI_SET_EVBIT, EV_KEY);
133 ioctl(fd, UI_SET_KEYBIT, BTN_LEFT);
135 ioctl(fd, UI_SET_EVBIT, EV_REL);
136 ioctl(fd, UI_SET_RELBIT, REL_X);
137 ioctl(fd, UI_SET_RELBIT, REL_Y);
[all …]
|
| /Documentation/virt/coco/ |
| D | tdx-guest.rst | 10 The TDX guest driver exposes IOCTL interfaces via the /dev/tdx-guest misc
16 In this section, for each supported IOCTL, the following information is
19 :Input parameters: Parameters passed to the IOCTL and related details.
32 The TDX_CMD_GET_REPORT0 IOCTL can be used by the attestation software to get
36 A subtype index is added at the end of this IOCTL CMD to uniquely identify the
39 currently used, and it expects this value to be 0. So to keep the IOCTL
42 a new IOCTL CMD will be created to handle it. To keep the IOCTL naming
43 consistent, a subtype index is added as part of the IOCTL CMD.
|
| D | sev-guest.rst | 15 whole SEV firmware. These ioctl are used by platform provisioning tools.
23 from the SEV firmware. For each ioctl, the following information is provided
27 which SEV technology provides this ioctl. SEV, SEV-ES, SEV-SNP or all.
30 hypervisor or guest. The ioctl can be used inside the guest or the
34 what parameters are accepted by the ioctl.
40 The guest ioctl should be issued on a file descriptor of the /dev/sev-guest
41 device. The ioctl accepts struct snp_user_guest_request. The input and
43 respectively. If the ioctl fails to execute due to a firmware error, then
71 The ioctl accepts the command ID/input structure documented below.
91 :Type: guest ioctl
[all …]
|
| /Documentation/gpu/imagination/ |
| D | uapi.rst | 20 :doc: PowerVR IOCTL interface
28 :doc: PowerVR IOCTL DEV_QUERY interface
56 :doc: PowerVR IOCTL CREATE_BO interface
67 :doc: PowerVR IOCTL GET_BO_MMAP_OFFSET interface
75 :doc: PowerVR IOCTL CREATE_VM_CONTEXT and DESTROY_VM_CONTEXT interfaces
84 :doc: PowerVR IOCTL VM_MAP and VM_UNMAP interfaces
93 :doc: PowerVR IOCTL CREATE_CONTEXT and DESTROY_CONTEXT interfaces
112 :doc: PowerVR IOCTL CREATE_FREE_LIST and DESTROY_FREE_LIST interfaces
123 :doc: PowerVR IOCTL CREATE_HWRT_DATASET and DESTROY_HWRT_DATASET interfaces
138 :doc: PowerVR IOCTL SUBMIT_JOBS interface
[all …]
|
| /Documentation/translations/zh_CN/dev-tools/ |
| D | kcov.rst | 57 #include <sys/ioctl.h>
83 if (ioctl(fd, KCOV_INIT_TRACE, COVER_SIZE))
84 perror("ioctl"), exit(1);
91 if (ioctl(fd, KCOV_ENABLE, KCOV_TRACE_PC))
92 perror("ioctl"), exit(1);
93 /* 在调用 ioctl() 之后重置覆盖率。 */
104 if (ioctl(fd, KCOV_DISABLE, 0))
105 perror("ioctl"), exit(1);
171 if (ioctl(fd, KCOV_INIT_TRACE, COVER_SIZE))
172 perror("ioctl"), exit(1);
[all …]
|
| /Documentation/userspace-api/media/rc/ |
| D | lirc-get-features.rst | 7 ioctl LIRC_GET_FEATURES
20 ``int ioctl(int fd, LIRC_GET_FEATURES, __u32 *features)``
82 :ref:`ioctl LIRC_SET_SEND_CARRIER <LIRC_SET_SEND_CARRIER>`.
89 :ref:`ioctl LIRC_SET_SEND_DUTY_CYCLE <LIRC_SET_SEND_DUTY_CYCLE>`.
96 :ref:`ioctl LIRC_SET_TRANSMITTER_MASK <LIRC_SET_TRANSMITTER_MASK>`.
103 :ref:`ioctl LIRC_SET_REC_CARRIER <LIRC_SET_REC_CARRIER>`.
110 :ref:`ioctl LIRC_SET_REC_CARRIER_RANGE <LIRC_SET_REC_CARRIER_RANGE>`.
117 :ref:`ioctl LIRC_GET_REC_RESOLUTION <LIRC_GET_REC_RESOLUTION>`.
124 :ref:`ioctl LIRC_SET_REC_TIMEOUT <LIRC_SET_REC_TIMEOUT>`.
131 :ref:`ioctl LIRC_SET_MEASURE_CARRIER_MODE <LIRC_SET_MEASURE_CARRIER_MODE>`.
[all …]
|
| /Documentation/userspace-api/media/dvb/ |
| D | dmx-reqbufs.rst | 7 ioctl DMX_REQBUFS
22 ``int ioctl(int fd, DMX_REQBUFS, struct dmx_requestbuffers *argp)``
36 This ioctl is used to initiate a memory mapped or DMABUF based demux I/O.
39 with this ioctl before they can be mapped into the application's address
41 ioctl is merely used to switch the driver into user pointer I/O mode and
43 allocated by applications through a device driver, and this ioctl only
52 When the ioctl is called with a pointer to this structure, the driver will
59 When this I/O method is not supported, the ioctl returns an ``EOPNOTSUPP``
|
| /Documentation/translations/it_IT/process/ |
| D | botching-up-ioctls.rst | 6 (Come evitare di) Raffazzonare delle ioctl
16 oggigiorno ogni driver ha il suo insieme di ioctl per allocare memoria ed
24 riguardo al modo migliore per implementare una ioctl per inviare compiti alla
67 * Abbiate un modo chiaro per capire dallo spazio utente se una nuova ioctl, o
70 un nuovo *flag*, modalità, o ioctl, (probabilmente perché avevate raffazzonato
75 * Abbiate un piano per estendere le ioctl con nuovi *flag* o campi alla fine di
76 una struttura dati. Il sistema drm verifica la dimensione di ogni ioctl in
84 altrimenti rifiutare la ioctl. Se non lo fate il vostro bel piano per
85 estendere le ioctl andrà a rotoli dato che qualcuno userà delle ioctl con
104 * Le ioctl devono verificare l'overflow dei vettori. Inoltre, per i valori
[all …]
|
| /Documentation/misc-devices/ |
| D | xilinx_sdfec.rst | 81 …- unlocked_ioctl: Provides the following ioctl commands that allows the application configure the …
128 Determine the configuration of the SD-FEC core by using the ioctl
136 Setting the order is done by using the ioctl :c:macro:`XSDFEC_SET_ORDER`
140 …- The ``state`` member of struct :c:type:`xsdfec_status <xsdfec_status>` filled by the ioctl :c:ma…
151 - Add the LPDC Code Parameters using the ioctl :c:macro:`XSDFEC_ADD_LDPC_CODE_PARAMS`
157 …- The ``code`` member of :c:type:`struct xsdfec_config <xsdfec_config>` filled by the ioctl :c:mac…
158 …- The ``code_wr_protect`` of :c:type:`struct xsdfec_config <xsdfec_config>` filled by the ioctl :c…
159 …- The ``state`` member of struct :c:type:`xsdfec_status <xsdfec_status>` filled by the ioctl :c:ma…
164 Configuring the Turbo decode parameters is done by using the ioctl :c:macro:`XSDFEC_SET_TURBO` usin…
168 …- The ``code`` member of :c:type:`struct xsdfec_config <xsdfec_config>` filled by the ioctl :c:mac…
[all …]
|
| /Documentation/watchdog/ |
| D | watchdog-api.rst | 73 The ioctl API
76 All conforming drivers also support an ioctl API.
78 Pinging the watchdog using an ioctl:
80 All drivers that have an ioctl interface support at least one ioctl,
81 KEEPALIVE. This ioctl does exactly the same thing as a write to the
86 ioctl(fd, WDIOC_KEEPALIVE, 0);
90 the argument to the ioctl is ignored.
96 fly with the SETTIMEOUT ioctl, those drivers have the WDIOF_SETTIMEOUT
103 ioctl(fd, WDIOC_SETTIMEOUT, &timeout);
110 current timeout using the GETTIMEOUT ioctl::
[all …]
|