Linux wireless drivers development
 help / color / mirror / Atom feed
From: Rameshkumar Sundaram <rameshkumar.sundaram@oss.qualcomm.com>
To: Baochen Qiang <baochen.qiang@oss.qualcomm.com>,
	Jeff Johnson <jjohnson@kernel.org>
Cc: linux-wireless@vger.kernel.org, ath12k@lists.infradead.org
Subject: Re: [PATCH ath-next v4 11/11] wifi: ath12k: use link_id_map to resolve RX link id for all devices
Date: Tue, 10 Nov 2026 12:09:07 +0530	[thread overview]
Message-ID: <d70e7ded-a378-4f7b-a599-df59f27e81e5@oss.qualcomm.com> (raw)
In-Reply-To: <c78e9194-ba3c-47ea-8876-9bf6bba4d7ef@oss.qualcomm.com>

On 11/10/2026 12:06 PM, Baochen Qiang wrote:
> 
> 
> On 11/10/2026 2:07 PM, Rameshkumar Sundaram wrote:
>> On 11/2/2026 12:08 PM, Baochen Qiang wrote:
>>> Commit a2fe9dc70f3b ("wifi: ath12k: Fix low MLO RX throughput on
>>> WCN7850") added a set_rx_link_id() op so that each device could resolve
>>> the RX link id in its own way: QCN9274/IPQ5332 index
>>> dp_peer->link_id_map[] with the hw_link_id, while WCN7850/QCC2072 walk
>>> dp_peer->link_peers[] and match by peer_id, tracked with a link_peers_map
>>> bitmap.
>>>
>>> Now that ath12k_skb_rxcb::drv_link_id carries the driver link id for all
>>> devices (the hw_link_id on QCN9274/IPQ5332 and the logical link id on
>>> WCN7850/QCC2072) and ath12k_dp_peer::link_id_map maps it to the IEEE80211
>>> link id, the RX path can resolve the link id uniformly.
>>>
>>> Revert the set_rx_link_id() machinery and the link_peers_map bitmap, and
>>> derive the link id directly from link_id_map[drv_link_id] in
>>> ath12k_dp_rx_deliver_msdu() for all devices. The NULL dp_peer guard added
>>> to ath12k_mac_peer_cleanup_all() is kept as it is an independent fix.
>>>
>>
>> Fixes: a2fe9dc70f3b ("wifi: ath12k: Fix low MLO RX throughput on WCN7850") ??
> 
> hmm, not sure here, since it would need to backport the whole series which is too large
> for a stable backport.
> 


Yeah, makes sense. Let's leave out the Fixes tag.

-- 
Ramesh

  reply	other threads:[~2026-11-10  6:39 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 [this message]
2026-11-03  4:05 ` [PATCH ath-next v4 00/11] wifi: ath12k: resolve RX link id via logical link id on WCN7850/QCC2072 Burke Cates
2026-11-03  5:17   ` 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=d70e7ded-a378-4f7b-a599-df59f27e81e5@oss.qualcomm.com \
    --to=rameshkumar.sundaram@oss.qualcomm.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