From: Karthikeyan Periyasamy <quic_periyasa@quicinc.com>
To: Johannes Berg <johannes@sipsolutions.net>, 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 20:51:46 +0530 [thread overview]
Message-ID: <a588beba-ddeb-445a-abff-cfb3f6a41a63@quicinc.com> (raw)
In-Reply-To: <36d111a1118349a86946bfdbc55e8fcbf3720fbc.camel@sipsolutions.net>
On 9/11/2024 7:10 PM, Johannes Berg wrote:
> On Wed, 2024-09-11 at 18:45 +0530, Karthikeyan Periyasamy wrote:
>>> I guess it depends on how you interpret "combined". It must be something
>>> that can actually be done *regardless* of radio assignment, to be
>>> compatible with older userspace.
>>>
>>> So if you think "combined" == "superset of all radios" then your
>>> understanding is incorrect. You need to think "combined" == "what the
>>> device can do without caring about radio assignment".
>>>
>> The current implementation of radio specific advertisement global iface
>> combination (NL80211_ATTR_WIPHY_INTERFACE_COMBINATIONS) expects the
>> superset of all radios, wherever the radio idx is -1 from caller of
>> cfg80211_iter_combinations().
>
> How so?
>
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().
--
Karthikeyan Periyasamy
--
கார்த்திகேயன் பெரியசாமி
next prev parent reply other threads:[~2024-09-11 15:21 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 [this message]
2024-09-11 15:25 ` Johannes Berg
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=a588beba-ddeb-445a-abff-cfb3f6a41a63@quicinc.com \
--to=quic_periyasa@quicinc.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
/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.