From: Luciano Coelho <coelho@ti.com>
To: Eliad Peller <eliad@wizery.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] wl12xx: avoid premature elp entrance
Date: Wed, 20 Apr 2011 20:44:13 +0300 [thread overview]
Message-ID: <1303321453.1988.737.camel@cumari> (raw)
In-Reply-To: <1301785319-18777-1-git-send-email-eliad@wizery.com>
On Sun, 2011-04-03 at 02:01 +0300, Eliad Peller wrote:
> The elp_work is being enqueued on wl1271_ps_elp_sleep, but doesn't get
> cancelled on wl1271_ps_elp_wakeup. This might cause immediate entrance
> to elp when the wl->mutex is being released, rather than using the delayed
> enqueueing optimization.
>
> Cancel elp_work on wakeup request, and add a new WL1271_FLAG_ELP_REQUESTED
> flag to further synchronize the elp actions.
>
> Signed-off-by: Eliad Peller <eliad@wizery.com>
> ---
Applied with a couple of changes in some comments. Thanks, Eliad, the
ELP man! :)
--
Cheers,
Luca.
prev parent reply other threads:[~2011-04-20 17:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-02 23:01 [PATCH] wl12xx: avoid premature elp entrance Eliad Peller
2011-04-20 17:44 ` Luciano Coelho [this message]
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=1303321453.1988.737.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