From: Rong Zhang <i@rong.moe>
To: "Michal Pecio" <michal.pecio@gmail.com>,
"Chris Lu (陸稚泓)" <Chris.Lu@mediatek.com>
Cc: "Alberto Garcia" <berto@igalia.com>,
sean.wang@kernel.org,
"luiz.dentz@gmail.com" <luiz.dentz@gmail.com>,
"Will-CY Lee (李政穎)" <Will-CY.Lee@mediatek.com>,
"marcel@holtmann.org" <marcel@holtmann.org>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"SS Wu (巫憲欣)" <ss.wu@mediatek.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
"patchwork-bot+bluetooth@kernel.org"
<patchwork-bot+bluetooth@kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>
Subject: Re: [PATCH] Bluetooth: btmtk: Disable remote wakeup for MT7922/MT7925
Date: Tue, 11 Aug 2026 04:03:38 +0800 [thread overview]
Message-ID: <868e97331dc74f176db2d3efdd1c579049b8e493.camel@rong.moe> (raw)
In-Reply-To: <20260809223320.24431a4a.michal.pecio@gmail.com>
Hi Michal,
Thanks for your insight.
On Sun, 2026-08-09 at 22:33 +0200, Michal Pecio wrote:
> On Mon, 29 Jun 2026 03:01:19 +0000, Chris Lu (陸稚泓) wrote:
> > Hi Rong,
> >
> > Thanks for your understanding. We hope to find a better way to handle
> > this issue.
> >
> >
> > Hi Luiz,
> >
> > Regarding this issue, MediaTek Bluetooth team has already initialed an
> > internal investigation for problematic combination and will seek
> > assistance from AMD SOC team to investigate the root cause of this
> > issue.
>
> Hi,
>
> I have seen multiple reports on Arch Linux forum of MTK Bluetooth chips
> sporadically locking up and no longer enumerating on AMD systems, also
> desktops, which had to be unplugged from power to restore operation.
>
> I have also seen claims that auto power management is broken in btusb:
> https://lore.kernel.org/linux-bluetooth/cover.1774348119.git.berto@igalia.com/T/#u
I believe the proper fix of autopm failure during initialization is
https://lore.kernel.org/linux-bluetooth/20250319231235.812700-1-sean.wang@kernel.org/
Some time earlier this year I was planing to pick it up and push it
forward, but it turned out I was too busy. Maybe I will find some time...
That being said, the bug I encountered has nothing to with the device
initialization though.
>
> This, if true, offers a plausible theory because:
> - URBs issued to suspended devices may fail, drivers may not notice,
> make wrong assumptions about their HW state and confuse the chip
> - USB core doesn't reliably block submission of such URBs
Not the case of my devices. Autosuspend and (non-remote) autowakeup
always work fine. The only thing that triggers the bug is a random[1]
remote wakeup.
Usbmon always shows no URB between the autosuspend and the subsequent
remote wakeup, expect for the interrupt from the root hub.
[1]: it happens when no Bluetooth device is trying to establish a
connection.
> - they were also seen to break some xHCI controllers, in theory this
> might be an HC problem - power cycling resets both device and HC
I also think this might be one of the reasons.
Thanks,
Rong
>
> Regards,
> Michal
next prev parent reply other threads:[~2026-08-10 20:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 18:38 Rong Zhang
2026-06-03 17:50 ` patchwork-bot+bluetooth
2026-06-26 2:40 ` Chris Lu (陸稚泓)
2026-06-26 11:19 ` Rong Zhang
2026-06-26 16:54 ` Luiz Augusto von Dentz
2026-06-26 17:56 ` Chris Lu (陸稚泓)
2026-06-26 19:56 ` Rong Zhang
2026-06-29 3:01 ` Chris Lu (陸稚泓)
2026-08-09 20:33 ` Michal Pecio
2026-08-10 20:03 ` Rong Zhang [this message]
2026-08-17 9:44 ` Alberto Garcia
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=868e97331dc74f176db2d3efdd1c579049b8e493.camel@rong.moe \
--to=i@rong.moe \
--cc=Chris.Lu@mediatek.com \
--cc=Will-CY.Lee@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=berto@igalia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=matthias.bgg@gmail.com \
--cc=michal.pecio@gmail.com \
--cc=patchwork-bot+bluetooth@kernel.org \
--cc=sean.wang@kernel.org \
--cc=ss.wu@mediatek.com \
/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
all inboxes | Powered by JetHome®