From: Johannes Berg <johannes@sipsolutions.net>
To: Victor Goldenshtein <victorg@ti.com>
Cc: linux-wireless@vger.kernel.org, kgiori@qca.qualcomm.com,
mcgrof@frijolero.org, zefir.kurtisi@neratec.com,
adrian.chadd@gmail.com, j@w1.fi, coelho@ti.com, assaf@ti.com,
yoni.divinsky@ti.com, igalc@ti.com, adrian@freebsd.org,
nbd@nbd.name, simon.wunderlich@s2003.tu-chemnitz.de
Subject: Re: [PATCH v3 6/7] mac80211: add ap channel switch command/event
Date: Mon, 10 Sep 2012 13:25:37 +0200 [thread overview]
Message-ID: <1347276337.4272.19.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1344426823-1795-7-git-send-email-victorg@ti.com>
> +static int
> +ieee80211_ap_process_chanswitch(struct wiphy *wiphy,
> + struct net_device *dev,
> + struct ieee80211_ap_ch_switch *ap_ch_switch)
> +{
> + struct ieee80211_sub_if_data *sdata = IEEE80211_DEV_TO_SUB_IF(dev);
> + struct ieee80211_local *local = sdata->local;
> +
> + if (!local->ops->channel_switch)
> + return -EOPNOTSUPP;
> +
> + if (!ap_ch_switch || !ap_ch_switch->channel)
> + return -EINVAL;
> +
> + drv_ap_channel_switch(local, ap_ch_switch);
> + return 0;
errors are not possible?
> +void ieee80211_ap_ch_switch_done(struct ieee80211_vif *vif,
> + struct ieee80211_channel *new_channel,
> + enum nl80211_channel_type type)
> +{
> + struct ieee80211_sub_if_data *sdata = vif_to_sdata(vif);
> + struct ieee80211_local *local = sdata->local;
> +
> + if (WARN_ON(sdata->vif.type != NL80211_IFTYPE_AP))
> + return;
> +
> + /* update the device channel directly */
> + mutex_lock(&local->mtx);
> + local->oper_channel = local->hw.conf.channel = new_channel;
> + local->_oper_channel_type = type;
> + mutex_unlock(&local->mtx);
> +
> + cfg80211_ch_switch_notify(sdata->dev, new_channel->center_freq, type);
> + trace_api_ap_ch_switch_done(sdata, new_channel->center_freq);
tracing last seems very strange
johannes
next prev parent reply other threads:[~2012-09-10 11:25 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 11:53 [PATCH v3 0/7] nl/cfg/mac80211: add DFS master ability Victor Goldenshtein
2012-08-08 11:53 ` [PATCH v3 1/7] nl80211/cfg80211: add radar detection command/event Victor Goldenshtein
2012-08-09 11:51 ` Stanislaw Gruszka
2012-08-09 12:08 ` Goldenshtein, Victor
2012-08-10 16:25 ` Stanislaw Gruszka
2012-08-12 7:31 ` Goldenshtein, Victor
2012-08-20 10:33 ` Johannes Berg
2012-09-10 10:53 ` Johannes Berg
2012-10-03 13:53 ` Goldenshtein, Victor
2012-10-09 18:46 ` Johannes Berg
2012-10-14 13:29 ` Victor Goldenshtein
2012-08-08 11:53 ` [PATCH v3 2/7] mac80211: " Victor Goldenshtein
2012-08-10 16:28 ` Stanislaw Gruszka
2012-08-12 7:31 ` Goldenshtein, Victor
2012-08-13 7:36 ` Stanislaw Gruszka
2012-08-20 7:21 ` Goldenshtein, Victor
2012-09-10 10:54 ` Johannes Berg
2012-09-10 11:17 ` Johannes Berg
2012-10-03 13:53 ` Goldenshtein, Victor
2012-08-08 11:53 ` [PATCH v3 3/7] nl80211/cfg80211: add ability to enable TX on op-channel Victor Goldenshtein
2012-08-08 11:53 ` [PATCH v3 4/7] mac80211: " Victor Goldenshtein
2012-09-10 11:20 ` Johannes Berg
2012-10-03 13:53 ` Goldenshtein, Victor
2012-08-08 11:53 ` [PATCH v3 5/7] nl80211/cfg80211: add ap channel switch command Victor Goldenshtein
2012-09-10 11:23 ` Johannes Berg
2012-10-03 13:53 ` Goldenshtein, Victor
2012-10-09 18:44 ` Johannes Berg
2012-10-14 13:29 ` Victor Goldenshtein
2012-08-08 11:53 ` [PATCH v3 6/7] mac80211: add ap channel switch command/event Victor Goldenshtein
2012-08-10 16:36 ` Stanislaw Gruszka
2012-08-12 7:31 ` Goldenshtein, Victor
2012-08-13 7:34 ` Stanislaw Gruszka
2012-08-20 10:32 ` Johannes Berg
2012-09-10 11:25 ` Johannes Berg [this message]
2012-10-03 13:54 ` Goldenshtein, Victor
2012-10-04 15:42 ` Goldenshtein, Victor
2012-08-08 11:53 ` [PATCH v3 7/7] mac80211: add DFS support to monitor interface Victor Goldenshtein
2012-09-10 11:26 ` Johannes Berg
2012-10-03 13:54 ` Goldenshtein, Victor
2012-10-09 18:42 ` Johannes Berg
2012-10-14 13:29 ` Victor Goldenshtein
2012-09-07 15:47 ` [PATCH v3 0/7] nl/cfg/mac80211: add DFS master ability Simon Wunderlich
2012-09-07 16:04 ` Johannes Berg
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=1347276337.4272.19.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=adrian.chadd@gmail.com \
--cc=adrian@freebsd.org \
--cc=assaf@ti.com \
--cc=coelho@ti.com \
--cc=igalc@ti.com \
--cc=j@w1.fi \
--cc=kgiori@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@frijolero.org \
--cc=nbd@nbd.name \
--cc=simon.wunderlich@s2003.tu-chemnitz.de \
--cc=victorg@ti.com \
--cc=yoni.divinsky@ti.com \
--cc=zefir.kurtisi@neratec.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).