From: Greg KH <gregkh@linuxfoundation.org>
To: "Geoffrey D. Bennett" <g@b4.vu>
Cc: stable@vger.kernel.org, Marcel Holtmann <marcel@holtmann.org>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Luiz Augusto von Dentz <luiz.von.dentz@intel.com>,
Hao Qin <hao.qin@mediatek.com>,
linux-bluetooth@vger.kernel.org,
Sean Wang <sean.wang@mediatek.com>,
Chris Lu <chris.lu@mediatek.com>,
linux-sound@vger.kernel.org, Benedikt Ziemons <ben@rs485.network>,
pmenzel@molgen.mpg.de, tiwai@suse.de, geraldogabriel@gmail.com,
regressions@lists.linux.dev
Subject: Re: [STABLE 6.12/6.14] Bluetooth MediaTek controller reset fixes
Date: Mon, 12 May 2025 15:56:36 +0200 [thread overview]
Message-ID: <2025051222-obnoxious-blurred-cbcc@gregkh> (raw)
In-Reply-To: <aBxdpIabalg073AU@m.b4.vu>
On Thu, May 08, 2025 at 05:00:44PM +0930, Geoffrey D. Bennett wrote:
> Hi stable@vger.kernel.org,
>
> Could you please apply:
>
> 1. Commit a7208610761ae ("Bluetooth: btmtk: Remove resetting mt7921
> before downloading the fw") to v6.12.x (it's already in
> v6.14).
>
> 2. Commit 33634e2ab7c6 ("Bluetooth: btmtk: Remove the resetting step
> before downloading the fw") to v6.12.x and v6.14.x.
>
> These fixes address an issue with some audio interfaces failing to
> initialise during boot on kernels 6.11+. As noted in my original
> analysis below, the MediaTek Bluetooth controller reset increases the
> device setup time from ~200ms to ~20s and can interfere with other USB
> devices on the bus.
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2025-05-12 13:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 20:52 [PATCH v2] Revert "Bluetooth: btusb: mediatek: reset the controller before downloading the fw" Geoffrey D. Bennett
2025-03-27 21:15 ` [v2] " bluez.test.bot
2025-03-27 22:14 ` [PATCH v2] " Geoffrey D. Bennett
2025-05-08 7:30 ` [STABLE 6.12/6.14] Bluetooth MediaTek controller reset fixes Geoffrey D. Bennett
2025-05-12 13:56 ` Greg KH [this message]
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=2025051222-obnoxious-blurred-cbcc@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ben@rs485.network \
--cc=chris.lu@mediatek.com \
--cc=g@b4.vu \
--cc=geraldogabriel@gmail.com \
--cc=hao.qin@mediatek.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.org \
--cc=pmenzel@molgen.mpg.de \
--cc=regressions@lists.linux.dev \
--cc=sean.wang@mediatek.com \
--cc=stable@vger.kernel.org \
--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 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.