@@ -76,6 +76,11 @@ queued directly and you next try to queue a request, or vice versa.
A request must contain at least one buffer, otherwise this ioctl will
return an ``ENOENT`` error.
+If the :ref:`buffer capabilities <v4l2-buf-capabilities>` indicate that
+only read-only requests are supported, then the request can only contain
+buffers. If anything else is present then this ioctl will return an
+``EINVAL`` error.
+
Return Value
============
@@ -53,6 +53,13 @@ with different configurations in advance, knowing that the configuration will be
applied when needed to get the expected result. Configuration values at the time
of request completion are also available for reading.
+In some cases it does not make sense for user-space to associate configuration
+values with a frame, instead it only makes sense to retrieving configuration
+values at the time of request completion. In that case read-only requests can be
+used that only allow buffers to be queued and not configuration values. Which
+type of requests (regular or read-only) are supported is signalled through
+:ref:`buffer capabilities <v4l2-buf-capabilities>`.
+
General Usage
-------------
@@ -95,6 +102,10 @@ A queued request cannot be modified anymore.
output buffers, not for capture buffers. Attempting to add a capture buffer
to a request will result in an ``EBADR`` error.
+If the buffer type supports only read-only requests, and the request contains
+configuration values such as controls, then ``EINVAL`` is returned since no
+configuration values are allowed when submitting a read-only request.
+
If the request contains configurations for multiple entities, individual drivers
may synchronize so the requested pipeline's topology is applied before the
buffers are processed. Media controller drivers do a best effort implementation
@@ -134,6 +134,7 @@ aborting or finishing any DMA in progress, an implicit
.. _V4L2-BUF-CAP-SUPPORTS-ORPHANED-BUFS:
.. _V4L2-BUF-CAP-SUPPORTS-M2M-HOLD-CAPTURE-BUF:
.. _V4L2-BUF-CAP-SUPPORTS-MMAP-CACHE-HINTS:
+.. _V4L2-BUF-CAP-SUPPORTS-RO-REQUESTS:
.. cssclass:: longtable
@@ -154,6 +155,7 @@ aborting or finishing any DMA in progress, an implicit
* - ``V4L2_BUF_CAP_SUPPORTS_REQUESTS``
- 0x00000008
- This buffer type supports :ref:`requests <media-request-api>`.
+ This flag is mutually exclusive with ``V4L2_BUF_CAP_SUPPORTS_RO_REQUESTS``.
* - ``V4L2_BUF_CAP_SUPPORTS_ORPHANED_BUFS``
- 0x00000010
- The kernel allows calling :ref:`VIDIOC_REQBUFS` while buffers are still
@@ -172,6 +174,10 @@ aborting or finishing any DMA in progress, an implicit
:ref:`V4L2_FLAG_MEMORY_NON_CONSISTENT <V4L2-FLAG-MEMORY-NON-CONSISTENT>`,
:ref:`V4L2_BUF_FLAG_NO_CACHE_INVALIDATE <V4L2-BUF-FLAG-NO-CACHE-INVALIDATE>` and
:ref:`V4L2_BUF_FLAG_NO_CACHE_CLEAN <V4L2-BUF-FLAG-NO-CACHE-CLEAN>`.
+ * - ``V4L2_BUF_CAP_SUPPORTS_RO_REQUESTS``
+ - 0x00000080
+ - This buffer type supports read-only :ref:`requests <media-request-api>`.
+ This flag is mutually exclusive with ``V4L2_BUF_CAP_SUPPORTS_REQUESTS``.
Return Value
This patch documents reaed-only requests, including the new V4L2_BUF_CAP_SUPPORTS_RO_REQUESTS capability flag. Based in part on a patch from Yunfei Dong <yunfei.dong@mediatek.com>. Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl> --- .../media/mediactl/media-request-ioc-queue.rst | 5 +++++ .../userspace-api/media/mediactl/request-api.rst | 11 +++++++++++ .../userspace-api/media/v4l/vidioc-reqbufs.rst | 6 ++++++ 3 files changed, 22 insertions(+)