From: Greg KH <gregkh@linuxfoundation.org>
To: Jose Ignacio Tornos Martinez <jtornosm@redhat.com>
Cc: stern@rowland.harvard.edu, linux-usb@vger.kernel.org,
marcel@holtmann.org
Subject: Re: [PATCH] Bluetooth: btusb: CSR chip hangs when unbound
Date: Mon, 2 May 2022 14:04:38 +0200 [thread overview]
Message-ID: <Ym/I1v094tX84nih@kroah.com> (raw)
In-Reply-To: <20220502070758.67396-1-jtornosm@redhat.com>
On Mon, May 02, 2022 at 09:07:58AM +0200, Jose Ignacio Tornos Martinez wrote:
> Bluetooth Dongles with CSR chip (i.e. USB Bluetooth V4.0 Dongle by
> Trust) hang when they are unbound from 'unbind' sysfs entry and
> can not be bound again.
>
> The reason is CSR chip hangs when usb configuration command with
> index 0 (used to unconfigure) is sent during disconnection.
>
> To avoid this unwanted result, it is necessary not to send this
> command for CSR chip when usb device is unbound, so a new quirk
> has been created for this device.
>
> Athough device is not unconfigured, it is better to avoid device
> hanging to be able to operate. Even bluetooth can be previously
> turned off.
> On the other hand, this is not important if usb device is going to
> be bound again (normal behavior), i.e. with usbip.
> ---
Also, the subject is totally wrong :(
next prev parent reply other threads:[~2022-05-02 12:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 7:07 [PATCH] Bluetooth: btusb: CSR chip hangs when unbound Jose Ignacio Tornos Martinez
2022-05-02 12:04 ` Greg KH
2022-05-02 12:04 ` Greg KH
2022-05-02 12:04 ` Greg KH [this message]
2022-05-02 14:22 ` Alan Stern
2022-05-03 6:13 ` Jose Ignacio Tornos Martinez
-- strict thread matches above, loose matches on Subject: below --
2022-04-29 15:31 Jose Ignacio Tornos Martinez
2022-04-29 15:46 ` Greg KH
2022-04-30 1:11 ` Alan Stern
2022-04-30 7:31 ` Jose Ignacio Tornos Martinez
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=Ym/I1v094tX84nih@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jtornosm@redhat.com \
--cc=linux-usb@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=stern@rowland.harvard.edu \
/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