From: Luciano Coelho <coelho@ti.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Eliad Peller <eliad@wizery.com>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 4/7] wl12xx: prevent scheduling while suspending (WoW enabled)
Date: Thu, 12 May 2011 23:09:15 +0300 [thread overview]
Message-ID: <1305230955.12586.1037.camel@cumari> (raw)
In-Reply-To: <1305229949.3461.41.camel@jlt3.sipsolutions.net>
On Thu, 2011-05-12 at 21:52 +0200, Johannes Berg wrote:
> On Thu, 2011-05-12 at 22:48 +0300, Luciano Coelho wrote:
>
> > > diff --git a/drivers/net/wireless/wl12xx/main.c b/drivers/net/wireless/wl12xx/main.c
> > > index 9ca71ce..308855a 100644
> > > --- a/drivers/net/wireless/wl12xx/main.c
> > > +++ b/drivers/net/wireless/wl12xx/main.c
> > > @@ -1338,6 +1338,28 @@ static int wl1271_op_suspend(struct ieee80211_hw *hw,
> > > struct wl1271 *wl = hw->priv;
> > > wl1271_debug(DEBUG_MAC80211, "mac80211 suspend wow=%d", !!wow);
> > > wl->wow_enabled = !!wow;
> > > + if (wl->wow_enabled) {
> > > + /* flush any remaining work */
> > > + wl1271_debug(DEBUG_MAC80211, "flushing remaining works");
> > > + flush_delayed_work(&wl->scan_complete_work);
> > > +
> > > + /*
> > > + * disable and re-enable interrupts in order to flush
> > > + * the threaded_irq
> > > + */
> > > + wl1271_disable_interrupts(wl);
> > > +
> > > + /*
> > > + * set suspended flag to avoid triggering a new threaded_irq
> > > + * work. no need for spinlock as interrupts are disabled.
> > > + */
> > > + set_bit(WL1271_FLAG_SUSPENDED, &wl->flags);
> >
> > The set_bit() function is atomic, so you wouldn't need the spinlock here
> > anyway. Couldn't you use __set_bit() instead, to avoid the expense of
> > using an atomic function when it's not necessary?
>
> That's only possible if the spinlock is held for all modifications of
> the variable. If there are any modifications that don't hold it, then
> you need the atomic version.
Ah, you're right. wl->flags is being modified in other places too (ie.
other bits are being set/cleared in other parts of the code), so there
could be some conflicts. I had just considered the flag as an
independent boolean, which it obviously isn't.
My next comment about changing to __set_bit() can also be disregarded.
--
Cheers,
Luca.
next prev parent reply other threads:[~2011-05-12 20:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 8:54 [PATCH 0/7] wl12xx: add initial wowlan support Eliad Peller
2011-05-11 8:54 ` [PATCH 1/7] wl12xx_sdio: set interrupt as wake_up interrupt Eliad Peller
2011-05-11 8:54 ` [PATCH 2/7] wl12xx: declare suspend/resume callbacks (for wowlan) Eliad Peller
2011-05-11 8:54 ` [PATCH 3/7] wl12xx_sdio: set MMC_PM_KEEP_POWER flag on suspend Eliad Peller
2011-05-11 8:54 ` [PATCH 4/7] wl12xx: prevent scheduling while suspending (WoW enabled) Eliad Peller
2011-05-12 19:48 ` Luciano Coelho
2011-05-12 19:52 ` Johannes Berg
2011-05-12 20:09 ` Luciano Coelho [this message]
2011-05-13 7:41 ` Eliad Peller
2011-05-11 8:54 ` [PATCH 5/7] wl12xx_sdio: declare support for NL80211_WOW_TRIGGER_ANYTHING trigger Eliad Peller
2011-05-11 8:54 ` [PATCH 6/7] wl12xx: add ps completion event Eliad Peller
2011-05-12 20:10 ` Luciano Coelho
2011-05-13 7:42 ` Eliad Peller
2011-05-11 8:54 ` [PATCH 7/7] wl12xx: enter/exit psm on wowlan suspend/resume Eliad Peller
2011-05-12 20:24 ` Luciano Coelho
2011-05-13 7:44 ` Eliad Peller
2011-05-11 8:57 ` [PATCH 0/7] wl12xx: add initial wowlan support Luciano Coelho
2011-05-11 16:52 ` Ohad Ben-Cohen
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=1305230955.12586.1037.camel@cumari \
--to=coelho@ti.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