Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp5141401pxj; Wed, 9 Jun 2021 10:03:45 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxX44Jq1xL4lmqmh52DdL3m/w+MYnzqqoSA+X2w9bu4N1MNVPDNA8AKmLkp33rF9cNtZMCq X-Received: by 2002:a05:6402:158e:: with SMTP id c14mr446377edv.128.1623258225604; Wed, 09 Jun 2021 10:03:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1623258225; cv=none; d=google.com; s=arc-20160816; b=Oi1oql9PXCbSk0dzgB7pz9LK2poFPWV/el+LeNbFipQPU+RS5fLEPoOB7qKss7tKrP YlfiVG7AVxpKUsc6nHzGjyj7KQc/uxZRD0Csc3nur2PfCQe/93eGmW/wiTbfmLJDBk1X oS2RMzPi2yMzIpozsG0h/p/M3Eoe8yqJxrhZkBtW47cXnobvQtj2mQlIUe4J9NL92gPF Bcl9SM11CMPFw5zw0B4+H+laUIFgjoRCZlR7odS0duKiyeUFmZ0ACW2r71hiAKbcLYvb jBX2TeN5w06rV4bmOWsXsuNlXX2PdpXScPxgm1EssbwWQ51cnxRoKL7Xxt6Modclmdps 672Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=Z3BOOY/+sPY2DGh8vy/+yFe3wY9oj28NcqKofD4JzIY=; b=Akj9Dl+FiToUNLVN7vngiNPhT5zRUWodwHDhdR4X2iG1RYZ64EoabsA8QseUFQtP/G ocID+SXznHkJwR7w7x7NgN1lBZiyL0lHVTISFlGJEOkCMv1f8KQnwLrDZRtX3esY9wQj mQR5PNzlmrUA7w+m66AZavPdKNDSKEKUa0n51RUgMpI3T+U6GQGH2kKQORcRAy4szjAb o4n9sLqMfLYKK5qJw+rc8VN86QJUp32kJnm31fRRIVdH0ZKLmaNbBHT1nG9gPHOH056w dSpzCY1gDasy9MBTCJtPqGrKW+u3p9Pgn2BHHKDjR6xvxQ2CTjgypJA5hM8UXSaMDzuO jVuQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id h28si202681edj.216.2021.06.09.10.03.18; Wed, 09 Jun 2021 10:03:45 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233454AbhFICOd (ORCPT + 99 others); Tue, 8 Jun 2021 22:14:33 -0400 Received: from netrider.rowland.org ([192.131.102.5]:48911 "HELO netrider.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S233322AbhFICOc (ORCPT ); Tue, 8 Jun 2021 22:14:32 -0400 Received: (qmail 1828243 invoked by uid 1000); 8 Jun 2021 22:12:37 -0400 Date: Tue, 8 Jun 2021 22:12:37 -0400 From: Alan Stern To: Larry Finger Cc: linux-usb@vger.kernel.org, LKML , Bjorn Helgaas , linux-pci@vger.kernel.org, ierturk@ieee.org Subject: Re: Strange problem with USB device Message-ID: <20210609021237.GA1826754@rowland.harvard.edu> References: <20210608182038.GA1812516@rowland.harvard.edu> <20210608185314.GB1812516@rowland.harvard.edu> <960057be-ef17-49e7-adba-ba2929d3a01f@lwfinger.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <960057be-ef17-49e7-adba-ba2929d3a01f@lwfinger.net> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 08, 2021 at 03:56:11PM -0500, Larry Finger wrote: > On 6/8/21 1:53 PM, Alan Stern wrote: > > I don't get it. If this is a PCIe device, why should it appear > > on a USB bus? Wouldn't you expect it to show up as a PCI device > > on a PCI bus instead? > > > > I do not know the internal details, but Realtek packages a PCIe wifi > device and a bluetooth USB device in the same package. Intel does the > same thing on my Wireless 7260. > > My lsusb shows: > Bus 003 Device 002: ID 8087:8000 Intel Corp. Integrated Rate Matching Hub > Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 001 Device 002: ID 8087:8008 Intel Corp. Integrated Rate Matching Hub > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 002 Device 004: ID 8087:07dc Intel Corp. Bluetooth wireless interface > Bus 002 Device 003: ID 0bda:c822 Realtek Semiconductor Corp. Bluetooth Radio > Bus 002 Device 002: ID 04f2:b3b2 Chicony Electronics Co., Ltd TOSHIBA > Web Camera - FHD > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > I have no devices plugged into a USB port. Okay, now I get the picture. The Intel PCIe card contains an EHCI USB host controller plus a couple of on-board USB Bluetooth devices and an on-board USB webcam, in addition to the PCIe wifi device. Which means you're looking at the problem all wrong. It isn't a USB problem at all; it's a PCI problem. Namely, why doesn't the system detect the USB host controller on the PCIe board? I have added the PCI maintainer and mailing list to the CC. Maybe they can help shed some light. The original Suse Bugzilla report: https://bugzilla.suse.com/show_bug.cgi?id=1186889 shows the Realtek board at PCI address 0000:03:00.0, but there's no mention of a USB host controller on that board. The only host controller on the system is the one at address 0000:00:14.0, which is xHCI and is directly on the motherboard. Furthermore, there's no trace of any mention of an EHCI USB host controller in the system log. So maybe the board has to be told somehow to turn that controller on before it will show up, and the rtw_8822ce driver isn't giving the appropriate order. Can the bug reporter get information from Windows about the USB host controllers, and in particular, the one on the RTL8822 board? Alan Stern