From: Lennert Buytenhek <buytenh@wantstofly.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 09/29] mwl8k: remove usage of deprecated radio_enabled
Date: Tue, 18 Aug 2009 10:25:37 +0200 [thread overview]
Message-ID: <20090818082537.GK18639@mail.wantstofly.org> (raw)
In-Reply-To: <1250580509.30538.2.camel@johannes.local>
On Tue, Aug 18, 2009 at 09:28:29AM +0200, Johannes Berg wrote:
> > Signed-off-by: Lennert Buytenhek <buytenh@marvell.com>
> > ---
> > drivers/net/wireless/mwl8k.c | 2 +-
> > 1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > diff --git a/drivers/net/wireless/mwl8k.c b/drivers/net/wireless/mwl8k.c
> > index 9f54204..3a201a2 100644
> > --- a/drivers/net/wireless/mwl8k.c
> > +++ b/drivers/net/wireless/mwl8k.c
> > @@ -2935,7 +2935,7 @@ static int mwl8k_config_wt(struct work_struct *wt)
> > struct mwl8k_priv *priv = hw->priv;
> > int rc = 0;
> >
> > - if (!conf->radio_enabled) {
> > + if (conf->flags & IEEE80211_CONF_IDLE) {
> > mwl8k_cmd_802_11_radio_disable(hw);
> > priv->current_channel = NULL;
> > rc = 0;
>
> So I think the return; a little below needs to be removed to allow doing
> other things while the radio is off? I'm not sure which actually happen
> but I never audited the code to make sure nothing happens.
The logic is just:
if (idle) {
issue "radio disable" command
} else {
issue "radio enable" command
set channel
set tx power
set antenna config
}
So if a channel change hapens while we are idle, that event won't get
lost -- it'll just happen later.
next prev parent reply other threads:[~2009-08-18 8:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-18 3:52 [PATCH 09/29] mwl8k: remove usage of deprecated radio_enabled Lennert Buytenhek
2009-08-18 7:27 ` Johannes Berg
2009-08-18 8:24 ` Lennert Buytenhek
2009-08-18 7:28 ` Johannes Berg
2009-08-18 8:25 ` Lennert Buytenhek [this message]
2009-08-18 8:26 ` Johannes Berg
2009-08-18 9:52 ` Lennert Buytenhek
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=20090818082537.GK18639@mail.wantstofly.org \
--to=buytenh@wantstofly.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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