Home
last modified time | relevance | path

Searched refs:IOCTL (Results 1 – 25 of 60) sorted by relevance

123

/openbmc/qemu/linux-user/
H A Dioctls.h14 IOCTL(TCSBRK, 0, TYPE_INT) in IOCTL()
15 IOCTL(TCSBRKP, 0, TYPE_INT) in IOCTL()
16 IOCTL(TCXONC, 0, TYPE_INT) in IOCTL()
17 IOCTL(TCFLSH, 0, TYPE_INT) in IOCTL()
18 IOCTL(TIOCEXCL, 0, TYPE_NULL) in IOCTL()
19 IOCTL(TIOCNXCL, 0, TYPE_NULL) in IOCTL()
20 IOCTL(TIOCSCTTY, 0, TYPE_INT) in IOCTL()
33 IOCTL(TIOCCONS, 0, TYPE_NULL) in IOCTL()
46 IOCTL(FIOCLEX, 0, TYPE_NULL) in IOCTL()
59 IOCTL(KDMKTONE, 0, TYPE_INT) in IOCTL()
[all …]
/openbmc/linux/Documentation/translations/zh_CN/video4linux/
H A Domap3isp.txt117 私有 IOCTL
126 支持以下私有 IOCTL：
140 虽然在不使用任何私有 IOCTL 的情况下使用 ISP 驱动是可能的，但这样无法
142 控制，以及图像均衡等）模块无法在未使用适当的私有 IOCTL 配置的情况下使用。
145 CCDC 和 preview（预览）模块 IOCTL
150 所控制的模块中，两个 IOCTL 控制多种功能。VIDIOC_OMAP3ISP_CCDC_CFG IOCTL
163 中的有效值。 这些值可能会在同一个 IOCTL 调用中配置多个功能。
198 统计模块 IOCTL
205 统计数据可由用户通过统计子设备节点使用私有 IOCTL 获取。
220 这些 IOCTL 用于配置模块。它们要求用户应用程序对硬件有深入的认识。对
[all …]
/openbmc/linux/Documentation/virt/coco/
H A Dtdx-guest.rst10 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.
/openbmc/linux/Documentation/driver-api/xilinx/
H A Deemi.rst22 IOCTL section in Xilinx Zynq MPSoC EEMI Documentation
24 IOCTL API is for device control and configuration. It is not a system
25 IOCTL but it is an EEMI API. This API can be used by master to control
26 any device specific configuration. IOCTL definitions can be platform
29 The following IOCTL IDs are valid for device control:
35 Refer EEMI API guide [0] for IOCTL specific parameters and other EEMI APIs.
/openbmc/linux/drivers/staging/pi433/
H A DTODO7 IOCTL. Going forward, we need to port userspace tools to use sysfs instead
8 of IOCTL and then we would delete IOCTL.
/openbmc/linux/Documentation/driver-api/surface_aggregator/clients/
H A Dcdev.rst35 registered via the ``SSAM_CDEV_NOTIF_REGISTER`` IOCTL. Notifiers are, in
42 be necessary to enable events via the ``SSAM_CDEV_EVENT_ENABLE`` IOCTL. While
113 by the IOCTL to return status and result of the request.
131 indication of the IOCTL is separated from failure indication of the request:
132 The IOCTL returns a negative status code if anything failed during setup of
136 ``-ENOMEM`` for out-of-memory), but this value may also be zero. The IOCTL
139 inside the IOCTL, but the request ``status`` member may still be negative in
155 ``SSAM_CDEV_EVENT_ENABLE`` IOCTL, before the EC will send them.
169 priority field will be ignored by this IOCTL. If no notifier has been
170 registered for this client instance and the given category, this IOCTL will
[all …]
/openbmc/linux/Documentation/gpu/rfc/
H A Di915_scheduler.rst28 a slot in a single execbuf IOCTL and the batches run on the GPU in
107 * Extend execbuf2 IOCTL to support submitting N BBs in a single IOCTL
114 logical mapping with the existing query engine info IOCTL. Also the GuC
131 execbuf2 IOCTL can be called submitting N BBs in a single IOCTL. Initially only
145 Extend execbuf2 IOCTL to support submitting N BBs in a single IOCTL
148 submit N BBs in a single execbuf2 IOCTL. The BBs are either the last N objects
152 required to the execbuf2 IOCTL.
/openbmc/linux/drivers/tty/serial/jsm/
H A Djsm_tty.c32 jsm_dbg(IOCTL, &ch->ch_bd->pci_dev, "start\n"); in jsm_get_mstat()
51 jsm_dbg(IOCTL, &ch->ch_bd->pci_dev, "finish\n"); in jsm_get_mstat()
69 jsm_dbg(IOCTL, &channel->ch_bd->pci_dev, "start\n"); in jsm_tty_get_mctrl()
76 jsm_dbg(IOCTL, &channel->ch_bd->pci_dev, "finish\n"); in jsm_tty_get_mctrl()
91 jsm_dbg(IOCTL, &channel->ch_bd->pci_dev, "start\n"); in jsm_tty_set_mctrl()
105 jsm_dbg(IOCTL, &channel->ch_bd->pci_dev, "finish\n"); in jsm_tty_set_mctrl()
128 jsm_dbg(IOCTL, &channel->ch_bd->pci_dev, "start\n"); in jsm_tty_start_tx()
133 jsm_dbg(IOCTL, &channel->ch_bd->pci_dev, "finish\n"); in jsm_tty_start_tx()
141 jsm_dbg(IOCTL, &channel->ch_bd->pci_dev, "start\n"); in jsm_tty_stop_tx()
145 jsm_dbg(IOCTL, &channel->ch_bd->pci_dev, "finish\n"); in jsm_tty_stop_tx()
[all …]
/openbmc/linux/Documentation/accel/qaic/
H A Dqaic.rst77 This IOCTL allows userspace to send a NNC request to the QSM. The call will
81 This IOCTL allows userspace to allocate a buffer object (BO) which can send
87 This IOCTL allows userspace to prepare an allocated BO to be mmap'd into the
91 This IOCTL allows userspace to slice a BO in preparation for sending the BO
97 This IOCTL allows userspace to submit a set of sliced BOs to the device. The
102 This IOCTL operates like DRM_IOCTL_QAIC_EXECUTE_BO, but it allows userspace
104 typically has N inputs, but only a subset of those is available, this IOCTL
106 sent to the device to minimize data transfer overhead. This IOCTL dynamically
111 This IOCTL allows userspace to determine when a particular BO has been
116 This IOCTL allows userspace to collect performance statistics on the most
[all …]
/openbmc/linux/Documentation/userspace-api/ioctl/
H A Dioctl-decoding.rst2 Decoding an IOCTL Magic Number
5 To decode a hex IOCTL code:
/openbmc/linux/Documentation/gpu/
H A Dtegra.rst145 The ``DRM_IOCTL_TEGRA_GEM_CREATE`` IOCTL is used to create a GEM buffer object
151 IOCTL.
157 ``DRM_IOCTL_TEGRA_SYNCPT_READ`` IOCTL. Incrementing the syncpoint is achieved
158 using the ``DRM_IOCTL_TEGRA_SYNCPT_INCR`` IOCTL.
161 execute the ``DRM_IOCTL_TEGRA_SYNCPT_WAIT`` IOCTL, specifying the value of
169 channel to an engine using the ``DRM_IOCTL_TEGRA_OPEN_CHANNEL`` IOCTL. Client
172 IOCTL. To retrieve the syncpoint associated with a channel, an application
177 to the ``DRM_IOCTL_TEGRA_SUBMIT`` IOCTL along with various other parameters,
H A Ddrm-uapi.rst290 IOCTL Support on Device Nodes
296 Recommended IOCTL Return Values
299 In theory a driver's IOCTL callback is only allowed to return very few error
336 DRM drivers assume that userspace restarts all IOCTLs. Any DRM IOCTL can
337 return EINTR and in such a case should be restarted with the IOCTL
349 IOCTL also use other error codes like ETIME, EFAULT, EBUSY, ENOTTY but their
352 "this IOCTL does not exist", and is used exactly as such in DRM.
369 New cross-driver userspace interface extensions, like new IOCTL, new KMS
/openbmc/linux/Documentation/driver-api/mei/
H A Dmei.rst80 The Intel MEI Driver supports the following IOCTL commands:
107 EINVAL Wrong IOCTL Number
144 EINVAL Wrong IOCTL Number or tag == 0
172 EINVAL Wrong IOCTL Number
197 EINVAL Wrong IOCTL Number
/openbmc/linux/drivers/accel/ivpu/
H A DTODO8 - Implement BO cache and MADVISE IOCTL
/openbmc/linux/drivers/accel/qaic/
H A DKconfig17 The driver manages the PCIe devices and provides an IOCTL interface
/openbmc/linux/drivers/accel/habanalabs/
H A DKconfig20 The driver manages the PCIe devices and provides IOCTL interface for
/openbmc/linux/Documentation/userspace-api/media/drivers/
H A Domap3isp-uapi.rst34 application using the VIDIOC_OMAP3ISP_STAT_REQ IOCTL. The events available
85 control. VIDIOC_OMAP3ISP_CCDC_CFG IOCTL accepts a pointer to struct
101 function in the same IOCTL call.
156 This private IOCTL enables/disables a statistic module. If this request is
H A Duvcvideo.rst54 "IOCTL reference" below.
86 "IOCTL reference" below.
106 IOCTL reference
/openbmc/linux/drivers/infiniband/hw/hfi1/
H A Dtrace_dbg.h92 __hfi1_trace_def(IOCTL);
/openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-security/trusted-services/corstone1000/
H A D0006-plat-corstone1000-Use-the-stateless-platform-service.patch34 /* Openamp call with IOCTL for firmware update*/
52 /*openamp call with IOCTL for kernel start*/
/openbmc/linux/Documentation/scsi/
H A DChangeLog.ips21 4.80.21 - Change memcpy() to copy_to_user() in NVRAM Page 5 IOCTL path
36 - Close Window for getting too many IOCTL's active
/openbmc/linux/drivers/isdn/capi/
H A DKconfig22 of CAPI messages. This feature can be enabled/disabled via IOCTL for
/openbmc/linux/Documentation/ABI/testing/
H A Ddell-smbios-wmi9 IOCTL's and buffer formats are defined in:
/openbmc/linux/Documentation/driver-api/hte/
H A Dtegra-hte.rst31 specified during IOCTL calls. Refer to ``tools/gpio/gpio-event-mon.c``, which
/openbmc/linux/Documentation/watchdog/
H A Dpcwd-watchdog.rst36 Other IOCTL functions include:

123