From: Hans de Goede <hdegoede@redhat.com>
To: Paulo Assis <pj.assis@gmail.com>
Cc: "Lluís Batlle i Rossell" <viric@viric.name>, linux-media@vger.kernel.org
Subject: Re: Problems with the gspca_ov519 driver
Date: Tue, 22 May 2012 16:39:17 +0200 [thread overview]
Message-ID: <4FBBA515.7010006@redhat.com> (raw)
In-Reply-To: <CAPueXH6uN4UQO_WL_pc9wBoZV=v_7AVtQKcruKY=BCMeJOw-2Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]
Hi,
On 05/22/2012 04:08 PM, Paulo Assis wrote:
> Hi,
> This bug also causes the camera to crash when changing fps in
> guvcview, uvc devices (at least all the ones I tested) require the
> stream to be restarted for fps to change, so in the case of this
> driver after STREAMOFF the camera just becomes unresponsive.
>
> Regards,
> Paulo
>
> 2012/5/22 Lluís Batlle i Rossell<viric@viric.name>:
>> Hello,
>>
>> I'm trying to get video using v4l2 ioctls from a gspca_ov519 camera, and after
>> STREAMOFF all buffers are still flagged as QUEUED, and QBUF fails. DQBUF also
>> fails (blocking for a 3 sec timeout), after streamoff. So I'm stuck, after
>> STREAMOFF, unable to get pictures coming in again. (Linux 3.3.5).
>>
>> As an additional note, pinchartl on irc #v4l says to favour a moving of gspca to
>> vb2. I don't know what it means.
>>
>> Can someone take care of the bug, or should I consider the camera 'non working'
>> in linux?
We talked about this on irc, attached it a patch which should fix this, feedback
appreciated.
Regards,
Hans
[-- Attachment #2: 0001-gspca-core-Fix-buffers-staying-in-queued-state-after.patch --]
[-- Type: text/x-patch, Size: 1209 bytes --]
>From b0eefa00c72e9dfe9eaa5f425c0d346b19ea01cd Mon Sep 17 00:00:00 2001
From: Hans de Goede <hdegoede@redhat.com>
Date: Tue, 22 May 2012 16:24:05 +0200
Subject: [PATCH] gspca-core: Fix buffers staying in queued state after a
stream_off
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
---
drivers/media/video/gspca/gspca.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/media/video/gspca/gspca.c b/drivers/media/video/gspca/gspca.c
index 137166d..31721ea 100644
--- a/drivers/media/video/gspca/gspca.c
+++ b/drivers/media/video/gspca/gspca.c
@@ -1653,7 +1653,7 @@ static int vidioc_streamoff(struct file *file, void *priv,
enum v4l2_buf_type buf_type)
{
struct gspca_dev *gspca_dev = video_drvdata(file);
- int ret;
+ int i, ret;
if (buf_type != V4L2_BUF_TYPE_VIDEO_CAPTURE)
return -EINVAL;
@@ -1678,6 +1678,8 @@ static int vidioc_streamoff(struct file *file, void *priv,
wake_up_interruptible(&gspca_dev->wq);
/* empty the transfer queues */
+ for (i = 0; i < gspca_dev->nframes; i++)
+ gspca_dev->frame[i].v4l2_buf.flags &= ~BUF_ALL_FLAGS;
atomic_set(&gspca_dev->fr_q, 0);
atomic_set(&gspca_dev->fr_i, 0);
gspca_dev->fr_o = 0;
--
1.7.10
next prev parent reply other threads:[~2012-05-22 14:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 11:00 Problems with the gspca_ov519 driver Lluís Batlle i Rossell
2012-05-22 14:08 ` Paulo Assis
2012-05-22 14:39 ` Hans de Goede [this message]
2012-05-22 15:27 ` Lluís Batlle i Rossell
2012-05-22 16:28 ` Hans de Goede
2012-05-22 16:30 ` Lluís Batlle i Rossell
2012-05-22 18:25 ` Lluís Batlle i Rossell
2012-05-22 21:02 ` Antonio Ospite
2012-05-23 8:14 ` Hans de Goede
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=4FBBA515.7010006@redhat.com \
--to=hdegoede@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=pj.assis@gmail.com \
--cc=viric@viric.name \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.