Linux wireless drivers development
 help / color / mirror / Atom feed
From: Felix Fietkau <nbd@nbd.name>
To: Aditya Kumar Singh <quic_adisi@quicinc.com>,
	linux-wireless@vger.kernel.org
Cc: johannes@sipsolutions.net, quic_periyasa@quicinc.com,
	ath12k@lists.infradead.org
Subject: Re: [RFC v2 0/7] cfg80211/mac80211: support defining multiple radios per wiphy
Date: Thu, 6 Jun 2024 12:10:24 +0200	[thread overview]
Message-ID: <7744b5a1-446a-4e80-83a2-1c5b727906d2@nbd.name> (raw)
In-Reply-To: <f751d310-4cbb-4562-947b-a0a76edb6b40@quicinc.com>

On 06.06.24 12:00, Aditya Kumar Singh wrote:
> On 6/6/24 00:01, Felix Fietkau wrote:
>> The prerequisite for MLO support in cfg80211/mac80211 is that all the links
>> participating in MLO must be from the same wiphy/ieee80211_hw. To meet this
>> expectation, some drivers may need to group multiple discrete hardware each
>> acting as a link in MLO under single wiphy.
>> 
>> With this series, the bands and supported frequencies of each individual
>> radio are reported to user space. This allows user space to figure out the
>> limitations of what combination of channels can be used concurrently.
>> 
>> Each mac80211 channel context is assigned to a radio based on radio specific
>> frequency ranges and interface combinations.
>> 
>> This is loosely based on Karthikeyan Periyasamy's series
>> "[PATCH 00/13] wifi: Add multi physical hardware iface combination support"
>> with some differences:
>> 
>>   - a struct wiphy_radio is defined, which holds the frequency ranges and
>>     a full struct ieee80211_iface_combination array
>>   - a channel context is explicitly assigned to a radio when created
>>   - both global and per-radio interface combination limits are checked
>>     and enforced on channel context assignment
>> 
>> Changes since RFC:
>>   - replace static per-radio number of channels limit with full ifcomb
>>     checks
>>   - remove band bitmask in favor of only using freq ranges
> 
> What about handling 2 GHz + 5 GHz issue we discussed in v1 related to
> radar detection width and num chan ctx? Is that taken care?

Seems that I missed that one. I will take care of it in the next version.

Thanks,

- Felix


      reply	other threads:[~2024-06-06 10:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-05 18:31 [RFC v2 0/7] cfg80211/mac80211: support defining multiple radios per wiphy Felix Fietkau
2024-06-05 18:31 ` [RFC v2 1/7] wifi: nl80211: split helper function from nl80211_put_iface_combinations Felix Fietkau
2024-06-05 18:31 ` [RFC v2 2/7] wifi: cfg80211: add support for advertising multiple radios belonging to a wiphy Felix Fietkau
2024-06-05 18:31 ` [RFC v2 3/7] wifi: cfg80211: extend interface combination check for multi-radio Felix Fietkau
2024-06-06  7:20   ` Karthikeyan Periyasamy
2024-06-06  7:55     ` Felix Fietkau
2024-06-06  8:56       ` Karthikeyan Periyasamy
2024-06-06  8:58         ` Felix Fietkau
2024-06-06  9:52           ` Karthikeyan Periyasamy
2024-06-06  9:57             ` Felix Fietkau
2024-06-05 18:31 ` [RFC v2 4/7] wifi: mac80211: add radio index to ieee80211_chanctx_conf Felix Fietkau
2024-06-05 18:31 ` [RFC v2 5/7] wifi: mac80211: extend ifcomb check functions for multi-radio Felix Fietkau
2024-06-05 18:31 ` [RFC v2 6/7] wifi: mac80211: move code in ieee80211_link_reserve_chanctx to a helper Felix Fietkau
2024-06-05 18:31 ` [RFC v2 7/7] wifi: mac80211: add wiphy radio assignment and validation Felix Fietkau
2024-06-06 10:00 ` [RFC v2 0/7] cfg80211/mac80211: support defining multiple radios per wiphy Aditya Kumar Singh
2024-06-06 10:10   ` Felix Fietkau [this message]

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=7744b5a1-446a-4e80-83a2-1c5b727906d2@nbd.name \
    --to=nbd@nbd.name \
    --cc=ath12k@lists.infradead.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=quic_adisi@quicinc.com \
    --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