From: Alan Stern <stern@rowland.harvard.edu>
To: Jose Ignacio Tornos Martinez <jtornosm@redhat.com>
Cc: gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
marcel@holtmann.org
Subject: Re: [PATCH v5] USB: core: skip unconfiguration if device doesn't support it
Date: Wed, 4 May 2022 13:54:08 -0400 [thread overview]
Message-ID: <YnK9wBQXPB+LuHVP@rowland.harvard.edu> (raw)
In-Reply-To: <20220504151647.471885-1-jtornosm@redhat.com>
On Wed, May 04, 2022 at 05:16:47PM +0200, Jose Ignacio Tornos Martinez wrote:
> Some devices like 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.
>
> For these devices, 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, so a new quirk has been created. By default, quirk is
> not applied for any device and needs to be enabled by user.
>
> For these devices, 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.
>
> Signed-off-by: Jose Ignacio Tornos Martinez <jtornosm@redhat.com>
> ---
Acked-by: Alan Stern <stern@rowland.harvard.edu>
next prev parent reply other threads:[~2022-05-04 18:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 15:16 [PATCH v5] USB: core: skip unconfiguration if device doesn't support it Jose Ignacio Tornos Martinez
2022-05-04 17:54 ` Alan Stern [this message]
2022-05-12 11:47 ` Greg KH
2022-05-13 9:50 ` Jose Ignacio Tornos Martinez
2022-05-13 14:09 ` Alan Stern
2022-05-13 14:13 ` Greg KH
2022-05-13 14:26 ` Alan Stern
2022-05-13 14:46 ` Greg KH
2022-05-13 14:58 ` Jose Ignacio Tornos Martinez
2022-05-17 13:58 ` Jose Ignacio Tornos Martinez
2022-05-13 15:00 ` Bjørn Mork
2022-05-16 5:45 ` 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=YnK9wBQXPB+LuHVP@rowland.harvard.edu \
--to=stern@rowland.harvard.edu \
--cc=gregkh@linuxfoundation.org \
--cc=jtornosm@redhat.com \
--cc=linux-usb@vger.kernel.org \
--cc=marcel@holtmann.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.