Lines Matching full:request

36 MEDIA_REQUEST_IOC_QUEUE - Queue a request
56 If the media device supports :ref:`requests <media-request-api>`, then
57 this request ioctl can be used to queue a previously allocated request.
59 If the request was successfully queued, then the file descriptor can be
60 :ref:`polled <request-func-poll>` to wait for the request to complete.
62 If the request was already queued before, then ``EBUSY`` is returned.
63 Other errors can be returned if the contents of the request contained
65 common error codes. On error both the request and driver state are unchanged.
67 Once a request is queued, then the driver is required to gracefully handle
68 errors that occur when the request is applied to the hardware. The
73 (without a request). ``EBUSY`` will be returned if the first buffer was
74 queued directly and you next try to queue a request, or vice versa.
76 A request must contain at least one buffer, otherwise this ioctl will
87     The request was already queued or the application queued the first
88     buffer directly, but later attempted to use a request. It is not permitted
91     The request did not contain any buffers. All requests are required
93     configuration is missing in the request.
96     request.
98     The request has invalid data.