From: Luciano Coelho <coelho@ti.com>
To: Eliad Peller <eliad@wizery.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 4/7] wl12xx: prevent scheduling while suspending (WoW enabled)
Date: Thu, 12 May 2011 22:48:57 +0300 [thread overview]
Message-ID: <1305229737.12586.1027.camel@cumari> (raw)
In-Reply-To: <1305104068-32240-5-git-send-email-eliad@wizery.com>
On Wed, 2011-05-11 at 11:54 +0300, Eliad Peller wrote:
> When WoW is enabled, the interface will stay up and the chip will
> be powered on, so we have to flush/cancel any remaining work, and
> prevent the irq handler from scheduling a new work until the system
> is resumed.
>
> Add 2 new flags:
> * WL1271_FLAG_SUSPENDED - the system is (about to be) suspended.
> * WL1271_FLAG_PENDING_WORK - there is a pending irq work which
> should be scheduled when the system is being resumed.
>
> In order to wake-up the system while getting an irq, we initialize
> the device as wakeup device, and calling pm_wakeup_event() upon
> getting the interrupt (while the system is about to be suspended)
>
> Signed-off-by: Eliad Peller <eliad@wizery.com>
> ---
[...]
> 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?
> +
> + wl1271_enable_interrupts(wl);
> + flush_work(&wl->tx_work);
> + flush_delayed_work(&wl->pspoll_work);
> + flush_delayed_work(&wl->elp_work);
> + }
> return 0;
> }
>
> @@ -1346,6 +1368,30 @@ static int wl1271_op_resume(struct ieee80211_hw *hw)
> struct wl1271 *wl = hw->priv;
> wl1271_debug(DEBUG_MAC80211, "mac80211 resume wow=%d",
> wl->wow_enabled);
> +
> + /*
> + * re-enable irq_work enqueuing, and call irq_work directly if
> + * there is a pending work.
> + */
> + if (wl->wow_enabled) {
> + struct wl1271 *wl = hw->priv;
> + unsigned long flags;
> + bool run_irq_work = false;
> +
> + spin_lock_irqsave(&wl->wl_lock, flags);
> + clear_bit(WL1271_FLAG_SUSPENDED, &wl->flags);
> + if (test_and_clear_bit(WL1271_FLAG_PENDING_WORK, &wl->flags))
> + run_irq_work = true;
> + spin_unlock_irqrestore(&wl->wl_lock, flags);
You could use __clear_bit() and __test_and_clear_bit() here too, since
you're spinning.
> + if (run_irq_work) {
> + wl1271_debug(DEBUG_MAC80211,
> + "run postponed irq_work directly");
> + wl1271_irq(0, wl);
> + wl1271_enable_interrupts(wl);
Shouldn't this wl1271_enable_interrupts() be outside the if? Don't you
want to enable interrupts again when there was no pending work?
> diff --git a/drivers/net/wireless/wl12xx/sdio.c b/drivers/net/wireless/wl12xx/sdio.c
> index 5b03fd5..bf2a6ad 100644
> --- a/drivers/net/wireless/wl12xx/sdio.c
> +++ b/drivers/net/wireless/wl12xx/sdio.c
> @@ -72,6 +72,7 @@ static irqreturn_t wl1271_hardirq(int irq, void *cookie)
> {
> struct wl1271 *wl = cookie;
> unsigned long flags;
> + bool skip = false;
>
> wl1271_debug(DEBUG_IRQ, "IRQ");
>
> @@ -82,8 +83,20 @@ static irqreturn_t wl1271_hardirq(int irq, void *cookie)
> complete(wl->elp_compl);
> wl->elp_compl = NULL;
> }
> +
> + if (test_bit(WL1271_FLAG_SUSPENDED, &wl->flags)) {
> + /* don't enqueue a work right now. mark it as pending */
> + set_bit(WL1271_FLAG_PENDING_WORK, &wl->flags);
> + wl1271_debug(DEBUG_IRQ, "should not enqueue work");
> + disable_irq_nosync(wl->irq);
> + pm_wakeup_event(wl1271_sdio_wl_to_dev(wl), 0);
> + skip = true;
> + }
> spin_unlock_irqrestore(&wl->wl_lock, flags);
>
> + if (skip)
> + return IRQ_HANDLED;
> +
> return IRQ_WAKE_THREAD;
> }
Could be nicer to just skip the skip variable (unintended pun
intended ;). You can do it like this:
if (test_bit...) {
...
spin_unlock_irqrestore();
return IRQ_HANDLED;
}
spin_unlock_irqrestore();
return IRQ_WAKE_THREAD;
Looks a bit nicer to me, but I don't mind if you prefer not skipping the
skip. :)
--
Cheers,
Luca.
next prev parent reply other threads:[~2011-05-12 19:49 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 [this message]
2011-05-12 19:52 ` Johannes Berg
2011-05-12 20:09 ` Luciano Coelho
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=1305229737.12586.1027.camel@cumari \
--to=coelho@ti.com \
--cc=eliad@wizery.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).