From: Mahesh Palivela <maheshp@posedge.com>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Kalle Valo <kvalo@adurom.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linville@tuxdriver.com" <linville@tuxdriver.com>
Subject: Re: [PATCH] cfg80211: VHT (11ac) Regulatory change
Date: Fri, 24 Aug 2012 17:03:05 +0530 [thread overview]
Message-ID: <50376671.7080007@posedge.com> (raw)
In-Reply-To: <20120822101252.GA6082@redhat.com>
>
> I see, we could add helper function that will calculate
> center_freq/bandwidth, but starting from defining new channel
> structure and accompanying code in nl80211/mac80211 is more
> reasonable.
>
> Stanislaw
>
How about below new channel config structure? wanted to fit 80+80 config
as well.
/**
* enum ieee80211_chan_width - channel bandwidths
*
* @IEEE80211_CHAN_WIDTH_20MHZ: 20 MHz chan bandwidth
* @IEEE80211_CHAN_WIDTH_40MHZ: 40 MHz chan bandwidth
* @IEEE80211_CHAN_WIDTH_80MHZ: 80 MHz chan bandwidth
* @IEEE80211_CHAN_WIDTH_160MHZ: 160 MHz chan bandwidth
*/
enum ieee80211_chan_width {
IEEE80211_CHAN_WIDTH_20MHZ = 20,
IEEE80211_CHAN_WIDTH_40MHZ = 40,
IEEE80211_CHAN_WIDTH_80MHZ = 80,
IEEE80211_CHAN_WIDTH_160MHZ = 160
};
/**
* struct ieee80211_channel_config - channel config definition
*
* This structure describes channel configuration
*
* @chan_width1: channel bandwidth 1
* @center_freq1: center frequency 1 for entire chan width
* @control_offset1: control chan offset 1
* @chan_width2: channel bandwidth 2
* @center_freq2: center frequency 2 for entire chan width
* @control_offset2: control chan offset 2
*/
struct ieee80211_channel_config {
enum ieee80211_chan_width chan_width1;
u16 center_freq1;
u16 control_offset1;
enum ieee80211_chan_width chan_width2;
u16 center_freq2;
u16 control_offset2;
};
next prev parent reply other threads:[~2012-08-24 11:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 15:55 [PATCH] cfg80211: VHT (11ac) Regulatory change Mahesh Palivela
2012-08-16 10:22 ` Stanislaw Gruszka
2012-08-16 13:17 ` Mahesh Palivela
2012-08-17 14:06 ` Stanislaw Gruszka
2012-08-17 17:56 ` Mahesh Palivela
2012-08-20 16:38 ` Johannes Berg
2012-08-21 7:50 ` Kalle Valo
2012-08-21 8:18 ` Stanislaw Gruszka
2012-08-21 13:35 ` Mahesh Palivela
2012-08-21 15:53 ` Johannes Berg
2012-08-21 18:07 ` Mahesh Palivela
2012-08-22 7:03 ` Johannes Berg
2012-08-22 9:01 ` Stanislaw Gruszka
2012-08-22 9:04 ` Johannes Berg
2012-08-22 10:12 ` Stanislaw Gruszka
2012-08-24 11:33 ` Mahesh Palivela [this message]
2012-08-24 12:05 ` Johannes Berg
2012-08-24 13:08 ` Mahesh Palivela
2012-08-26 8:39 ` Johannes Berg
2012-08-27 4:15 ` Mahesh Palivela
2012-08-27 12:05 ` Mahesh Palivela
2012-08-28 12:20 ` Mahesh Palivela
2012-08-29 4:07 ` Mahesh Palivela
2012-09-04 8:17 ` Johannes Berg
-- strict thread matches above, loose matches on Subject: below --
2012-08-14 7:32 Mahesh Palivela
2012-08-14 12:05 ` Stanislaw Gruszka
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=50376671.7080007@posedge.com \
--to=maheshp@posedge.com \
--cc=johannes@sipsolutions.net \
--cc=kvalo@adurom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=sgruszka@redhat.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).