From: Seth Forshee <seth.forshee@canonical.com>
To: Arend van Spriel <arend@broadcom.com>
Cc: linux-wireless@vger.kernel.org,
"Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>
Subject: Re: [RFC PATCH 5/8] brcm80211: smac: enable/disable radio on regulatory updates
Date: Sat, 26 May 2012 12:18:17 -0500 [thread overview]
Message-ID: <20120526171817.GD11759@ubuntu-mba> (raw)
In-Reply-To: <4FC008BB.1020606@broadcom.com>
On Sat, May 26, 2012 at 12:33:31AM +0200, Arend van Spriel wrote:
> > @@ -1240,12 +1199,37 @@ static int brcms_reg_notifier(struct wiphy *wiphy,
> > struct ieee80211_hw *hw = wiphy_to_ieee80211_hw(wiphy);
> > struct brcms_info *wl = hw->priv;
> > struct brcms_c_info *wlc = wl->wlc;
> > + struct ieee80211_supported_band *sband;
> > + struct ieee80211_channel *ch;
> > + int band, i, n_channels = 0;
> >
> > brcms_reg_apply_radar_flags(wiphy);
> >
> > if (request && request->initiator == NL80211_REGDOM_SET_BY_COUNTRY_IE)
> > brcms_reg_apply_beaconing_flags(wiphy, request->initiator);
> >
> > + /* Disable radio if all channels disallowed by regulatory */
>
> I think we need to validate the channels against our phy as well. See
> brcms_c_channels_init().
I disable channels not supported by the phy in brcms_c_regd_init(), so
it's not necessary to check it again here.
> > + for (band = 0; band < IEEE80211_NUM_BANDS; band++) {
> > + sband = wiphy->bands[band];
> > + if (!sband)
> > + continue;
> > +
> > + for (i = 0; i < sband->n_channels; i++) {
> > + ch = &sband->channels[i];
> > +
> > + if (!(ch->flags & IEEE80211_CHAN_DISABLED))
> > + n_channels++;
>
> could break here when a valid channel is found.
Ack, I'll do that.
next prev parent reply other threads:[~2012-05-26 17:18 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 20:17 [RFC PATCH 0/8] brcm80211: smac: rework regulatory support Seth Forshee
2012-04-16 20:17 ` [RFC PATCH 1/8] brcm80211: smac: don't set up tx power limits during initialization Seth Forshee
2012-05-25 22:32 ` Arend van Spriel
2012-04-16 20:17 ` [RFC PATCH 2/8] brcm80211: smac: always set channel specified by mac80211 Seth Forshee
2012-05-25 22:32 ` Arend van Spriel
2012-04-16 20:17 ` [RFC PATCH 3/8] brcm80211: smac: clean up channel.c Seth Forshee
2012-05-25 22:33 ` Arend van Spriel
2012-05-26 17:17 ` Seth Forshee
2012-05-27 11:51 ` Arend van Spriel
2012-05-27 11:53 ` Arend van Spriel
2012-05-29 12:46 ` Seth Forshee
2012-05-29 13:03 ` Arend van Spriel
2012-04-16 20:17 ` [RFC PATCH 4/8] brcm80211: smac: inform mac80211 of the X2 regulatory domain Seth Forshee
2012-05-25 22:33 ` Arend van Spriel
2012-05-26 17:18 ` Seth Forshee
2012-05-27 12:17 ` Arend van Spriel
2012-05-29 13:12 ` Seth Forshee
2012-05-29 16:44 ` Arend van Spriel
2012-05-31 14:46 ` Seth Forshee
2012-05-31 17:49 ` Arend van Spriel
2012-06-07 18:18 ` Luis R. Rodriguez
2012-04-16 20:17 ` [RFC PATCH 5/8] brcm80211: smac: enable/disable radio on regulatory updates Seth Forshee
2012-05-25 22:33 ` Arend van Spriel
2012-05-26 17:18 ` Seth Forshee [this message]
2012-05-27 12:18 ` Arend van Spriel
2012-04-16 20:17 ` [RFC PATCH 6/8] brcm80211: smac: use mac80211 channel data for tx power limits Seth Forshee
2012-05-25 22:33 ` Arend van Spriel
2012-04-16 20:17 ` [RFC PATCH 7/8] brcm80211: smac: don't validate channels against internal regulatory data Seth Forshee
2012-05-25 22:33 ` Arend van Spriel
2012-04-16 20:17 ` [RFC PATCH 8/8] brcm80211: smac: use current regulatory domain when checking whether OFDM is allowed Seth Forshee
2012-05-25 22:34 ` Arend van Spriel
2012-04-16 20:42 ` [RFC PATCH 0/8] brcm80211: smac: rework regulatory support Arend van Spriel
2012-04-16 20:53 ` Seth Forshee
2012-04-19 19:31 ` Arend van Spriel
2012-04-19 19:46 ` Seth Forshee
2012-04-30 17:12 ` Seth Forshee
2012-05-01 12:13 ` Arend van Spriel
2012-05-01 16:12 ` Seth Forshee
2012-05-25 22:31 ` Arend van Spriel
2012-05-25 22:51 ` Luis R. Rodriguez
2012-05-26 6:38 ` Arend van Spriel
2012-05-26 7:19 ` Luis R. Rodriguez
2012-05-26 17:17 ` Seth Forshee
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=20120526171817.GD11759@ubuntu-mba \
--to=seth.forshee@canonical.com \
--cc=arend@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rodrigue@qca.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