From: Alan Stern <stern@rowland.harvard.edu>
To: Ibrahim Erturk <ierturk@ieee.org>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
linux-usb@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org
Subject: Re: Strange problem with USB device
Date: Thu, 10 Jun 2021 22:13:04 -0400 [thread overview]
Message-ID: <20210611021304.GA23289@rowland.harvard.edu> (raw)
In-Reply-To: <CAFHYy-iMty-jjZzgzRA6tOezN-RJ+o4hRL1kZk+tuN1i-K9Ukg@mail.gmail.com>
On Fri, Jun 11, 2021 at 03:08:16AM +0300, Ibrahim Erturk wrote:
> Hi,
>
> I've already attached logs and a snapshot from the device manager on
> the windows side into the bug report. Hope this helps.
Yes, it does help. Although the information in those reports is somewhat
disorganized, it clearly shows there is only one USB host controller in the
system, and that is the one Linux detects. So my impression that we weren't
finding the host controller was wrong.
Back to my earlier guess: The Realtek board has to be told to do something in
order to make the Bluetooth device start working, such as turning on a power
source. (And perhaps that is what the RealTek people were talking about when
they suggested the problem could be in the rtw8822 power-up sequence.) Whatever
it is, the rtw8822 driver isn't doing it.
This means it's still a PCI problem.
Alan Stern
PS: Larry, the discrepancy between Windows reporting an Intel USB hub and Linux
reporting two Linux Foundation hubs isn't real -- or at least, it's what should
be expected. I can explain in more detail if you're curious, but you don't need
to worry about it.
prev parent reply other threads:[~2021-06-11 2:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cfc37ce0-823e-0d19-f5d7-fcd571a94943@lwfinger.net>
[not found] ` <20210608182038.GA1812516@rowland.harvard.edu>
[not found] ` <a7c7ba62-a74f-d7db-bfd9-4f6c8e25e0b8@lwfinger.net>
[not found] ` <20210608185314.GB1812516@rowland.harvard.edu>
[not found] ` <960057be-ef17-49e7-adba-ba2929d3a01f@lwfinger.net>
2021-06-09 2:12 ` Strange problem with USB device Alan Stern
2021-06-11 0:08 ` Ibrahim Erturk
2021-06-11 2:13 ` Alan Stern [this message]
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=20210611021304.GA23289@rowland.harvard.edu \
--to=stern@rowland.harvard.edu \
--cc=Larry.Finger@lwfinger.net \
--cc=bhelgaas@google.com \
--cc=ierturk@ieee.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).