From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Andre Eikmeyer <dev@deq.rocks>
Cc: Arend van Spriel <arend.vanspriel@broadcom.com>,
Jakub Kicinski <kuba@kernel.org>,
Aditya Garg <gargaditya08@live.com>,
linux-wireless@vger.kernel.org, brcm80211@lists.linux.dev,
brcm80211-dev-list.pdl@broadcom.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] wifi: brcmfmac: handle missing D3 ACK on BCM4377 T2 Macs
Date: Sun, 4 Oct 2026 05:28:24 -0700 [thread overview]
Message-ID: <20261004122824.1390579-1-arend.vanspriel@broadcom.com> (raw)
In-Reply-To: <20261001085308.1688049-1-dev@deq.rocks>
On Thu, 1 Oct 2026 10:53:08 +0200, Andre Eikmeyer wrote:
> BCM4377 on the affected T2 Macs does not acknowledge HOST_D3_INFORM.
> The current PCIe suspend callback treats this as fatal and aborts system
> suspend.
>
> When this happens on BCM4377, mask the mailbox interrupt, preserve the
> bus-down state, and let generic PCI/ACPI suspend proceed. On resume the
> existing recovery path tears down and probes the device again instead of
> relying on a D0 mailbox transaction.
>
> Tested-on: MacBookAir9,1, MacBookPro15,4, MacBookPro16,3
> Signed-off-by: Andre Eikmeyer <dev@deq.rocks>
> ---
> drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c | 7 +++++++
> 1 file changed, 7 insertions(+)
Thanks for the patch. However, an earlier patch from Sebastian Reichel
already addresses this issue generically: "[wireless-next,v2] wifi: brcmfmac:
Improve D3 substate entering timeout handling" [1].
That patch makes the D3 ACK timeout non-fatal whenever Wake-on-WLAN is not
enabled, which covers BCM4377 as well and avoids the need for chip-specific
workarounds. I have accepted Sebastian's patch, so this one is superseded.
[1] https://lore.kernel.org/linux-wireless/20260915-brcmfmac-bcm43752-suspend-fix-v2-1-1bd84914998b@collabora.com/
Regards,
Arend
prev parent reply other threads:[~2026-10-04 12:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 21:30 [PATCH] wifi: brcmfmac: handle missing D3 ACK on BCM4377 T2 Macs Andre Eikmeyer
2026-09-19 22:05 ` Aditya Garg
2026-09-23 11:41 ` kernel test robot
2026-10-01 8:53 ` [PATCH v2] " Andre Eikmeyer
2026-10-04 12:28 ` Arend van Spriel [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=20261004122824.1390579-1-arend.vanspriel@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211@lists.linux.dev \
--cc=dev@deq.rocks \
--cc=gargaditya08@live.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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