From: 김승우 <sw0312.kim@samsung.com>
To: Seung-Woo Kim <sw0312.kim@samsung.com>
Cc: linux-media@vger.kernel.org, mchehab@redhat.com,
m.szyprowski@samsung.com, hans.verkuil@cisco.com,
pawel@osciak.com, kyungmin.park@samsung.com,
Seung-Woo Kim <sw0312.kim@samsung.com>
Subject: Re: [RFC][PATCH 0/2] media: fix polling not to wait if a buffer is available
Date: Tue, 07 May 2013 14:28:49 +0900 [thread overview]
Message-ID: <51889111.60202@samsung.com> (raw)
In-Reply-To: <1364798447-32224-1-git-send-email-sw0312.kim@samsung.com>
Ping this patch-set.
The first patch for vb2 was acked by Marek.
any suggestion for the second patch?
Regards,
- Seung-Woo Kim
On 2013년 04월 01일 15:40, Seung-Woo Kim wrote:
> As poll behavior described in following link, polling needs to just return if
> already some buffer is in done list.
> Link: http://www.spinics.net/lists/linux-media/msg34759.html
>
> But in current vb2 and v4l2_m2m, poll function always calls poll_wait(), so it
> needs to wait until next vb2_buffer_done() or queue is cancelled.
>
> So I add check routine for done_list before calling poll_wait().
> But I'm not sure that locking for done_lock of queue is also needed in this
> case or not because done_list of queue is checked without locking in some
> other parts of vb2.
>
> Seung-Woo Kim (2):
> media: vb2: return for polling if a buffer is available
> media: v4l2-mem2mem: return for polling if a buffer is available
>
> drivers/media/v4l2-core/v4l2-mem2mem.c | 6 ++++--
> drivers/media/v4l2-core/videobuf2-core.c | 3 ++-
> 2 files changed, 6 insertions(+), 3 deletions(-)
>
--
Seung-Woo Kim
Samsung Software R&D Center
--
prev parent reply other threads:[~2013-05-07 5:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-01 6:40 [RFC][PATCH 0/2] media: fix polling not to wait if a buffer is available Seung-Woo Kim
2013-04-01 6:40 ` [RFC][PATCH 1/2] media: vb2: return for polling " Seung-Woo Kim
2013-04-11 11:15 ` Marek Szyprowski
2013-04-01 6:40 ` [RFC][PATCH 2/2] media: v4l2-mem2mem: " Seung-Woo Kim
2013-05-07 13:43 ` Marek Szyprowski
2013-05-07 5:28 ` 김승우 [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=51889111.60202@samsung.com \
--to=sw0312.kim@samsung.com \
--cc=hans.verkuil@cisco.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-media@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mchehab@redhat.com \
--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).