Linux wireless drivers development
 help / color / mirror / Atom feed
From: Burke Cates <burke.cates@gmail.com>
To: baochen.qiang@oss.qualcomm.com
Cc: Jeff Johnson <jjohnson@kernel.org>,
	linux-wireless@vger.kernel.org, ath12k@lists.infradead.org
Subject: Re: [PATCH ath-next v4 00/11] wifi: ath12k: resolve RX link id via logical link id on WCN7850/QCC2072
Date: Mon,  2 Nov 2026 20:05:33 -0800	[thread overview]
Message-ID: <20261103040533.3388284-1-burke.cates@gmail.com> (raw)
In-Reply-To: <20261102-ath12k-logical-link-id-v4-0-f4c7807c299b@oss.qualcomm.com>

On Mon, Nov 02, 2026 at 02:38:09PM +0800, Baochen Qiang wrote:
> ath12k currently relies on hardware link id to resolve the link peer. This
> works for QCN9274, IPQ5332 and IPQ5424 but breaks WCN7850/QCC2072 which use
> logical link id instead.

Tested on an ASUS Zenbook A16 (UX3607OA, Snapdragon X2 Elite) with
the on-board QCC2072, on v7.4-rc1 plus c752394249f8, 02121aa4a012 and
1e678e37ff13 from ath.git and out-of-tree Glymur platform/board
patches, without Miaoqing's "fix MLO 4-way handshake timeout on
QCC2072". All 11 applied as posted.

A Wi-Fi 7 MLO SSID (SAE, PMF required, 2.4+5+6 GHz) that used to fail
with reason 15 connects as MLO with three links: 12 of 12
connect/disconnect cycles and 5 of 5 rejoins after s2idle resume,
ping OK each time. Non-MLO 5 GHz is unaffected. The firmware sends
PEER_EXTENDED, so the host allocation in 8/11 was not exercised.

Tested-on: QCC2072 hw1.0 PCI WLAN.COL.1.0.c2-00277-QCACOLSWPL_V1_TO_SILICONZ-1

Tested-by: Burke Cates <burke.cates@gmail.com> # ASUS Zenbook A16 (UX3607OA)

AI coding assistants helped run these tests and draft this reply; the
results are from the hardware runs.

Thanks,
Burke

  parent reply	other threads:[~2026-11-03  4:05 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-02  6:38 [PATCH ath-next v4 00/11] wifi: ath12k: resolve RX link id via logical link id on WCN7850/QCC2072 Baochen Qiang
2026-11-02  6:38 ` [PATCH ath-next v4 01/11] wifi: ath12k: fix potential OOB access due to unverified hardware link id Baochen Qiang
2026-11-02  6:38 ` [PATCH ath-next v4 02/11] wifi: ath12k: skip hw link id match for devices without hw link id support Baochen Qiang
2026-11-02  6:38 ` [PATCH ath-next v4 03/11] wifi: ath12k: rename ath12k_dp_peer::hw_links to link_id_map Baochen Qiang
2026-11-02  6:38 ` [PATCH ath-next v4 04/11] wifi: ath12k: rename ath12k_dp_link_peer::hw_link_id to drv_link_id Baochen Qiang
2026-11-02  6:38 ` [PATCH ath-next v4 05/11] wifi: ath12k: rename ath12k_skb_rxcb::hw_link_id " Baochen Qiang
2026-11-02  6:38 ` [PATCH ath-next v4 06/11] wifi: ath12k: derive device id without drv_link_id for single device group Baochen Qiang
2026-11-02  6:38 ` [PATCH ath-next v4 07/11] wifi: ath12k: add support for HTT_T2H_MSG_TYPE_PEER_EXTENDED event Baochen Qiang
2026-11-02  6:38 ` [PATCH ath-next v4 08/11] wifi: ath12k: allocate logical link id on host when firmware does not report it Baochen Qiang
2026-11-02  6:38 ` [PATCH ath-next v4 09/11] wifi: ath12k: derive REO RX drv_link_id per device via HAL ops Baochen Qiang
2026-11-02  6:38 ` [PATCH ath-next v4 10/11] wifi: ath12k: derive WBM " Baochen Qiang
2026-11-02  6:38 ` [PATCH ath-next v4 11/11] wifi: ath12k: use link_id_map to resolve RX link id for all devices Baochen Qiang
2026-11-10  6:07   ` Rameshkumar Sundaram
2026-11-10  6:36     ` Baochen Qiang
2026-11-10  6:39       ` Rameshkumar Sundaram
2026-11-03  4:05 ` Burke Cates [this message]
2026-11-03  5:17   ` [PATCH ath-next v4 00/11] wifi: ath12k: resolve RX link id via logical link id on WCN7850/QCC2072 Baochen Qiang
2026-11-03  5:20 ` Baochen Qiang
2026-11-03 15:26   ` Jeff Johnson
2026-11-14 19:35     ` Walt Holman
2026-11-16  5:28       ` Baochen Qiang
2026-11-16 13:10         ` Walt Holman

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=20261103040533.3388284-1-burke.cates@gmail.com \
    --to=burke.cates@gmail.com \
    --cc=ath12k@lists.infradead.org \
    --cc=baochen.qiang@oss.qualcomm.com \
    --cc=jjohnson@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