Home
last modified time | relevance | path

Searched refs:request_fd (Results 1 – 7 of 7) sorted by relevance

/linux/Documentation/userspace-api/media/mediactl/
H A Dmedia-request-ioc-reinit.rst20 ``int ioctl(int request_fd, MEDIA_REQUEST_IOC_REINIT)``
25 ``request_fd``
H A Drequest-api.rst42 request support, such as V4L2 APIs that take an explicit ``request_fd``
58 support this. Configurations set with a ``request_fd`` parameter are stored
152 ctrls.request_fd = req_fd;
158 buf.request_fd = req_fd;
201 ctrls.request_fd = req_fd;
235 ctrls.request_fd = req_fd;
241 buf.request_fd = req_fd;
H A Dmedia-request-ioc-queue.rst20 ``int ioctl(int request_fd, MEDIA_REQUEST_IOC_QUEUE)``
25 ``request_fd``
/linux/drivers/media/mc/
H A Dmc-request.c254 media_request_get_by_fd(struct media_device *mdev, int request_fd) in media_request_get_by_fd() argument
262 CLASS(fd, f)(request_fd); in media_request_get_by_fd()
284 dev_dbg(mdev->dev, "cannot find request_fd %d\n", request_fd); in media_request_get_by_fd()
/linux/Documentation/userspace-api/media/v4l/
H A Dvidioc-qbuf.rst101 The ``request_fd`` field can be used with the ``VIDIOC_QBUF`` ioctl to specify
120 ``request_fd`` only for output buffers, not for capture buffers. Attempting
166 set but the given ``request_fd`` was invalid, or ``m.fd`` was
H A Ddev-stateless-decoder.rst276 ``request_fd``
296 ``request_fd``
308 long as ``request_fd`` and ``which`` are properly set. The controls state
H A Dbuffer.rst292 - ``request_fd``
609 - The ``request_fd`` field contains a valid file descriptor.