From: Hans Verkuil <hverkuil-cisco@xs4all.nl>
To: Benjamin Gaignard <benjamin.gaignard@collabora.com>,
tfiga@chromium.org, m.szyprowski@samsung.com, mchehab@kernel.org
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@collabora.com
Subject: Re: [PATCH] media: core: Refactor vb2_ioctl_create_bufs() to always set capabilities flags
Date: Tue, 16 Jan 2024 15:03:16 +0100 [thread overview]
Message-ID: <cbafd2ce-bbfd-4684-a876-79af20ad33cd@xs4all.nl> (raw)
In-Reply-To: <20240115170826.214519-1-benjamin.gaignard@collabora.com>
On 15/01/2024 18:08, Benjamin Gaignard wrote:
> vb2_create_bufs() takes care of setting V4L2_BUF_CAP_SUPPORTS_MAX_NUM_BUFFERS
> flag and vb2_queue max_num_buffers field so call it instead duplicate the
> same code in vb2_ioctl_create_bufs(). Testing p->count after calling
> vb2_create_bufs() is safe since the function also check it.
>
> Fixes: d055a76c0065 ("media: core: Report the maximum possible number of buffers for the queue")
> Signed-off-by: Benjamin Gaignard <benjamin.gaignard@collabora.com>
> ---
> .../media/common/videobuf2/videobuf2-v4l2.c | 23 ++++++++++---------
> 1 file changed, 12 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/media/common/videobuf2/videobuf2-v4l2.c b/drivers/media/common/videobuf2/videobuf2-v4l2.c
> index 54d572c3b515..bf304a7234a0 100644
> --- a/drivers/media/common/videobuf2/videobuf2-v4l2.c
> +++ b/drivers/media/common/videobuf2/videobuf2-v4l2.c
> @@ -1029,23 +1029,24 @@ int vb2_ioctl_create_bufs(struct file *file, void *priv,
> int res = vb2_verify_memory_type(vdev->queue, p->memory,
> p->format.type);
>
> - p->index = vdev->queue->num_buffers;
> - fill_buf_caps(vdev->queue, &p->capabilities);
> - validate_memory_flags(vdev->queue, p->memory, &p->flags);
> + if (vb2_queue_is_busy(vdev->queue, file)) {
> + res = -EBUSY;
> + goto failed;
> + }
> +
> + res = vb2_create_bufs(vdev->queue, p);
> + if (res == 0)
> + vdev->queue->owner = file->private_data;
This would set owner when called with p->count == 0, but that's
not what you want.
I decided to make an attempt at this myself, I'll post a patch.
Regards,
Hans
> +
> +failed:
> /*
> * If count == 0, then just check if memory and type are valid.
> - * Any -EBUSY result from vb2_verify_memory_type can be mapped to 0.
> + * Any -EBUSY result from vb2_verify_memory_type() or
> + * vb2_queue_is_busy() can be mapped to 0.
> */
> if (p->count == 0)
> return res != -EBUSY ? res : 0;
> - if (res)
> - return res;
> - if (vb2_queue_is_busy(vdev->queue, file))
> - return -EBUSY;
>
> - res = vb2_create_bufs(vdev->queue, p);
> - if (res == 0)
> - vdev->queue->owner = file->private_data;
> return res;
> }
> EXPORT_SYMBOL_GPL(vb2_ioctl_create_bufs);
prev parent reply other threads:[~2024-01-16 14:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 17:08 Benjamin Gaignard
2024-01-15 17:08 ` [PATCH] media: media videobuf2: Stop direct calls to queue num_buffers field Benjamin Gaignard
2024-01-16 9:21 ` Hans Verkuil
2024-01-16 9:32 ` Benjamin Gaignard
2024-01-18 11:22 ` Tomasz Figa
2024-01-18 11:50 ` Hans Verkuil
2024-01-16 14:03 ` Hans Verkuil [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cbafd2ce-bbfd-4684-a876-79af20ad33cd@xs4all.nl \
--to=hverkuil-cisco@xs4all.nl \
--cc=benjamin.gaignard@collabora.com \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mchehab@kernel.org \
--cc=tfiga@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®