linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Eliad Peller <eliad@wizery.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org
Subject: Re: [RFC 2/2] mac80211: config hw when going back on-channel
Date: Mon, 25 Jul 2011 10:18:28 -0700	[thread overview]
Message-ID: <4E2DA564.5070305@candelatech.com> (raw)
In-Reply-To: <1311607763-12603-3-git-send-email-eliad@wizery.com>

On 07/25/2011 08:29 AM, Eliad Peller wrote:
> The hw is currently not configured when going
> back on-channel.

I am less sure about this patch.  With the existing code,
I think it should catch going from on channel to off
and do the hw config properly.

With your change it will also reconfig the hardware, but it will
reconfig even if we were already on-channel (if, for instance,
local->tmp_channel is oper-channel), right?

Can you please explain in more detail how this code is
broken?

Thanks,
Ben

>
> Signed-off-by: Eliad Peller<eliad@wizery.com>
> ---
>   net/mac80211/work.c |    3 +--
>   1 files changed, 1 insertions(+), 2 deletions(-)
>
> diff --git a/net/mac80211/work.c b/net/mac80211/work.c
> index 3291958..e6abb15 100644
> --- a/net/mac80211/work.c
> +++ b/net/mac80211/work.c
> @@ -1075,7 +1075,6 @@ static void ieee80211_work_work(struct work_struct *work)
>   	}
>
>   	if (!remain_off_channel&&  local->tmp_channel) {
> -		bool on_oper_chan = ieee80211_cfg_on_oper_channel(local);
>   		local->tmp_channel = NULL;
>   		/* If tmp_channel wasn't operating channel, then
>   		 * we need to go back on-channel.
> @@ -1085,7 +1084,7 @@ static void ieee80211_work_work(struct work_struct *work)
>   		 * we still need to do a hardware config.  Currently,
>   		 * we cannot be here while scanning, however.
>   		 */
> -		if (ieee80211_cfg_on_oper_channel(local)&&  !on_oper_chan)
> +		if (!ieee80211_cfg_on_oper_channel(local))
>   			ieee80211_hw_config(local, 0);
>
>   		/* At the least, we need to disable offchannel_ps,


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


  reply	other threads:[~2011-07-25 17:18 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-25 15:29 [RFC 0/2] mac80211 offchannel fixes Eliad Peller
2011-07-25 15:29 ` [RFC 1/2] mac80211: fix remain_off_channel regression Eliad Peller
2011-07-25 17:13   ` Ben Greear
2011-08-09 12:13   ` Johannes Berg
2011-08-09 12:48     ` Eliad Peller
2011-08-09 12:55       ` Johannes Berg
2011-10-19 18:03   ` Ben Greear
2011-10-20 16:47     ` Eliad Peller
2011-07-25 15:29 ` [RFC 2/2] mac80211: config hw when going back on-channel Eliad Peller
2011-07-25 17:18   ` Ben Greear [this message]
2011-07-25 19:16     ` Eliad Peller
2011-07-25 19:56       ` Ben Greear
2011-07-25 20:07         ` Eliad Peller
2011-07-26  4:39           ` Ben Greear
2011-07-26  5:48             ` Eliad Peller
2011-08-09 12:14     ` Johannes Berg
2011-08-09 13:27       ` Ben Greear
2011-08-09 13:28         ` Johannes Berg
2011-08-09 13:33           ` Ben Greear

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=4E2DA564.5070305@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=eliad@wizery.com \
    --cc=johannes@sipsolutions.net \
    --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).