Home
last modified time | relevance | path

Searched full:ioctl (Results 1 – 25 of 1660) sorted by relevance

12345678910>>...67

/linux/include/drm/
H A Ddrm_ioctl.h38 #include <asm/ioctl.h>
45 * drm_ioctl_t - DRM ioctl function type.
47 * @data: private pointer of the ioctl call
48 * @file_priv: DRM file this ioctl was made on
50 * This is the DRM ioctl typedef. Note that drm_ioctl() has alrady copied @data
52 * settings in the ioctl command code.
58 * drm_ioctl_compat_t - compatibility DRM ioctl function type.
60 * @cmd: ioctl command code
61 * @arg: DRM file this ioctl was made on
64 * New drivers shouldn't screw up the structure layout for their ioctl
[all …]
/linux/Documentation/userspace-api/ioctl/
H A Dcdrom.rst2 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 …]
/linux/Documentation/driver-api/tty/
H A Dn_gsm.rst26 ``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 …]
/linux/Documentation/translations/zh_CN/video4linux/
H A Domap3isp.txt104 通过 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 …]
/linux/Documentation/userspace-api/media/v4l/
H A Dfunc-ioctl.rst4 .. _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 …]
/linux/Documentation/userspace-api/media/mediactl/
H A Dmedia-func-ioctl.rst4 .. _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 …]
H A Drequest-func-ioctl.rst4 .. _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 …]
/linux/include/uapi/linux/
H A Dloop.h38 int lo_number; /* ioctl r/o */
39 __kernel_old_dev_t lo_device; /* ioctl r/o */
40 unsigned long lo_inode; /* ioctl r/o */
41 __kernel_old_dev_t lo_rdevice; /* ioctl r/o */
44 int lo_encrypt_key_size; /* ioctl w/o */
47 unsigned char lo_encrypt_key[LO_KEY_SIZE]; /* ioctl w/o */
53 __u64 lo_device; /* ioctl r/o */
54 __u64 lo_inode; /* ioctl r/o */
55 __u64 lo_rdevice; /* ioctl r/o */
58 __u32 lo_number; /* ioctl r/o */
[all …]
H A Duinput.h26 * - add UI_DEV_SETUP ioctl
27 * - add UI_ABS_SETUP ioctl
28 * - add UI_GET_VERSION ioctl
30 * - add UI_GET_SYSNAME ioctl
62 /* ioctl */
76 * This ioctl sets parameters for the input device to be created. It
81 * The ioctl takes a "struct uinput_setup" object as argument. The fields of
89 * This ioctl can be called multiple times and will overwrite previous values.
90 * If this ioctl fails with -EINVAL, it is recommended to use the old
92 * old kernel that does not support this ioctl.
[all …]
H A Dmei.h13 * This IOCTL is used to associate the current file descriptor with a
20 * The IOCTL argument is a struct with a union that contains
21 * the input parameter and the output parameter for this IOCTL.
41 * IOCTL Connect Client Data structure
53 * The IOCTL argument is 1 for enabling event notification and 0 for
62 * The IOCTL output argument is 1 if an event was pending and 0 otherwise.
63 * The ioctl has to be called in order to acknowledge pending event.
83 * struct mei_connect_client_data_vtag - IOCTL connect data union
97 * This IOCTL is used to associate the current file descriptor with a
99 * The IOCTL opens a communication channel between a host client and
[all …]
/linux/Documentation/userspace-api/gpio/
H A Dchardev_v1.rst38 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 …]
/linux/include/uapi/drm/
H A Dvmwgfx_drm.h89 * Does the driver support the overlay ioctl.
138 * Argument to the DRM_VMW_GET_PARAM Ioctl.
160 * Output argument to the DRM_VMW_CREATE_CONTEXT Ioctl.
161 * Input argument to the DRM_VMW_UNREF_CONTEXT Ioctl.
203 * Input data to the DRM_VMW_CREATE_SURFACE Ioctl.
204 * Output data from the DRM_VMW_REF_SURFACE Ioctl.
220 * @handle_type: Handle type for DRM_VMW_REF_SURFACE Ioctl.
222 * Output data from the DRM_VMW_CREATE_SURFACE Ioctl.
223 * Input argument to the DRM_VMW_UNREF_SURFACE Ioctl.
224 * Input argument to the DRM_VMW_REF_SURFACE Ioctl.
[all …]
/linux/tools/testing/selftests/powerpc/ptrace/
H A Dperf-hwbreak.c29 #include <sys/ioctl.h>
126 ioctl(fd[i], PERF_EVENT_IOC_RESET); in reset_fds()
134 ioctl(fd[i], PERF_EVENT_IOC_ENABLE); in enable_fds()
142 ioctl(fd[i], PERF_EVENT_IOC_DISABLE); in disable_fds()
255 ioctl(break_fd, PERF_EVENT_IOC_ENABLE); in runtestsingle()
268 ioctl(break_fd, PERF_EVENT_IOC_DISABLE); in runtestsingle()
317 ioctl(break_fd, PERF_EVENT_IOC_RESET); in runtest_dar_outside()
318 ioctl(break_fd, PERF_EVENT_IOC_ENABLE); in runtest_dar_outside()
321 ioctl(break_fd, PERF_EVENT_IOC_DISABLE); in runtest_dar_outside()
332 ioctl(break_fd, PERF_EVENT_IOC_RESET); in runtest_dar_outside()
[all …]
/linux/Documentation/userspace-api/media/cec/
H A Dcec-func-ioctl.rst4 .. _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 …]
/linux/Documentation/input/
H A Duinput.rst73 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 …]
/linux/tools/testing/selftests/rtc/
H A Drtctest.c13 #include <sys/ioctl.h>
56 rc = ioctl(self->fd, RTC_RD_TIME, &rtc_tm); in TEST_F()
100 rc = ioctl(fd, RTC_PARAM_GET, &param); in get_rtc_alarm_state()
127 rc = ioctl(self->fd, RTC_RD_TIME, &rtc_tm);
135 rc = ioctl(self->fd, RTC_RD_TIME, &rtc_tm);
163 rc = ioctl(self->fd, RTC_UIE_ON, 0);
179 rc = ioctl(self->fd, RTC_UIE_OFF, 0);
192 rc = ioctl(self->fd, RTC_UIE_ON, 0); in TEST_F()
218 rc = ioctl(self->fd, RTC_UIE_OFF, 0); in TEST_F()
241 rc = ioctl(self->fd, RTC_RD_TIME, &tm); in TEST_F()
[all …]
/linux/drivers/scsi/esas2r/
H A Desas2r_ioctl.c49 * Buffered ioctl handlers. A buffered ioctl is one which requires that we
53 * it for subsequent ioctl calls that require it.
71 void *ioctl; member
110 /* Handle EXPRESS_IOCTL_RW_FIRMWARE ioctl with img_type = FW_IMG_FM_API. */
243 "for a buffered ioctl!", in handle_buffered_ioctl()
246 esas2r_debug("buffered ioctl alloc failure"); in handle_buffered_ioctl()
251 memcpy(esas2r_buffered_ioctl, bi->ioctl, bi->length); in handle_buffered_ioctl()
259 esas2r_debug("buffered ioctl - no requests"); in handle_buffered_ioctl()
288 memcpy(bi->ioctl, esas2r_buffered_ioctl, bi->length); in handle_buffered_ioctl()
294 /* SMP ioctl support */
[all …]
/linux/Documentation/translations/it_IT/process/
H A Dbotching-up-ioctls.rst6 (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 …]
/linux/Documentation/virt/coco/
H A Dsev-guest.rst15 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 …]
/linux/Documentation/translations/zh_CN/dev-tools/
H A Dkcov.rst57 #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 …]
/linux/drivers/platform/x86/intel/speed_select_if/
H A Disst_if_common.h24 * This is enough to handle command to every core in one ioctl, or all
26 * per IOCTL request, as PUNIT may take different times to process each
40 * struct isst_if_cmd_cb - Used to register a IOCTL handler
43 * @cmd_size: The command size of the individual command in IOCTL
49 * @cmd_callback: Callback function to handle IOCTL. The callback has the
52 * response to user ioctl buffer. The "resume" argument
55 * @def_ioctl: Default IOCTL handler callback, if there is no match in
56 * the existing list of IOCTL handled by the common handler.
58 * This structure is used to register an handler for IOCTL. To avoid
59 * code duplication common code handles all the IOCTL command read/write
[all …]
/linux/Documentation/misc-devices/
H A Dxilinx_sdfec.rst81 …- 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 …]
/linux/Documentation/gpu/imagination/
H A Duapi.rst20 :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 …]
/linux/Documentation/watchdog/
H A Dwatchdog-api.rst73 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 …]
/linux/Documentation/userspace-api/media/
H A Dgen-errors.rst22 - 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

12345678910>>...67