From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: linux-media@vger.kernel.org
Cc: kernel@pengutronix.de,
Marek Szyprowski <m.szyprowski@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Pawel Osciak <p.osciak@samsung.com>,
Hans Verkuil <hverkuil@xs4all.nl>
Subject: vb2 queue setup skipped when playing bigger video
Date: Wed, 8 Jun 2011 10:53:55 +0200 [thread overview]
Message-ID: <20110608085355.GS9907@pengutronix.de> (raw)
Hello,
I'm writing a driver for a video overlay device and have the problem
that if I first playback a video with a resolution of say 320x240 and
then another one with 640x400 the buffers allocated for the first
playback are too small, but my .queue_setup callback isn't called.
I think the culprit is the following line in vb2_reqbufs()
(drivers/media/video/videobuf2-core.c):
/*
* If the same number of buffers and memory access method is requested
* then return immediately.
*/
if (q->memory == req->memory && req->count == q->num_buffers)
return 0;
which exits vb2_reqbufs before
ret = call_qop(q, queue_setup, q, &num_buffers, &num_planes,
plane_sizes, q->alloc_ctx);
Reading the vb1 code, this shortcut isn't implemented there.
As I'm quite new to all that v4l2 stuff, I'm not sure what to do.
Just removing the return 0 (i.e. reverting 31901a07) seems to do the
right thing for me.
Thoughts?
Thanks and best regards,
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next reply other threads:[~2011-06-08 8:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 8:53 Uwe Kleine-König [this message]
2011-06-08 8:58 ` Corrected address for Pawel [Was: vb2 queue setup skipped when playing bigger video] Uwe Kleine-König
2011-06-08 9:09 ` vb2 queue setup skipped when playing bigger video Marek Szyprowski
2011-06-08 9:31 ` [PATCH] Don't shortcut vb2_reqbufs in case the format changed Uwe Kleine-König
2011-06-08 20:00 ` Uwe Kleine-König
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=20110608085355.GS9907@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=hverkuil@xs4all.nl \
--cc=kernel@pengutronix.de \
--cc=kyungmin.park@samsung.com \
--cc=linux-media@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=p.osciak@samsung.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