From: "André Eikmeyer" <dev@deq.rocks>
To: "Kordian Chmielewski (mlody1212)" <kudzo51@gmail.com>
Cc: arend.vanspriel@broadcom.com, asahi@lists.linux.dev,
brcm80211-dev-list.pdl@broadcom.com, brcm80211@lists.linux.dev,
j@jannau.net, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org, marcan@marcan.st,
michael.reeves077@gmail.com, sebastian.reichel@collabora.com
Subject: Re: [PATCH 4/4] wifi: brcmfmac: msgbuf: send the flowring delete without waiting for tx status
Date: Wed, 11 Nov 2026 20:07:14 +0100 [thread overview]
Message-ID: <20261111200714.7897345f@kait2en-mbp15-1> (raw)
In-Reply-To: <20261110231248.206892-1-kudzo51@gmail.com>
On Wed, 11 Nov 2026 00:12:47 +0100
"Kordian Chmielewski (mlody1212)" <kudzo51@gmail.com> wrote:
> Do you know how the
> firmware orders them? In my tree each tx pktid keeps the generation of
> its flowring for that case; I can send it on top of your patch if it
> turns out to be needed.
Hi Kordian,
On the BCM4377 I have a trace of a disconnect with debug output. The
status messages are processed before both delete responses. But they
come on the complete ring and the responses on the control complete
ring. And brcmf_proto_msgbuf_rx_trigger() always drains the tx complete
ring first. So that only shows the order within one interrupt.
Please send your generation patch on top. That should close it
independent of firmware ordering.
Andre
next prev parent reply other threads:[~2026-11-11 19:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-07 15:48 [PATCH 0/4] wifi: brcmfmac: pcie: S3 suspend and resume on the T2 Mac chips Andre Eikmeyer
2026-11-07 15:48 ` [PATCH 1/4] wifi: brcmfmac: pcie: set the state before D0_INFORM on resume Andre Eikmeyer
2026-11-07 15:48 ` [PATCH 2/4] wifi: brcmfmac: pcie: skip the host ready doorbell at init once it is a capability Andre Eikmeyer
2026-11-07 15:48 ` [PATCH 3/4] wifi: brcmfmac: pcie: probe again after a resume through firmware Andre Eikmeyer
2026-11-07 15:48 ` [PATCH 4/4] wifi: brcmfmac: msgbuf: send the flowring delete without waiting for tx status Andre Eikmeyer
2026-11-10 23:12 ` Kordian Chmielewski (mlody1212)
2026-11-11 19:07 ` André Eikmeyer [this message]
2026-11-11 19:55 ` [PATCH wireless-next] wifi: brcmfmac: msgbuf: count tx status only for the current flowring Kordian Chmielewski (mlody1212)
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=20261111200714.7897345f@kait2en-mbp15-1 \
--to=dev@deq.rocks \
--cc=arend.vanspriel@broadcom.com \
--cc=asahi@lists.linux.dev \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211@lists.linux.dev \
--cc=j@jannau.net \
--cc=kudzo51@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=michael.reeves077@gmail.com \
--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®