linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mahesh Palivela <maheshp@posedge.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "linville@tuxdriver.com" <linville@tuxdriver.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] cfg80211: 80MHz (11ac) regulatory change
Date: Wed, 25 Jul 2012 09:31:24 +0530	[thread overview]
Message-ID: <500F6F94.3070400@posedge.com> (raw)
In-Reply-To: <1343128638.4415.17.camel@jlt3.sipsolutions.net>

On 07/24/2012 04:47 PM, Johannes Berg wrote:
> On Tue, 2012-07-24 at 16:18 +0530, Mahesh Palivela wrote:
>
>>>> indicating the number of channels below/above control (for control
>>>> channel 1,2,3,4 respectively). Similarly, for VHT160 you'd have 8
>>>> possibilities:
>>>>
>>>> |-1-|-2-|-3-|-4-|-5-|-6-|-7-|-8-|
>>>>
>>>> (which one could again capture as VHT_CHAN_LAYOUT_0_7 etc.)
>>>>
>>>> [MP] I see your point. But according to 11ac spec, AP will use primary
>>>> chan as specified in HT operation IE chan num. Secondary channel is
>>>> center freq specified in VHT Operation IE. So I am thinking secondary
>>>> channel is not relative offset to primary channel. Hope I am not
>>>> mistaken here.
>>>
>>> Ok so HT has primary channel and secondary, and VHT has secondary VHT
>>> which can again be above/below? That would make sense, but you wouldn't
>>> be covering it.
>>>
>>
>> I am thinking no need of above/below convention as the center frequency
>> value itself we know.
>
> But we don't use the center frequency of the overall Ht40/80/160
> channel, we always use the center frequency of the control channel.
>

11ac Draft3.0 section 22.3.14 says VHT channel is specified by
dot11CurrentChannelBandwidth, dot11CurrentChannelCenterFrequencyIndex0,
dot11CurrentChannelCenterFrequencyIndex1 and dot11CurrentPrimaryChannel

primary channel comes from HT Op IE.
chanBW, chanCenterFreq0, chanCenterFreq1 comes from VHT Op IE.
So multiple secondary channels doesn't seem to be a valid?

>>>>> +     /* This would happen when regulatory rules disallow VHT80 completely */
>>>>> +     if (IEEE80211_CHAN_NO_VHT80 == (chan->flags & (IEEE80211_CHAN_NO_VHT80)))
>>>>> +             return true;
>>>>
>>>> Is that really right? Need to document what the return value of this
>>>> function should be, I guess?
>>>>
>>>> [MP] I guess, it's possible for a channel not allowed for 80Mhz operation.
>>>
>>> Yeah but should it really check *all* the bits rather than any one of
>>> them?
>>>
>>
>> You mean to say other bits like HT40MINUS, HT40PLUS or even DFS?
>
> No, I mean all the bits that are part of CHAN_NO_VHT80.
>


CHAN_NO_VHT80 is actually 2 bits. NO_VHT80MINUS & NO_VHT80PLUS.
Is that ok?

+	IEEE80211_CHAN_NO_VHT80PLUS	= 1<<6,
+	IEEE80211_CHAN_NO_VHT80MINUS	= 1<<7,

+#define IEEE80211_CHAN_NO_VHT80 \
+	(IEEE80211_CHAN_NO_VHT80PLUS | IEEE80211_CHAN_NO_VHT80MINUS)

> johannes
>

Thanks,
Mahesh

  reply	other threads:[~2012-07-25  4:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-23  9:17 [PATCH] cfg80211: 80MHz (11ac) regulatory change Mahesh Palivela
2012-07-23 13:06 ` Johannes Berg
2012-07-24  6:46   ` Mahesh Palivela
2012-07-24  8:56     ` Johannes Berg
2012-07-24 10:48       ` Mahesh Palivela
2012-07-24 11:17         ` Johannes Berg
2012-07-25  4:01           ` Mahesh Palivela [this message]
2012-07-25  9:50             ` Johannes Berg
2012-07-26  6:30               ` Mahesh Palivela
2012-07-26 17:42                 ` Johannes Berg
2012-07-30  8:31                   ` Mahesh Palivela
2012-07-24  7:12 ` Kalle Valo

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=500F6F94.3070400@posedge.com \
    --to=maheshp@posedge.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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;
as well as URLs for NNTP newsgroup(s).