diff mbox series

[1] Documentation: media: add missing V4L2_BUF_CAP_ flags

Message ID df3f1c25-5956-4273-9e0a-5db712583f30@xs4all.nl (mailing list archive)
State New
Headers show
Series [1] Documentation: media: add missing V4L2_BUF_CAP_ flags | expand

Commit Message

Hans Verkuil July 16, 2024, 12:08 p.m. UTC
The documentation for V4L2_BUF_CAP_SUPPORTS_MAX_NUM_BUFFERS and
V4L2_BUF_CAP_SUPPORTS_REMOVE_BUFS was missing. Add this.

Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
---
 Documentation/userspace-api/media/v4l/vidioc-reqbufs.rst | 7 +++++++
 1 file changed, 7 insertions(+)

Comments

Hans Verkuil July 16, 2024, 12:10 p.m. UTC | #1
That should have been just [PATCH] in the subject line :-)

On 16/07/2024 14:08, Hans Verkuil wrote:
> The documentation for V4L2_BUF_CAP_SUPPORTS_MAX_NUM_BUFFERS and
> V4L2_BUF_CAP_SUPPORTS_REMOVE_BUFS was missing. Add this.
> 
> Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
> ---
>  Documentation/userspace-api/media/v4l/vidioc-reqbufs.rst | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/Documentation/userspace-api/media/v4l/vidioc-reqbufs.rst b/Documentation/userspace-api/media/v4l/vidioc-reqbufs.rst
> index bbc22dd76032..1df3ce1fe93e 100644
> --- a/Documentation/userspace-api/media/v4l/vidioc-reqbufs.rst
> +++ b/Documentation/userspace-api/media/v4l/vidioc-reqbufs.rst
> @@ -166,6 +166,13 @@ aborting or finishing any DMA in progress, an implicit
>          :ref:`V4L2_BUF_FLAG_NO_CACHE_INVALIDATE <V4L2-BUF-FLAG-NO-CACHE-INVALIDATE>`,
>          :ref:`V4L2_BUF_FLAG_NO_CACHE_CLEAN <V4L2-BUF-FLAG-NO-CACHE-CLEAN>` and
>          :ref:`V4L2_MEMORY_FLAG_NON_COHERENT <V4L2-MEMORY-FLAG-NON-COHERENT>`.
> +    * - ``V4L2_BUF_CAP_SUPPORTS_MAX_NUM_BUFFERS``
> +      - 0x00000080
> +      - If set, then the ``max_num_buffers`` field in ``struct v4l2_create_buffers``
> +        is valid.
> +    * - ``V4L2_BUF_CAP_SUPPORTS_REMOVE_BUFS``
> +      - 0x00000100
> +      - If set, then ``VIDIOC_REMOVE_BUFS`` is supported.
> 
>  .. raw:: latex
>
Sebastian Fricke July 16, 2024, 12:21 p.m. UTC | #2
Hey Hans,

On 16.07.2024 14:08, Hans Verkuil wrote:
>The documentation for V4L2_BUF_CAP_SUPPORTS_MAX_NUM_BUFFERS and
>V4L2_BUF_CAP_SUPPORTS_REMOVE_BUFS was missing. Add this.
>
>Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
>---
> Documentation/userspace-api/media/v4l/vidioc-reqbufs.rst | 7 +++++++
> 1 file changed, 7 insertions(+)
>
>diff --git a/Documentation/userspace-api/media/v4l/vidioc-reqbufs.rst b/Documentation/userspace-api/media/v4l/vidioc-reqbufs.rst
>index bbc22dd76032..1df3ce1fe93e 100644
>--- a/Documentation/userspace-api/media/v4l/vidioc-reqbufs.rst
>+++ b/Documentation/userspace-api/media/v4l/vidioc-reqbufs.rst
>@@ -166,6 +166,13 @@ aborting or finishing any DMA in progress, an implicit
>         :ref:`V4L2_BUF_FLAG_NO_CACHE_INVALIDATE <V4L2-BUF-FLAG-NO-CACHE-INVALIDATE>`,
>         :ref:`V4L2_BUF_FLAG_NO_CACHE_CLEAN <V4L2-BUF-FLAG-NO-CACHE-CLEAN>` and
>         :ref:`V4L2_MEMORY_FLAG_NON_COHERENT <V4L2-MEMORY-FLAG-NON-COHERENT>`.
>+    * - ``V4L2_BUF_CAP_SUPPORTS_MAX_NUM_BUFFERS``
>+      - 0x00000080
>+      - If set, then the ``max_num_buffers`` field in ``struct v4l2_create_buffers``
>+        is valid.

Looks like the default is VB2_MAX_FRAME, if this isn't set, could you
highlight that here, I think that makes it a bit easier for the easier
to understand when this is needed.

Regards,
Sebastian

>+    * - ``V4L2_BUF_CAP_SUPPORTS_REMOVE_BUFS``
>+      - 0x00000100
>+      - If set, then ``VIDIOC_REMOVE_BUFS`` is supported.
>
> .. raw:: latex
>
>-- 
>2.43.0
>
>
diff mbox series

Patch

diff --git a/Documentation/userspace-api/media/v4l/vidioc-reqbufs.rst b/Documentation/userspace-api/media/v4l/vidioc-reqbufs.rst
index bbc22dd76032..1df3ce1fe93e 100644
--- a/Documentation/userspace-api/media/v4l/vidioc-reqbufs.rst
+++ b/Documentation/userspace-api/media/v4l/vidioc-reqbufs.rst
@@ -166,6 +166,13 @@  aborting or finishing any DMA in progress, an implicit
         :ref:`V4L2_BUF_FLAG_NO_CACHE_INVALIDATE <V4L2-BUF-FLAG-NO-CACHE-INVALIDATE>`,
         :ref:`V4L2_BUF_FLAG_NO_CACHE_CLEAN <V4L2-BUF-FLAG-NO-CACHE-CLEAN>` and
         :ref:`V4L2_MEMORY_FLAG_NON_COHERENT <V4L2-MEMORY-FLAG-NON-COHERENT>`.
+    * - ``V4L2_BUF_CAP_SUPPORTS_MAX_NUM_BUFFERS``
+      - 0x00000080
+      - If set, then the ``max_num_buffers`` field in ``struct v4l2_create_buffers``
+        is valid.
+    * - ``V4L2_BUF_CAP_SUPPORTS_REMOVE_BUFS``
+      - 0x00000100
+      - If set, then ``VIDIOC_REMOVE_BUFS`` is supported.

 .. raw:: latex