From: Johannes Berg <johannes@sipsolutions.net>
To: Karthikeyan Periyasamy <quic_periyasa@quicinc.com>
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 14:52:43 +0200 [thread overview]
Message-ID: <dfd252e8c553c5501eb97042325d9009be14faed.camel@sipsolutions.net> (raw)
In-Reply-To: <b7769f15-b0ef-fb61-8622-fc8bdc7339cc@quicinc.com>
On Wed, 2024-09-11 at 18:21 +0530, Karthikeyan Periyasamy wrote:
>
> On 9/11/2024 3:12 PM, Johannes Berg wrote:
> > On Wed, 2024-09-04 at 16:59 +0530, Karthikeyan Periyasamy wrote:
> > > Currently, wiphy_verify_combinations() fails for the multi-radio per wiphy
> > > due to the condition check on global interface combination that DFS only
> > > works on one channel.
> >
> > As it should, really.
> >
> > > In a multi-radio scenario, global interface
> > > combination encompasses the capabilities of all radio combinations, so it
> > > supports more than one channel with DFS.
> >
> > No, that's not correct, it doesn't.
>
> But the attribute comment section clearly says the Global iface
> combination encompass all radio combination as below
>
> * @NL80211_ATTR_WIPHY_INTERFACE_COMBINATIONS: Nested attribute listing *
> the
> * supported interface combinations for all radios combined. In each
> * nested item, it contains attributes defined in
> * &enum nl80211_if_combination_attrs.
>
> Is my understanding incorrect ?
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".
johannes
next prev parent reply other threads:[~2024-09-11 12:52 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 [this message]
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
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=dfd252e8c553c5501eb97042325d9009be14faed.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--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