From: <gregkh@linuxfoundation.org>
To: marcel@holtmann.org, gregkh@linuxfoundation.org, johan.hedberg@intel.com
Cc: <stable@vger.kernel.org>, <stable-commits@vger.kernel.org>
Subject: Patch "Bluetooth: Ignore isochronous endpoints for Intel USB bootloader" has been added to the 3.14-stable tree
Date: Sun, 26 Apr 2015 11:51:13 +0200 [thread overview]
Message-ID: <143004187324474@kroah.com> (raw)
This is a note to let you know that I've just added the patch titled
Bluetooth: Ignore isochronous endpoints for Intel USB bootloader
to the 3.14-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
bluetooth-ignore-isochronous-endpoints-for-intel-usb-bootloader.patch
and it can be found in the queue-3.14 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@vger.kernel.org> know about it.
>From d92f2df0565ea04101d6ac04bdc10feeb1d93c94 Mon Sep 17 00:00:00 2001
From: Marcel Holtmann <marcel@holtmann.org>
Date: Sun, 6 Jul 2014 14:53:55 +0200
Subject: Bluetooth: Ignore isochronous endpoints for Intel USB bootloader
From: Marcel Holtmann <marcel@holtmann.org>
commit d92f2df0565ea04101d6ac04bdc10feeb1d93c94 upstream.
The isochronous endpoints are not valid when the Intel Bluetooth
controller boots up in bootloader mode. So just mark these endpoints
as broken and then they will not be configured.
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
drivers/bluetooth/btusb.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -121,7 +121,8 @@ static const struct usb_device_id btusb_
{ USB_VENDOR_AND_INTERFACE_INFO(0x13d3, 0xff, 0x01, 0x01) },
/* Intel Bluetooth USB Bootloader (RAM module) */
- { USB_DEVICE(0x8087, 0x0a5a), .driver_info = BTUSB_INTEL_BOOT },
+ { USB_DEVICE(0x8087, 0x0a5a),
+ .driver_info = BTUSB_INTEL_BOOT | BTUSB_BROKEN_ISOC },
{ } /* Terminating entry */
};
Patches currently in stable-queue which might be from marcel@holtmann.org are
queue-3.14/bluetooth-add-support-for-broadcom-device-of-asus-z97-deluxe-motherboard.patch
queue-3.14/bluetooth-add-support-for-acer-2.patch
queue-3.14/bluetooth-add-firmware-update-for-atheros-0cf3-311f.patch
queue-3.14/add-a-new-pid-vid-0227-0930-for-ar3012.patch
queue-3.14/bluetooth-add-support-for-intel-bootloader-devices.patch
queue-3.14/bluetooth-add-usb-device-04ca-3010-as-atheros-ar3012.patch
queue-3.14/bluetooth-add-support-for-acer.patch
queue-3.14/bluetooth-btusb-add-imc-networks-broadcom-based.patch
queue-3.14/bluetooth-append-new-supported-device-to-the-list.patch
queue-3.14/bluetooth-ignore-isochronous-endpoints-for-intel-usb-bootloader.patch
queue-3.14/bluetooth-sort-the-list-of-ids-in-the-source-code.patch
queue-3.14/bluetooth-enable-atheros-0cf3-311e-for-firmware-upload.patch
reply other threads:[~2015-04-26 9:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=143004187324474@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=johan.hedberg@intel.com \
--cc=marcel@holtmann.org \
--cc=stable-commits@vger.kernel.org \
--cc=stable@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).