From: Johannes Berg <johannes@sipsolutions.net>
To: Karthikeyan Periyasamy <quic_periyasa@quicinc.com>,
Felix Fietkau <nbd@nbd.name>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v3] wifi: cfg80211: check radio iface combination for multi radio per wiphy
Date: Wed, 11 Sep 2024 17:25:21 +0200 [thread overview]
Message-ID: <7ddb082fc1a1886f343e4c0233a24221932edb64.camel@sipsolutions.net> (raw)
In-Reply-To: <a588beba-ddeb-445a-abff-cfb3f6a41a63@quicinc.com>
On Wed, 2024-09-11 at 20:51 +0530, Karthikeyan Periyasamy wrote:
>
> ieee80211_link_reserve_chanctx() calls
> ieee80211_can_create_new_chanctx() with radio_idx (-1) to calculate the
> max channel (ieee80211_max_num_channels) after the iface combination
> check (cfg80211_iter_combinations) passed for the global iface
> combination. Here the expectation is number of channel context is less
> than the number of different channel. So in multi-radio advertisement,
> each radio support atleast one channel, so totally multiple different
> channels advertised in the global iface combination to pass this
> ieee80211_max_num_channels().
So maybe that's broken then, I dunno. You should figure it out with
Felix I guess.
The intent was, and clearly it has to be, that the global combinations
are something that can be handled regardless of radio information, to be
backward compatible with existing uses. Therefore, it cannot be
something where you say two channels and radar detection on both because
that would imply being able to use channels 36 and 40 with 20 MHz at the
same time with radar detection, which isn't actually possible.
In this case, the "two channels" is only possible with also two radios,
which has to rely on the per-radio advertisement, and the global one has
to be just one channel for radar detection.
We still need the part of the patch that calls the validation on each
radio, but it shouldn't be different from the global one. If you could
make that patch I'd appreciate it.
johannes
next prev parent reply other threads:[~2024-09-11 15:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 11:29 [PATCH v3] wifi: cfg80211: check radio iface combination for multi radio per wiphy Karthikeyan Periyasamy
2024-09-11 9:42 ` Johannes Berg
2024-09-11 12:51 ` Karthikeyan Periyasamy
2024-09-11 12:52 ` Johannes Berg
2024-09-11 13:15 ` Karthikeyan Periyasamy
2024-09-11 13:40 ` Johannes Berg
2024-09-11 15:21 ` Karthikeyan Periyasamy
2024-09-11 15:25 ` Johannes Berg [this message]
2024-09-11 15:58 ` Felix Fietkau
2024-09-11 16:00 ` Johannes Berg
2024-09-11 15:59 ` Karthikeyan Periyasamy
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=7ddb082fc1a1886f343e4c0233a24221932edb64.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
--cc=quic_periyasa@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