public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: "Németh Márton" <nm127@freemail.hu>
To: Jean-Francois Moine <moinejf@free.fr>
Cc: V4L Mailing List <linux-media@vger.kernel.org>
Subject: gspca_pac7302: sporatdic problem when plugging the device
Date: Sun, 10 Jan 2010 17:58:58 +0100	[thread overview]
Message-ID: <4B4A0752.6030306@freemail.hu> (raw)

Hi,

I have sporadic problem with Labtec Webcam 2200 (0x093a:0x2626). I'm using
gspca_pac7302 driver from http://linuxtv.org/hg/~jfrancois/gspca/
rev 13915 on top of Linux kernel 2.6.32.

I executed the following command in an xterm window:
$ while true; do ./svv; done

Then I plugged and unplugged the device 16 times. When I last plugged the
device I get the following error in the dmesg:

[32393.421313] gspca: probing 093a:2626
[32393.426193] gspca: video0 created
[32393.426958] gspca: probing 093a:2626
[32393.426968] gspca: Interface class 1 not handled here
[32394.005917] pac7302: reg_w_page(): Failed to write register to index 0x49, value 0x0, error -71
[32394.067799] gspca: set alt 8 err -71
[32394.090792] gspca: set alt 8 err -71
[32394.118159] gspca: set alt 8 err -71

The 17th plug was working correctly again. I executed this test on an EeePC 901.

This driver version contains the msleep(4) in the reg_w_buf(). However, here
the reg_w_page() fails, which does not have msleep() inside. I don't know what
is the real problem, but I am afraid that slowing down reg_w_page() would make
the time longer when the device can be used starting from the event when it is
plugged.

Regards,

	Márton Németh

             reply	other threads:[~2010-01-10 16:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-10 16:58 Németh Márton [this message]
2010-01-10 19:48 ` gspca_pac7302: sporatdic problem when plugging the device Jean-Francois Moine
2010-01-10 20:28   ` Németh Márton
2010-01-11  8:09     ` Jean-Francois Moine
2010-01-11  8:10     ` Jean-Francois Moine
2010-01-11 18:07       ` Németh Márton

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=4B4A0752.6030306@freemail.hu \
    --to=nm127@freemail.hu \
    --cc=linux-media@vger.kernel.org \
    --cc=moinejf@free.fr \
    /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