All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Glotzer <jglotzer@gmail.com>
To: rtl8821cerfe2@gmail.com
Cc: Aaron.Hou@mediatek.com, Chris.Lu@mediatek.com,
	Deren.Wu@mediatek.com, Hao.Qin@mediatek.com,
	Sean.Wang@mediatek.com, jglotzer@gmail.com,
	johan.hedberg@gmail.com, linux-bluetooth@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
	luiz.dentz@gmail.com, marc.payne@mdpsys.co.uk,
	marcel@holtmann.org, regressions@lists.linux.dev,
	sergio.callegari@unibo.it, steve.lee@mediatek.com, tiwai@suse.de
Subject: Re: [PATCH] Bluetooth: btmtk: Remove resetting mt7921 before downloading the fw
Date: Wed, 29 Jan 2025 12:31:09 -0600	[thread overview]
Message-ID: <20250129183109.10770-1-jglotzer@gmail.com> (raw)
In-Reply-To: <585f1075-a662-489b-bd5c-cf9f24291804@gmail.com>

Good news/TLDR
   Yes, so far I have resumed from sleep 2x without any issues
   with both of my workarounds disabled (kernel command line/systemd rfkill on sleep).

What I don't yet understand
   This commit
   (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/diff/drivers/bluetooth/btusb.c?id=v6.12.8&id2=v6.12.7)
   was a pure USB fix. My mt7922 device (not a USB dongle but built into the motherboard)
   seems to be both a bluetooth device (bound to btusb driver) *and* a Wifi device (bound to mt7921e driver).

   I remain puzzled as to how is it that the issue that is on the USB side was *also* fixed by
   adding mt7921e.disable_aspm=y to the kernel command line (since that would act on the wifi/pci pathway)?

  reply	other threads:[~2025-01-29 18:31 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-22  5:23 [PATCH] Bluetooth: btmtk: Remove resetting mt7921 before downloading the fw Hao Qin
2024-09-10 17:09 ` Marc Payne
2024-09-12  7:09   ` Chris Lu (陸稚泓)
2024-09-17 19:53     ` marc.payne
     [not found]       ` <9bfbbf24ac2480d94d3455f7e33e4b5502b38ced.camel@mediatek.com>
2024-09-18 13:37         ` Luiz Augusto von Dentz
2024-09-19  3:26           ` Chris Lu (陸稚泓)
2024-09-19 22:25             ` marc.payne
2024-09-20  6:27               ` Chris Lu (陸稚泓)
2024-10-14  9:29                 ` Linux regression tracking (Thorsten Leemhuis)
2024-10-22 10:56                   ` Takashi Iwai
2024-10-30  9:21                     ` Thorsten Leemhuis
2024-10-30 11:03                       ` Chris Lu (陸稚泓)
2024-10-30 11:29                         ` Thorsten Leemhuis
2024-11-01  7:11                           ` Chris Lu (陸稚泓)
2024-11-01 14:22                             ` Thorsten Leemhuis
2024-11-02 10:04                               ` Takashi Iwai
2024-11-11  9:21                                 ` Linux regression tracking (Thorsten Leemhuis)
2025-01-13 22:18                                   ` Sergio Callegari
2025-01-18 16:58                                     ` John Glotzer
2025-01-28  0:04                                       ` Bitterblue Smith
2025-01-29 18:31                                         ` John Glotzer [this message]
2024-11-27 23:14                               ` [REGRESSION] bluetooth: mt7921: Crash on Resume From Suspend And Hibernate John Glotzer
2024-12-05 12:59                                 ` Sergio Callegari
2024-12-06  2:29                                   ` John Glotzer
2024-12-21  9:52                                   ` Sergio Callegari
2024-09-18 16:02         ` [PATCH] Bluetooth: btmtk: Remove resetting mt7921 before downloading the fw marc.payne
  -- strict thread matches above, loose matches on Subject: below --
2025-01-10  9:55 Hao Qin
2025-01-14 17:20 ` patchwork-bot+bluetooth

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=20250129183109.10770-1-jglotzer@gmail.com \
    --to=jglotzer@gmail.com \
    --cc=Aaron.Hou@mediatek.com \
    --cc=Chris.Lu@mediatek.com \
    --cc=Deren.Wu@mediatek.com \
    --cc=Hao.Qin@mediatek.com \
    --cc=Sean.Wang@mediatek.com \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marc.payne@mdpsys.co.uk \
    --cc=marcel@holtmann.org \
    --cc=regressions@lists.linux.dev \
    --cc=rtl8821cerfe2@gmail.com \
    --cc=sergio.callegari@unibo.it \
    --cc=steve.lee@mediatek.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 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.