From: Richard Acayan <mailingradian@gmail.com>
To: Jeff Johnson <jjohnson@kernel.org>,
Michal Kazior <michal.kazior@tieto.com>,
Kalle Valo <kvalo@qca.qualcomm.com>,
linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Cc: Richard Acayan <mailingradian@gmail.com>
Subject: [RFC PATCH 0/2] ath10k wifi fixes
Date: Mon, 9 Feb 2026 21:12:47 -0500 [thread overview]
Message-ID: <20260210021249.12132-1-mailingradian@gmail.com> (raw)
These are WiFi fixes that seem to be helpful on SDM670. There is no
ath10k support for SDM670, but some similar SoCs also need these fixes.
This is RFC because there could be better solutions.
On SDM670 with patches, the MPDU has 32 MSDUs when the last one isn't
the last in the A-MSDU.
Richard Acayan (2):
wifi: ath10k: make in-order rx amsdu buffers persistent
wifi: ath10k: only wait for response to SET_KEY
drivers/net/wireless/ath/ath10k/htt.h | 4 +++
drivers/net/wireless/ath/ath10k/htt_rx.c | 41 ++++++++++++++++++------
drivers/net/wireless/ath/ath10k/mac.c | 8 +++--
3 files changed, 41 insertions(+), 12 deletions(-)
--
2.53.0
next reply other threads:[~2026-02-10 2:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 2:12 Richard Acayan [this message]
2026-02-10 2:12 ` [RFC PATCH 1/2] wifi: ath10k: make in-order rx amsdu buffers persistent Richard Acayan
2026-02-12 17:38 ` Jeff Johnson
2026-02-10 2:12 ` [RFC PATCH 2/2] wifi: ath10k: only wait for response to SET_KEY Richard Acayan
2026-02-12 2:11 ` James Prestwood
2026-02-12 17:56 ` Jeff Johnson
2026-02-13 14:00 ` James Prestwood
2026-02-18 4:14 ` Felix Kaechele
2026-02-26 2:59 ` Baochen Qiang
2026-02-27 17:28 ` James Prestwood
2026-02-12 18:36 ` Felix Kaechele
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=20260210021249.12132-1-mailingradian@gmail.com \
--to=mailingradian@gmail.com \
--cc=ath10k@lists.infradead.org \
--cc=jjohnson@kernel.org \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.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