linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Menzel <pmenzel@molgen.mpg.de>
To: "Ortwin Glück" <ortwin.glueck@logobject.ch>
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>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix 5.15 init regression for Intel Bluetooth
Date: Tue, 28 Dec 2021 11:46:43 +0100	[thread overview]
Message-ID: <c26d4792-0efa-d661-faec-cb00c68132e0@molgen.mpg.de> (raw)
In-Reply-To: <b0f6f66b-28aa-9d43-0aab-e6887ee0fda8@logobject.ch>

Dear Ortwin,


Am 27.12.21 um 11:26 schrieb Ortwin Glück:

> 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.

This has been already reported in *[PATCH] Bluetooth: Apply initial 
command workaround for more Intel chips* [1].

As I replied there, on what device do you experience this, and how can 
it be reproduced?

I have a Dell Latitude E7250 with the Bluetooth device 0x0a2a, and 
everything works fine under Debian sid/unstable with Linux 5.15 up to 
5.16-rc6.

     Bus 002 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless 
interface


Kind regards,

Paul


[1]: 
https://lore.kernel.org/linux-bluetooth/20211202162256.31837-1-tiwai@suse.de/

  parent reply	other threads:[~2021-12-28 10:46 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 ` [PATCH] fix 5.15 init regression for Intel Bluetooth Ortwin Glück
2021-12-28  7:20   ` Thorsten Leemhuis
2021-12-28 10:46   ` Paul Menzel [this message]
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=c26d4792-0efa-d661-faec-cb00c68132e0@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=ortwin.glueck@logobject.ch \
    /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).