linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vasanthakumar Thiagarajan <vthiagar@qca.qualcomm.com>
To: "Pedersen, Thomas" <c_tpeder@qca.qualcomm.com>
Cc: <kvalo@qca.qualcomm.com>, <linux-wireless@vger.kernel.org>,
	<ath6kl-devel@qualcomm.com>
Subject: Re: [PATCH 2/2] ath6kl: Configure htcap in fw based on the channel type in AP mode
Date: Sat, 7 Apr 2012 18:25:13 +0530	[thread overview]
Message-ID: <20120407125511.GA19815@vasanth-laptop> (raw)
In-Reply-To: <20120406174157.GA10355@pista>

> >  
> > +static int ath6kl_set_channel(struct wiphy *wiphy, struct net_device *dev,
> > +			      struct ieee80211_channel *chan,
> > +			      enum nl80211_channel_type channel_type)
> > +{
> > +	struct ath6kl_vif *vif;
> > +
> > +	/*
> > +	 * 'dev' could be NULL if a channel change is required for the hardware
> > +	 * device itself, instead of a particular VIF.
> > +	 *
> > +	 * FIXME: To be handled properly when monitor mode is supported.
> > +	 */
> > +	if (!dev)
> > +		return -EBUSY;
> > +
> > +	vif = netdev_priv(dev);
> > +
> > +	if (!ath6kl_cfg80211_ready(vif))
> > +		return -EIO;
> > +
> > +	ath6kl_dbg(ATH6KL_DBG_WLAN_CFG, "%s: center_freq=%u hw_value=%u\n",
> > +		   __func__, chan->center_freq, chan->hw_value);
> > +	vif->next_chan = chan->center_freq;
> > +	vif->next_ch_type = channel_type;
> > +	vif->next_ch_band = chan->band;
> 
> Why this indirection? Can't we just call ath6kl_set_htcap() here and
> thereby handle the STA case as well?

Station mode does not use set_channel for normal operation in ath6kl. Only when
a channel is set from user space (like iw) this will be called and as such it has
no use for station mode as of now. connect() is the right place to override fw ht
configuration in station mode.

Vasanth

      reply	other threads:[~2012-04-07 12:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-06 14:07 [PATCH 1/2] ath6kl: Don't advertise HT40 support in 2.4 Ghz Vasanthakumar Thiagarajan
2012-04-06 14:07 ` [PATCH 2/2] ath6kl: Configure htcap in fw based on the channel type in AP mode Vasanthakumar Thiagarajan
2012-04-06 14:54   ` Joe Perches
2012-04-06 15:10     ` Vasanthakumar Thiagarajan
2012-04-06 17:41   ` Pedersen, Thomas
2012-04-07 12:55     ` Vasanthakumar Thiagarajan [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=20120407125511.GA19815@vasanth-laptop \
    --to=vthiagar@qca.qualcomm.com \
    --cc=ath6kl-devel@qualcomm.com \
    --cc=c_tpeder@qca.qualcomm.com \
    --cc=kvalo@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    /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).