linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ortwin Glück" <ortwin.glueck@logobject.ch>
To: linux-kernel@vger.kernel.org
Cc: linux-bluetooth@vger.kernel.org,
	Marcel Holtmann <marcel@holtmann.org>,
	Johan Hedberg <johan.hedberg@gmail.com>,
	Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Subject: [PATCH] fix 5.15 init regression for Intel Bluetooth
Date: Mon, 27 Dec 2021 11:26:59 +0100	[thread overview]
Message-ID: <b0f6f66b-28aa-9d43-0aab-e6887ee0fda8@logobject.ch> (raw)
In-Reply-To: <856c5dc7-9fb4-8438-3451-7b369832056a@odi.ch>

[-- Attachment #1: Type: text/plain, Size: 449 bytes --]


Hi

On all 5.15 kernels the Intel Bluetooth no longer works. All was fine in 5.14.
Apparently the quirk is needed for this device.

vanilla 5.15.5:
    Bluetooth: hci0: Reading Intel version command failed (-110)
    Bluetooth: hci0: command tx timeout

with patch:
    Bluetooth: hci0: Legacy ROM 2.5 revision 1.0 build 3 week 17 2014
    Bluetooth: hci0: Intel device is already patched. patch num: 32

Please apply to stable too.

Thanks

Ortwin

[-- Attachment #2: 0001-Bluetooth-btusb-Add-init-quitk.patch --]
[-- Type: text/x-patch, Size: 1434 bytes --]

From fb721988425ffd40e09603a3e8b141c0b46b74e0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ortwin=20Gl=C3=BCck?= <odi@odi.ch>
Date: Sat, 4 Dec 2021 14:25:56 +0100
Subject: [PATCH] Bluetooth: btusb: Add init quitk
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Fixes the boot regression against 5.14:
 Bluetooth: hci0: Reading Intel version command failed (-110)
 Bluetooth: hci0: command tx timeout

Signed-off-by: Ortwin Glück <odi@odi.ch>
Cc: stable@vger.kernel.org
---
 drivers/bluetooth/btusb.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index 79d0db542da3..232cfcb41734 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -366,7 +366,8 @@ static const struct usb_device_id blacklist_table[] = {
 	{ USB_DEVICE(0x8087, 0x07da), .driver_info = BTUSB_CSR },
 	{ USB_DEVICE(0x8087, 0x07dc), .driver_info = BTUSB_INTEL_COMBINED |
 						     BTUSB_INTEL_BROKEN_INITIAL_NCMD },
-	{ USB_DEVICE(0x8087, 0x0a2a), .driver_info = BTUSB_INTEL_COMBINED },
+	{ USB_DEVICE(0x8087, 0x0a2a), .driver_info = BTUSB_INTEL_COMBINED |
+						     BTUSB_INTEL_BROKEN_INITIAL_NCMD },
 	{ USB_DEVICE(0x8087, 0x0a2b), .driver_info = BTUSB_INTEL_COMBINED },
 	{ USB_DEVICE(0x8087, 0x0aa7), .driver_info = BTUSB_INTEL_COMBINED },
 	{ USB_DEVICE(0x8087, 0x0aaa), .driver_info = BTUSB_INTEL_COMBINED },
-- 
2.32.0


       reply	other threads:[~2021-12-27 10:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <856c5dc7-9fb4-8438-3451-7b369832056a@odi.ch>
2021-12-27 10:26 ` Ortwin Glück [this message]
2021-12-28  7:20   ` [PATCH] fix 5.15 init regression for Intel Bluetooth Thorsten Leemhuis
2021-12-28 10:46   ` Paul Menzel
2022-01-08  2:08   ` An, Tedd
2022-01-08 11:53     ` Thorsten Leemhuis

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=b0f6f66b-28aa-9d43-0aab-e6887ee0fda8@logobject.ch \
    --to=ortwin.glueck@logobject.ch \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --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 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).