linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marek Szyprowski <m.szyprowski@samsung.com>
To: Hans Verkuil <hverkuil@xs4all.nl>,
	linux-media <linux-media@vger.kernel.org>
Cc: Pawel Osciak <pawel@osciak.com>
Subject: Re: [PATCH] vb2: fix vb2_poll for output streams
Date: Fri, 25 Jul 2014 07:21:35 +0200	[thread overview]
Message-ID: <53D1E95F.7050601@samsung.com> (raw)
In-Reply-To: <53D0F9D9.7080003@xs4all.nl>

Hello,

On 2014-07-24 14:19, Hans Verkuil wrote:
> vb2_poll should always return POLLOUT | POLLWRNORM as long as there
> are fewer buffers queued than there are buffers available. Poll for
> an output stream should only wait if all buffers are queued and nobody
> is dequeuing them.
>
> Signed-off-by: Hans Verkuil <hansverk@cisco.com>

Acked-by: Marek Szyprowski <m.szyprowski@samsung.com>

> ---
>   drivers/media/v4l2-core/videobuf2-core.c | 7 +++++++
>   1 file changed, 7 insertions(+)
>
> diff --git a/drivers/media/v4l2-core/videobuf2-core.c b/drivers/media/v4l2-core/videobuf2-core.c
> index f33508f..c359006 100644
> --- a/drivers/media/v4l2-core/videobuf2-core.c
> +++ b/drivers/media/v4l2-core/videobuf2-core.c
> @@ -2596,6 +2596,13 @@ unsigned int vb2_poll(struct vb2_queue *q, struct file *file, poll_table *wait)
>   	if ((list_empty(&q->queued_list) && !vb2_is_streaming(q)) || q->error)
>   		return res | POLLERR;
>   
> +	/*
> +	 * For output streams you can write as long as there are fewer buffers
> +	 * queued than there are buffers available.
> +	 */
> +	if (V4L2_TYPE_IS_OUTPUT(q->type) && q->queued_count < q->num_buffers)
> +		return res | POLLOUT | POLLWRNORM;
> +
>   	if (list_empty(&q->done_list))
>   		poll_wait(file, &q->done_wq, wait);
>   

Best regards
-- 
Marek Szyprowski, PhD
Samsung R&D Institute Poland


      reply	other threads:[~2014-07-25  5:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-24 12:19 [PATCH] vb2: fix vb2_poll for output streams Hans Verkuil
2014-07-25  5:21 ` Marek Szyprowski [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=53D1E95F.7050601@samsung.com \
    --to=m.szyprowski@samsung.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=pawel@osciak.com \
    /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;
as well as URLs for NNTP newsgroup(s).