Linux-Wireless Archive mirror
 help / color / mirror / Atom feed
From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: Pradeep Kumar Chitrapu <quic_pradeepc@quicinc.com>,
	<ath12k@lists.infradead.org>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH V4 10/10] wifi: ath12k: add extended NSS bandwidth support for 160 MHz
Date: Mon, 13 May 2024 13:56:15 -0700	[thread overview]
Message-ID: <15047448-4fb1-4024-8d62-1922e8f15940@quicinc.com> (raw)
In-Reply-To: <20240508002055.17705-11-quic_pradeepc@quicinc.com>

On 5/7/2024 5:20 PM, Pradeep Kumar Chitrapu wrote:
> Currently rx and tx MCS map for 160 MHz under HE capabilities
> are not updating properly, when 160 MHz is configured with NSS
> lesser than max NSS support. Fix this by utilizing
> nss_ratio_enabled and nss_ratio_info fields sent by firmware
> in service ready event.
> 
> However, if firmware advertises EXT NSS BW support in VHT caps
> as 1(1x2) and when nss_ratio_info indicates 1:1, reset the EXT
> NSS BW Support in VHT caps to 0 which indicates 1x1. This is
> to avoid incorrectly chosing 1:2 NSS ratio when using the

s/chosing /choosing /

> default VHT caps advertised by firmware.
> 
> Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.0.1-00029-QCAHKSWPL_SILICONZ-1
> 
> Signed-off-by: Pradeep Kumar Chitrapu <quic_pradeepc@quicinc.com>
Acked-by: Jeff Johnson <quic_jjohnson@quicinc.com>


      reply	other threads:[~2024-05-13 20:56 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-08  0:20 [PATCH V4 00/10] wifi: ath12k: add MU-MIMO and 160 MHz bandwidth support Pradeep Kumar Chitrapu
2024-05-08  0:20 ` [PATCH V4 01/10] wifi: mac80211: Add EHT UL MU-MIMO flag in ieee80211_bss_conf Pradeep Kumar Chitrapu
2024-05-13 20:49   ` Jeff Johnson
2024-05-15 16:10     ` Pradeep Kumar Chitrapu
2024-05-08  0:20 ` [PATCH V4 02/10] wifi: ath12k: push HE MU-MIMO params to hardware Pradeep Kumar Chitrapu
2024-05-13 20:50   ` Jeff Johnson
2024-05-08  0:20 ` [PATCH V4 03/10] wifi: ath12k: push EHT " Pradeep Kumar Chitrapu
2024-05-13 20:50   ` Jeff Johnson
2024-05-08  0:20 ` [PATCH V4 04/10] wifi: ath12k: move HE MCS mapper to a separate function Pradeep Kumar Chitrapu
2024-05-13 20:50   ` Jeff Johnson
2024-05-08  0:20 ` [PATCH V4 05/10] wifi: ath12k: generate rx and tx mcs maps for supported HE mcs Pradeep Kumar Chitrapu
2024-05-13 20:51   ` Jeff Johnson
2024-05-08  0:20 ` [PATCH V4 06/10] wifi: ath12k: fix TX and RX MCS rate configurations in HE mode Pradeep Kumar Chitrapu
2024-05-13 20:52   ` Jeff Johnson
2024-05-08  0:20 ` [PATCH V4 07/10] wifi: ath12k: add support for setting fixed HE rate/GI/LTF Pradeep Kumar Chitrapu
2024-05-13 20:52   ` Jeff Johnson
2024-05-08  0:20 ` [PATCH V4 08/10] wifi: ath12k: clean up 80P80 support Pradeep Kumar Chitrapu
2024-05-13 20:52   ` Jeff Johnson
2024-05-08  0:20 ` [PATCH V4 09/10] wifi: ath12k: add support for 160 MHz bandwidth Pradeep Kumar Chitrapu
2024-05-13 20:54   ` Jeff Johnson
2024-05-15 16:10     ` Pradeep Kumar Chitrapu
2024-05-08  0:20 ` [PATCH V4 10/10] wifi: ath12k: add extended NSS bandwidth support for 160 MHz Pradeep Kumar Chitrapu
2024-05-13 20:56   ` Jeff Johnson [this message]

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=15047448-4fb1-4024-8d62-1922e8f15940@quicinc.com \
    --to=quic_jjohnson@quicinc.com \
    --cc=ath12k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=quic_pradeepc@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).