From: Raj Kumar Bhagat <quic_rajkbhag@quicinc.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: <linux-wireless@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Vasanthakumar Thiagarajan
<vasanthakumar.thiagarajan@oss.qualcomm.com>
Subject: Re: [PATCH wireless-next 1/3] wifi: cfg80211: Add utility API to get radio index from channel
Date: Thu, 22 May 2025 14:50:40 +0530 [thread overview]
Message-ID: <d2fa7aba-b038-4d5b-877e-30362336016b@quicinc.com> (raw)
In-Reply-To: <37f00d636e1ffb68e383e0784b30e7e5cf48b4dd.camel@sipsolutions.net>
On 5/16/2025 1:21 PM, Johannes Berg wrote:
> On Wed, 2025-05-14 at 16:58 +0530, Raj Kumar Bhagat wrote:
>>
>> +int cfg80211_get_radio_idx_by_chan(struct wiphy *wiphy,
>> + const struct ieee80211_channel *chan)
>> +{
>> + const struct wiphy_radio *radio;
>> + int i, j;
>> + u32 freq;
>> +
>> + if (!chan)
>> + return -EINVAL;
>> +
>> + freq = ieee80211_channel_to_khz(chan);
>> + for (i = 0; i < wiphy->n_radio; i++) {
>> + radio = &wiphy->radio[i];
>> + for (j = 0; j < radio->n_freq_range; j++) {
>> + if (freq >= radio->freq_range[j].start_freq &&
>> + freq <= radio->freq_range[j].end_freq)
>> + return i;
>>
>
> I believe we also discussed this in the past elsewhere, but I don't
> think the the >= and <= can simultaneously be wrong. If the frequency
> ranges for radios are adjacent, then the intervals here need to be half
> open. I _think_ it should be < instead of <=, and therefore a half-open
> interval of "[start, end[" (or "[start, end)" depending on your
> preferred notation.)
>
Sure, will use half-open interval ([start, end[) in next version.
next prev parent reply other threads:[~2025-05-22 9:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 11:28 [PATCH wireless-next 0/3] wifi: cfg80211/mac80211: Handle simultaneous scan and DFS operations on different radios Raj Kumar Bhagat
2025-05-14 11:28 ` [PATCH wireless-next 1/3] wifi: cfg80211: Add utility API to get radio index from channel Raj Kumar Bhagat
2025-05-16 7:51 ` Johannes Berg
2025-05-16 7:52 ` Johannes Berg
2025-05-22 9:20 ` Raj Kumar Bhagat [this message]
2025-05-14 11:28 ` [PATCH wireless-next 2/3] wifi: mac80211: Allow scan on a radio while operating on DFS on another radio Raj Kumar Bhagat
2025-05-16 8:01 ` Johannes Berg
2025-05-22 10:40 ` Raj Kumar Bhagat
2025-05-22 11:23 ` Johannes Berg
2025-05-27 6:49 ` Raj Kumar Bhagat
2025-05-14 11:28 ` [PATCH wireless-next 3/3] wifi: mac80211: Allow DFS/CSA on a radio if scan is ongoing " Raj Kumar Bhagat
2025-05-16 8:05 ` Johannes Berg
2025-05-22 9:21 ` Raj Kumar Bhagat
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=d2fa7aba-b038-4d5b-877e-30362336016b@quicinc.com \
--to=quic_rajkbhag@quicinc.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=vasanthakumar.thiagarajan@oss.qualcomm.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
all inboxes | Powered by JetHome®