From: Aditya Kumar Singh <quic_adisi@quicinc.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: <linux-wireless@vger.kernel.org>, <ath12k@lists.infradead.org>
Subject: Re: [PATCH] wifi: mac80211: fix assigning channel in activate links
Date: Tue, 1 Oct 2024 13:07:34 +0530 [thread overview]
Message-ID: <5fe9fdf2-ae5c-4d15-a095-0203a814e4ba@quicinc.com> (raw)
In-Reply-To: <c103db90ed53a75cae10baba0ae52dae85bf1c3f.camel@sipsolutions.net>
On 10/1/24 12:52, Johannes Berg wrote:
> But that doesn't explain the*comment*, which literally says:
>
> inform about the link info changed parameters after all stations are
> also added
>
> but you
> (a) don't add stations here
> (b) if you're thinking about link stations, the link stations are
> only added_after_ this comment and the link info change ...
>
Oops! my bad. Previously I was thinking like this -
First iterate and do only _ieee80211_link_use_channel() this part. Then
let the flow as usual and after stations are added, do the
link_info_changed() part.
>
>> Later, in the loop for_each_set_bit(link_id, &add,
>> IEEE80211_MLD_MAX_NUM_LINKS), channels are added. At this stage, the
>> driver will actually create the link on the interface at its own level.
>> Since here using the channel information, appropriate firmware can be
>> picked. For example 2 GHz or 5 GHz or 6 GHz firmware.
> Picking "firmware" sounds very odd here, I'd say you mean "which device
> to pick"?
:) Yeah.
>
>> hmm... yeah true that. May be I will move this once the old links are
>> removed?
>>
> I'd think at least that?
>
> But also this seems to break out driver for other reasons, because it
> initializes rate control somewhere here and needs a station for that.
> Didn't look deeply into that yet though.
Okay so doing as I said above could work -
if (add) {
...
}
for_each_set_bit(link_id, &rem, ..) {
...
}
for_each_set_bit(link_id, &add ...) {
_ieee80211_link_use_channel()
}
list_for_each_entry(sta, &local->sta_list, list) {
...
}
...
for_each_set_bit(link_id, &add ....) {
now call
ieee80211_mgd_set_link_qos_params()
ieee80211_link_info_change_notify()
}
...
At least I tried both of these ways in hwsim. I dont see any failures.
Hence I thought why not move whole for loop to top instead.
--
Aditya
next prev parent reply other threads:[~2024-10-01 7:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 4:15 [PATCH] wifi: mac80211: fix assigning channel in activate links Aditya Kumar Singh
2024-10-01 6:31 ` Johannes Berg
2024-10-01 7:17 ` Aditya Kumar Singh
2024-10-01 7:22 ` Johannes Berg
2024-10-01 7:37 ` Aditya Kumar Singh [this message]
2024-10-01 8:08 ` Johannes Berg
2024-10-01 8:26 ` Aditya Kumar Singh
2024-10-01 8:28 ` Johannes Berg
2024-10-01 9:16 ` Aditya Kumar Singh
2024-10-01 6:32 ` Johannes Berg
2024-10-01 7:20 ` Aditya Kumar Singh
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=5fe9fdf2-ae5c-4d15-a095-0203a814e4ba@quicinc.com \
--to=quic_adisi@quicinc.com \
--cc=ath12k@lists.infradead.org \
--cc=johannes@sipsolutions.net \
--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