From patchwork Sat Mar 6 19:46:09 2010 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: =?utf-8?q?Erik_Andr=C3=A9n?= X-Patchwork-Id: 2891 Return-path: Envelope-to: mchehab@infradead.org Delivery-date: Sat, 06 Mar 2010 19:46:34 +0000 Received: from bombadil.infradead.org [18.85.46.34] by pedra with IMAP (fetchmail-6.3.6) for (single-drop); Sat, 06 Mar 2010 16:49:14 -0300 (BRT) Received: from vger.kernel.org ([209.132.180.67]) by bombadil.infradead.org with esmtp (Exim 4.69 #1 (Red Hat Linux)) id 1NnzxJ-0003Ny-SI; Sat, 06 Mar 2010 19:46:34 +0000 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752224Ab0CFTqM (ORCPT + 1 other); Sat, 6 Mar 2010 14:46:12 -0500 Received: from fg-out-1718.google.com ([72.14.220.153]:59766 "EHLO fg-out-1718.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751421Ab0CFTqL (ORCPT ); Sat, 6 Mar 2010 14:46:11 -0500 Received: by fg-out-1718.google.com with SMTP id l26so656725fgb.1 for ; Sat, 06 Mar 2010 11:46:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=2BqUzO3Avp194h9IFWGn6B5FWPMkjqIm6rp+qkNtzTw=; b=Cr3otOOa3WoXVqGvrHlgGX1pkh7sIv7OpMNNPtMgReiz+AEoE6zHSycLe93/YIsrhM n+RxDuxJU2xjekEFudAokzEnT6TDev8sOTIjP4bMearUNjdVyTlmeMub3med+udx0Nto RQXdK+ByDGFBFRPp/vY342McAb0g/UDfdBjPs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=S5UVXneYgp/oKoFmCySRDvLXkFwqBdDmBmQIIyTQpfMkEXGRTnI1/gSWjSVRh64ByU zNqUDEXtCnozDrsWvHwB2wCGZCtEUptX1Gj9RQbCLSOL8o+RAQOIda2VG47K4WXmw0W5 lkjeFYYlZwUIPWMufMGdyljt5j636PzebEF/w= MIME-Version: 1.0 Received: by 10.239.193.11 with SMTP id g11mr209337hbi.164.1267904769476; Sat, 06 Mar 2010 11:46:09 -0800 (PST) In-Reply-To: <4B8F9FC6.9030105@redhat.com> References: <1820d69d1003030445n18b35839r407d4d277b1bf48d@mail.gmail.com> <62e5edd41003030517g6fa9b64awdf18578d6c5db7e@mail.gmail.com> <4B8F974A.4090001@redhat.com> <62e5edd41003040336x16253369ycb1905a9938432db@mail.gmail.com> <4B8F9FC6.9030105@redhat.com> Date: Sat, 6 Mar 2010 20:46:09 +0100 Message-ID: <62e5edd41003061146x689527c9s5b3ab81eec3425a0@mail.gmail.com> Subject: Re: Gspca USB driver zc3xx and STV06xx probe the same device .. From: =?ISO-8859-1?Q?Erik_Andr=E9n?= To: Gabriel C Cc: LKML , Jean-Francois Moine , Linux Media Mailing List , Hans de Goede Sender: linux-media-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-media@vger.kernel.org 2010/3/4 Hans de Goede : > Hi, > > On 03/04/2010 12:36 PM, Erik Andrén wrote: >> >> 2010/3/4 Hans de Goede: >>> >>> Hi, >>> >>> On 03/03/2010 02:17 PM, Erik Andrén wrote: >>>> >>>> 2010/3/3 Gabriel C: >>>>> >>>>> Hello, >>>>> >>>>> I own a QuickCam Messanger webcam.. I didn't used it in ages but today >>>>> I plugged it in.. >>>>> ( Device 002: ID 046d:08da Logitech, Inc. QuickCam Messanger ) >>>>> >>>>> Now zc3xx and stv06xx are starting both to probe the device .. In >>>>> 2.6.33 that result in a not working webcam. >>>>> ( rmmod both&&    modprobe zc3xx one seems to fix that ) >>>>> >>>>> On current git head zc3xx works fine even when both are probing the >>>>> device. >>>>> >>>>> Also I noticed stv06xx fails anyway for my webcam with this error: >>>>> .... >>>>> >>>>> [  360.910243] STV06xx: Configuring camera >>>>> [  360.910244] STV06xx: st6422 sensor detected >>>>> [  360.910245] STV06xx: Initializing camera >>>>> [  361.161948] STV06xx: probe of 6-1:1.0 failed with error -32 >>>>> [  361.161976] usbcore: registered new interface driver STV06xx >>>>> [  361.161978] STV06xx: registered >>>>> ..... >>>>> >>>>> Next thing is stv06xx tells it is an st6422 sensor and does not work >>>>> with it while zc3xx tells it is an HV7131R(c) sensor and works fine >>>>> with it. >>>>> >>>>> What is right ? >>>> >>>> Hans, >>>> As you added support for the st6422 sensor to the stv06xx subdriver I >>>> imagine you best know what's going on. >>>> >>> >>> I took the USB-ID in question from the out of tree v4l1 driver I was >>> basing >>> my >>> st6422 work on. Looking at the other ID's (which are very close together) >>> and >>> combining that with this bug report, I think it is safe to say that the >>> USB-ID >>> in question should be removed from the stv06xx driver. >>> >>> Erik will you handle this, or shall I ? >>> >> Either way is fine by me. >> I can try to do it tonight. >> > > If you could take care of this that would be great! > > Thanks, > > Hans > Sorry for delaying this, real life came in the way. I'm pasting in a patch that removes the usb id. I'm also attaching it as an attachment as gmail probably will stomp on the inline version. Gabriel, could you please apply and test this patch and verify that it works as intended, i. e. the stv06xx driver _doesn't_ bind to your camera but the zx3xx driver instead does. If it works as intended could you please reply to this mail with a tested-by: your name tag. Best regards, Erik From 6f40494d48c5641326168115a96659581cea6273 Mon Sep 17 00:00:00 2001 From: =?utf-8?q?Erik=20Andr=C3=A9n?= Date: Sat, 6 Mar 2010 20:34:51 +0100 Subject: [PATCH 1/1] gspca-stv06xx: Remove the 046d:08da usb id from linking to the stv06xx driver MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit The 046d:08da usb id shouldn't be associated with the stv06xx driver as they're not compatible with each other. This fixes a bug where Quickcam Messenger cams fail to use its proper driver (gspca-zc3xx), rendering the camera inoperable. Signed-off-by: Erik Andrén tested-by: Gabriel Craciunescu --- drivers/media/video/gspca/stv06xx/stv06xx.c | 2 -- 1 files changed, 0 insertions(+), 2 deletions(-) MODULE_DEVICE_TABLE(usb, device_table); diff --git a/drivers/media/video/gspca/stv06xx/stv06xx.c b/drivers/media/video/gspca/stv06xx/stv06xx.c index de823ed..b1f7e28 100644 --- a/drivers/media/video/gspca/stv06xx/stv06xx.c +++ b/drivers/media/video/gspca/stv06xx/stv06xx.c @@ -497,8 +497,6 @@ static const __devinitdata struct usb_device_id device_table[] = { {USB_DEVICE(0x046D, 0x08F5), .driver_info = BRIDGE_ST6422 }, /* QuickCam Messenger (new) */ {USB_DEVICE(0x046D, 0x08F6), .driver_info = BRIDGE_ST6422 }, - /* QuickCam Messenger (new) */ - {USB_DEVICE(0x046D, 0x08DA), .driver_info = BRIDGE_ST6422 }, {} };