From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: "André Eikmeyer" <dev@deq.rocks>
Cc: linux-wireless@vger.kernel.org, brcm80211@lists.linux.dev,
brcm80211-dev-list.pdl@broadcom.com,
linux-kernel@vger.kernel.org, sebastian.reichel@collabora.com,
Lukas Klizas <lukas@klizas.lt>,
Yossef Osman <Yossef.Osman@proton.me>,
Aditya Garg <aditya.garg@linux.dev>
Subject: Re: [PATCH] wifi: brcmfmac: reload the firmware after a missing D3 ACK
Date: Wed, 18 Nov 2026 13:21:45 +0100 [thread overview]
Message-ID: <0d8104b6-888f-475a-99e0-0275c12f7a76@broadcom.com> (raw)
In-Reply-To: <20261118125034.4d257b01@kait2en-mbp15-1>
On 18/11/2026 12:50, André Eikmeyer wrote:
> On Tue, 17 Nov 2026 13:12:49 +0100
> Arend van Spriel <arend.vanspriel@broadcom.com> wrote:
>
> Hi Arend,
>
>> It is all you ;-) so you can probably confirm whether this is indeed
>> superseded by the series mentioned above. I marked it as such in
>> linux-wireless patchwork.
>
> Yes, confirmed. Patches 3/5 and 4/5 of the T2 suspend series cover both
> parts of it.
>
> The same goes for the older "wifi: brcmfmac: handle missing D3 ACK on
> BCM4377 T2 Macs" v2 [1]. With Michael's mailbox over the control ring
> the BCM4377 ACKs D3, so that workaround is not needed anymore and can
> be dropped as well.
Understood. Thanks for the confirmation.
Regards,
Arend
prev parent reply other threads:[~2026-11-18 12:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 15:16 Andre Eikmeyer
2026-11-16 11:08 ` Arend van Spriel
2026-11-17 12:12 ` Arend van Spriel
2026-11-18 11:50 ` André Eikmeyer
2026-11-18 12:21 ` 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=0d8104b6-888f-475a-99e0-0275c12f7a76@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=Yossef.Osman@proton.me \
--cc=aditya.garg@linux.dev \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211@lists.linux.dev \
--cc=dev@deq.rocks \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lukas@klizas.lt \
--cc=sebastian.reichel@collabora.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®