From: Kalle Valo <kvalo@kernel.org>
To: Baochen Qiang <quic_bqiang@quicinc.com>
Cc: <ath11k@lists.infradead.org>, <linux-wireless@vger.kernel.org>,
regressions@lists.linux.dev
Subject: Re: [PATCH v2] wifi: ath11k: move power type check to ASSOC stage when connecting to 6 GHz AP
Date: Sat, 11 May 2024 12:54:33 +0300 [thread overview]
Message-ID: <87wmo0k71i.fsf@kernel.org> (raw)
In-Reply-To: <20240424064019.4847-1-quic_bqiang@quicinc.com> (Baochen Qiang's message of "Wed, 24 Apr 2024 14:40:19 +0800")
Baochen Qiang <quic_bqiang@quicinc.com> writes:
> With commit bc8a0fac8677 ("wifi: mac80211: don't set bss_conf in parsing")
> ath11k fails to connect to 6 GHz AP.
>
> This is because currently ath11k checks AP's power type in
> ath11k_mac_op_assign_vif_chanctx() which would be called in AUTH stage.
> However with above commit power type is not available until ASSOC stage.
> As a result power type check fails and therefore connection fails.
>
> Fix this by moving power type check to ASSOC stage, also move regulatory
> rules update there because it depends on power type.
>
> Tested-on: WCN6855 hw2.0 PCI WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.30
>
> Fixes: bc8a0fac8677 ("wifi: mac80211: don't set bss_conf in parsing")
> Signed-off-by: Baochen Qiang <quic_bqiang@quicinc.com>
Oh, this fell through the cracks. Commit bc8a0fac8677 was introduced in
v6.9-rc1 so I should have sent this to v6.9 but it's too late now. I'll
need to queue this for v6.10 via wireless tree.
Adding the regression also to regzbot:
#regzbot introduced: bc8a0fac8677
#regzbot title: ath11k: connection to 6 GHz AP fails
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-05-11 9:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 6:40 [PATCH v2] wifi: ath11k: move power type check to ASSOC stage when connecting to 6 GHz AP Baochen Qiang
2024-04-24 12:20 ` Kalle Valo
2024-04-24 19:21 ` Jeff Johnson
2024-05-11 9:54 ` Kalle Valo [this message]
2024-05-16 11:42 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-17 2:14 ` Baochen Qiang
2024-05-17 5:58 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-20 15:34 ` Kalle Valo
2024-05-21 1:52 ` Baochen Qiang
2024-05-21 5:12 ` Kalle Valo
2024-05-21 5:27 ` Baochen Qiang
2024-05-21 16:27 ` Jeff Johnson
2024-05-23 12:48 ` Kalle Valo
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=87wmo0k71i.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_bqiang@quicinc.com \
--cc=regressions@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.