From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Tedd Ho-Jeong An <tedd.an@intel.com>,
linux-kernel@vger.kernel.org, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: Apply initial command workaround for more Intel chips
Date: Thu, 2 Dec 2021 17:32:14 +0100 [thread overview]
Message-ID: <acc7b5b4-72cc-9f3b-90a6-6fbf6c3a71e7@molgen.mpg.de> (raw)
In-Reply-To: <20211202162256.31837-1-tiwai@suse.de>
Dear Takashi,
Am 02.12.21 um 17:22 schrieb Takashi Iwai:
> It seems that a few more Intel chips require the workaround for the
> broken initial command. At least, per openSUSE Bugzilla reports,
> 8087:0a2a and 8087:0026 need BTUSB_INTEL_BROKEN_INITIAL_NCMD flag.
>
> Fixes: 83f2dafe2a62 ("Bluetooth: btintel: Refactoring setup routine for legacy ROM sku")
> Buglink: https://bugzilla.opensuse.org/show_bug.cgi?id=1193124
> Signed-off-by: Takashi Iwai <tiwai@suse.de>
>
[…]
I have a Dell Latitude E7250 with
Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless
interface
and Bluetooth seems to work fine minus some Linux warnings [1] and a
problem transferring greater than some bytes files with the Nokia N9 [2].
Linux 5.16-rc3, Dell Inc. Latitude E7250/0TVD2T, BIOS A19 01/23/2018:
```
$ sudo dmesg | grep -i bluet
[ 8.173417] calling bt_init+0x0/0xb3 [bluetooth] @ 301
[ 8.173439] Bluetooth: Core ver 2.22
[ 8.173463] NET: Registered PF_BLUETOOTH protocol family
[ 8.173464] Bluetooth: HCI device and connection manager initialized
[ 8.173467] Bluetooth: HCI socket layer initialized
[ 8.173470] Bluetooth: L2CAP socket layer initialized
[ 8.173473] Bluetooth: SCO socket layer initialized
[ 8.173475] initcall bt_init+0x0/0xb3 [bluetooth] returned 0 after 35
usecs
[ 8.216875] Bluetooth: hci0: Legacy ROM 2.5 revision 1.0 build 3 week
17 2014
[ 8.233515] bluetooth hci0: firmware: direct-loading firmware
intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[ 8.233520] Bluetooth: hci0: Intel Bluetooth firmware file:
intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[ 8.540884] Bluetooth: hci0: unexpected event for opcode 0xfc2f
[ 8.558942] Bluetooth: hci0: Intel BT fw patch 0x32 completed & activated
```
Kind regards,
Paul
[1]: https://bugzilla.kernel.org/show_bug.cgi?id=215189
[2]:
https://lore.kernel.org/linux-bluetooth/cf71bdea-ec22-e4c9-016c-69e94a130607@molgen.mpg.de/T/#t
next prev parent reply other threads:[~2021-12-02 16:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 16:22 [PATCH] Bluetooth: Apply initial command workaround for more Intel chips Takashi Iwai
2021-12-02 16:32 ` Paul Menzel [this message]
2021-12-02 16:47 ` Takashi Iwai
2021-12-02 16:58 ` Paul Menzel
2021-12-03 7:24 ` Takashi Iwai
2021-12-03 21:18 ` Marcel Holtmann
2021-12-04 11:20 ` Takashi Iwai
2021-12-05 10:33 ` Fernando Ramos
2021-12-07 16:14 ` Marcel Holtmann
2021-12-10 13:23 ` Takashi Iwai
2022-01-16 14:06 ` Paul Menzel
2022-01-20 14:26 ` Thorsten Leemhuis
2022-01-20 15:07 ` Marcel Holtmann
2022-01-20 15:13 ` Thorsten Leemhuis
2022-01-20 14:32 ` Takashi Iwai
2021-12-28 12:43 ` 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=acc7b5b4-72cc-9f3b-90a6-6fbf6c3a71e7@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--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 \
--cc=tedd.an@intel.com \
--cc=tiwai@suse.de \
/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).