mirror of https://lore.kernel.org/ath12k/
 help / color / mirror / Atom feed
From: Aloka Dixit <quic_alokad@quicinc.com>
To: Wen Gong <quic_wgong@quicinc.com>, <ath12k@lists.infradead.org>,
	<linux-wireless@vger.kernel.org>
Cc: Pradeep Kumar Chitrapu <quic_pradeepc@quicinc.com>
Subject: Re: [PATCH v4 06/11] wifi: ath12k: prepare EHT peer assoc parameters
Date: Tue, 25 Jul 2023 15:44:13 -0700	[thread overview]
Message-ID: <54dc7722-0335-e585-56fd-c01318c52ed4@quicinc.com> (raw)
In-Reply-To: <f9f53552-4823-c841-866a-77057bef0b11@quicinc.com>

On 7/25/2023 3:07 AM, Wen Gong wrote:
> 
> For station mode of ath12k, the eht_cap->eht_mcs_nss_supp is from the IE 
> "Supported
> EHT-MCS and NSS Set" in assoc resp of AP in function 
> ieee80211_eht_cap_ie_to_sta_eht_cap().
> Now it is "EHT-MCS Map (BW <= 80MHz): 0x222222" for the AP(11BE-EHT mode 
> for 20 MHz
> bandwidth on 6 GHz band) in my test as below IEs.
> 
> The field only_20mhz and field _80 are union in struct 
> ieee80211_eht_mcs_nss_supp, the
> value of field _80 is 0x222222 for this AP, then the value of field 
> only_20mhz is like this:
> rx_tx_mcs7_max_nss=0x22,
> rx_tx_mcs9_max_nss=0x22,
> rx_tx_mcs11_max_nss=0x22,
> rx_tx_mcs13_max_nss=0.
> 
> Then ath12k_mac_set_eht_mcs() will get value 0 fro mcs13 because it used 
> the field only_20mhz
> passed by ath12k_peer_assoc_h_eht().
> 

Understood, I fixed the default case to check for the he_cap field for 
the bandwidth support instead of peer_phymode in v5.

-- 
ath12k mailing list
ath12k@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/ath12k

  reply	other threads:[~2023-07-25 22:44 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-02 23:58 [PATCH v4 00/11] wifi: ath12k: (v4) EHT support Aloka Dixit
2023-06-02 23:58 ` [PATCH v4 01/11] wifi: ath12k: rename HE capabilities setup/copy functions Aloka Dixit
2023-06-02 23:58 ` [PATCH v4 02/11] wifi: ath12k: move HE capabilities processing to a new function Aloka Dixit
2023-06-02 23:58 ` [PATCH v4 03/11] wifi: ath12k: WMI support to process EHT capabilities Aloka Dixit
2023-06-15 11:49   ` Kalle Valo
2023-06-16 10:50     ` Wen Gong
2023-07-24 17:42       ` Aloka Dixit
2023-07-25 10:51     ` Wen Gong
2023-07-25 19:44       ` Aloka Dixit
2023-06-02 23:58 ` [PATCH v4 04/11] wifi: ath12k: propagate EHT capabilities to userspace Aloka Dixit
2023-06-15 11:51   ` Kalle Valo
2023-07-24 18:11     ` Aloka Dixit
2023-06-02 23:58 ` [PATCH v4 05/11] wifi: ath12k: add EHT PHY modes Aloka Dixit
2023-06-02 23:58 ` [PATCH v4 06/11] wifi: ath12k: prepare EHT peer assoc parameters Aloka Dixit
2023-07-24 10:16   ` Wen Gong
2023-07-24 18:24     ` Aloka Dixit
2023-07-25 10:07       ` Wen Gong
2023-07-25 22:44         ` Aloka Dixit [this message]
2023-06-02 23:58 ` [PATCH v4 07/11] wifi: ath12k: add WMI support for EHT peer Aloka Dixit
2023-06-02 23:58 ` [PATCH v4 08/11] wifi: ath12k: peer assoc for 320 MHz Aloka Dixit
2023-06-02 23:58 ` [PATCH v4 09/11] wifi: ath12k: add MLO header in peer association Aloka Dixit
2023-06-02 23:58 ` [PATCH v4 10/11] wifi: ath12k: parse WMI service ready ext2 event Aloka Dixit
2023-06-02 23:58 ` [PATCH v4 11/11] wifi: ath12k: configure puncturing bitmap Aloka Dixit
2023-06-15 11:47 ` [PATCH v4 00/11] wifi: ath12k: (v4) EHT support Kalle Valo
2023-07-24 17:43   ` Aloka Dixit

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=54dc7722-0335-e585-56fd-c01318c52ed4@quicinc.com \
    --to=quic_alokad@quicinc.com \
    --cc=ath12k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=quic_pradeepc@quicinc.com \
    --cc=quic_wgong@quicinc.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