From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1CF28C43381 for ; Mon, 11 Jan 2021 20:30:35 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id D2D5B21BE5 for ; Mon, 11 Jan 2021 20:30:34 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1733074AbhAKUaV (ORCPT ); Mon, 11 Jan 2021 15:30:21 -0500 Received: from mail.kernel.org ([198.145.29.99]:34378 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1732953AbhAKUaU (ORCPT ); Mon, 11 Jan 2021 15:30:20 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id 6595121BE5; Mon, 11 Jan 2021 20:29:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1610396979; bh=ZL2Tr27BAyH7lf+5uXotJ3Ho5kTkqKeZLx2htZ7lDHs=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=oebD7mUPSSPQ1PTwzzpDqA+X0JU8ex5c8lGbRurImuiQhKH0tccUQusQWh27U7GO9 ryz0X28A2PDjYnvme4ArnpBKGIHX5LhqWnwFlMpbWvBHyn+WesZwifI3R0j+3JJSeh cazQ9AsQKW6KCIBiMj5d4Zci4v7HuXXK1bnRy3cM= Date: Mon, 11 Jan 2021 21:30:50 +0100 From: Greg Kroah-Hartman To: Patrik Jakobsson Cc: Al Cooper , Felipe Balbi , linux-usb@vger.kernel.org Subject: Re: Conflicting PCI ID in bdc driver Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-usb@vger.kernel.org On Mon, Jan 11, 2021 at 08:34:01PM +0100, Patrik Jakobsson wrote: > Hi Al, > The PCI device ID of 0x1570 in the bdc driver (bdc_pci.c) is > conflicting with the Apple FacetimeHD webcam [1]. Is this caused by an > incorrect ID in the bdc driver or are there actually two devices with > the same ID in the wild? If we have a real conflict, how would we go > about solving this? Looks like someone at broadcom messed up :( Can you look for any other fields in the device other than just the vendor/device ids to verify that this really is a webcam so you can not bind to the same thing this driver wants to bind to? thanks, greg k-h