From: Marcel Holtmann <marcel@holtmann.org>
To: Hui Wang <hui.wang@canonical.com>
Cc: Bluetooth Kernel Mailing List <linux-bluetooth@vger.kernel.org>,
Johan Hedberg <johan.hedberg@gmail.com>
Subject: Re: [PATCH] Bluetooth: btusb: Add a module parameter ignore_id for debugging
Date: Mon, 3 Aug 2020 08:45:50 +0200 [thread overview]
Message-ID: <636EB5CB-7A63-4C3B-A053-D59EA73FF1F2@holtmann.org> (raw)
In-Reply-To: <8c625767-7211-2b41-7673-33e641c2924e@canonical.com>
Hi Hui,
>>> There is always an on-board usb bluetooth hci on the laptops, if
>>> the bluetooth function doesn't work well like a bt headset can't work
>>> with HSP/HFP mode, we often plug an external usb BT hci to verify if
>>> that headset could work with the exteral BT hci or not, in this
>>> situation, there will be 2 hcis (hci0 and hci1) in the system, and
>>> so far, the gnome can't handle the hci1 well so we met lots of
>>> problems when debugging with hci1 under gnome.
>>>
>>> After adding this new module parameter, we could ban the on-board
>>> usb hci by putting btusb.ignore_id=idVendor,idProduct to the bootargs,
>>> then the external usb hci will be hci0 and there is only one hci
>>> in the system. We could easily debug with the external usb bluetooth
>>> hci after this change.
>>>
>>> Signed-off-by: Hui Wang <hui.wang@canonical.com>
>>> ---
>>> drivers/bluetooth/btusb.c | 11 +++++++++++
>>> 1 file changed, 11 insertions(+)
>> please use this instead.
>>
>> echo “vvvv pppp 0 08fd 0002" > /sys/bus/usb/drivers/foo/new_id
>
> Thanks, but to run the command above, the system should boot up first. After the system boot up, the btusb is already loaded and and the on-board hci is already driven by btusb. looks like it is too late to run that command for on-board hci.
then unload the module first or blacklist the module.
Regards
Marcel
next prev parent reply other threads:[~2020-08-03 6:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-02 4:21 [PATCH] Bluetooth: btusb: Add a module parameter ignore_id for debugging Hui Wang
2020-08-02 14:58 ` Marcel Holtmann
2020-08-03 2:55 ` Hui Wang
2020-08-03 6:45 ` Marcel Holtmann [this message]
2020-08-03 7:59 ` Hui Wang
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=636EB5CB-7A63-4C3B-A053-D59EA73FF1F2@holtmann.org \
--to=marcel@holtmann.org \
--cc=hui.wang@canonical.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@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).