From: Kalle Valo <kvalo@kernel.org>
To: david Atkins <david@3adesign.co.uk>
Cc: Baochen Qiang <quic_bqiang@quicinc.com>,
"ath12k@lists.infradead.org" <ath12k@lists.infradead.org>,
linux-wireless@vger.kernel.org
Subject: Re: wcn7850 issues
Date: Tue, 03 Sep 2024 10:47:51 +0300 [thread overview]
Message-ID: <871q21kwk8.fsf@kernel.org> (raw)
In-Reply-To: <LO0P123MB40578B26075CD4C9C66D144BD6932@LO0P123MB4057.GBRP123.PROD.OUTLOOK.COM> (david Atkins's message of "Tue, 3 Sep 2024 06:29:29 +0000")
+ linux-wireless
david Atkins <david@3adesign.co.uk> writes:
> ...
>> >>> Ext Tag: EHT Operation (802.11be D3.0)
>> >>> Ext Tag length: 8 (Tag len: 9)
>> >>> Ext Tag Number: EHT Operation (802.11be D3.0) (106)
>> >>> EHT Operation Parameters: 0x01, EHT Operation Information
>> Present
>> >>> .... ...1 = EHT Operation Information Present: True
>> >>> .... ..0. = Disabled Subchannel Bitmap Present: False
>> >>> .... .0.. = EHT Default PE Duration: False
>> >>> .... 0... = Group Addressed BU Indication Limit: False
>> >>> ..00 .... = Group Addressed BU Indication Exponent: 0
>> >>> 00.. .... = Reserved: 0x0
>> >>> Basic EHT-MCS And Nss Set: 0x44444444
>> >>> Control: 0x02, Channel Width: 80 MHz EHT BSS bandwidth
>> >>> .... .010 = Channel Width: 80 MHz EHT BSS bandwidth (2)
>> >>> 0000 0... = Reserved: 0x00
>> >>>
>> >>> Are you saying the ath12k driver does not support these features? If
>> >>> not can
>> >> you clarify the issue so I can raise with the AP team.
>> >>>
>> >> ath12k/WCN7850 supports EHT, but with NSS only 2. Here the AP
>> >> requires NSS to be no less than 4, that is why EHT connection was disabled.
>> >
>> > Which field is requiring NSS of 4, I'm only seeing a maximum of 4, the
>> Qualcomm windows driver will connect to the same AP, we had assumed that
>> that ath12k would do the same.
>> Basic EHT-MCS And Nss Set: 0x44444444
>
> My understanding of the spec is that there are maximum numbers of
> streams though, are you saying the AP has to advertise 0x22222222
> which would then prevent a 4x4 client (say an extender) from
> connecting with 4 streams? I note that the Qualcomm windows driver for
> Hamilton works with the AP and an Intel BE200 also works both of which
> will be in at most 2x2
Did you test Intel BE200 with the Windows driver? Johannes mentioned
that ieee80211_verify_sta_eht_mcs_support() in mac80211 checks this so I
would assume that iwlwifi also behaves like ath12k.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
https://docs.kernel.org/process/submitting-patches.html
next prev parent reply other threads:[~2024-09-03 7:52 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <LO0P123MB4057D6C2F6FEFF335B30EE7CD6BF2@LO0P123MB4057.GBRP123.PROD.OUTLOOK.COM>
2024-08-06 8:06 ` wcn7850 issues david Atkins
2024-08-13 13:20 ` david Atkins
2024-08-14 7:28 ` Kang Yang
2024-08-14 8:46 ` Lingbo Kong
2024-08-14 10:33 ` Baochen Qiang
2024-08-14 16:58 ` david Atkins
2024-08-14 10:42 ` Baochen Qiang
2024-08-14 17:00 ` david Atkins
2024-08-14 20:38 ` david Atkins
2024-08-15 2:15 ` Baochen Qiang
2024-08-16 12:23 ` david Atkins
2024-08-19 2:33 ` Baochen Qiang
2024-08-19 10:55 ` david Atkins
2024-08-30 5:55 ` david Atkins
2024-08-30 7:08 ` Baochen Qiang
2024-09-01 7:39 ` david Atkins
2024-09-02 1:56 ` Baochen Qiang
2024-09-02 6:03 ` david Atkins
2024-09-02 6:20 ` Baochen Qiang
2024-09-03 6:29 ` david Atkins
2024-09-03 7:47 ` Kalle Valo [this message]
2024-09-03 9:57 ` Janusz Dziedzic
2024-09-03 10:07 ` Johannes Berg
2024-09-03 10:09 ` Kalle Valo
2024-09-03 21:15 ` david Atkins
2024-09-04 5:08 ` Janusz Dziedzic
2024-09-04 6:04 ` david Atkins
2024-09-04 7:08 ` Janusz Dziedzic
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=871q21kwk8.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath12k@lists.infradead.org \
--cc=david@3adesign.co.uk \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_bqiang@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