From: Kalle Valo <kvalo@codeaurora.org>
To: Rajat Jain <rajatja@google.com>
Cc: Amitkumar Karwar <akarwar@marvell.com>,
Nishant Sarmukadam <nishants@marvell.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
Rajat Jain <rajatja@google.com>,
Wei-Ning Huang <wnhuang@google.com>,
Brian Norris <briannorris@google.com>,
Eric Caruso <ejcaruso@chromium.org>,
rajatxjain@gmail.com
Subject: Re: [v3] mwifiex: report wakeup for wowlan
Date: Thu, 17 Nov 2016 06:41:20 +0000 (UTC) [thread overview]
Message-ID: <20161117064120.5925C61414@smtp.codeaurora.org> (raw)
In-Reply-To: <1475613462-93384-1-git-send-email-rajatja@google.com>
Rajat Jain <rajatja@google.com> wrote:
> Register the WLAN device as a wakeup source since it can
> wake the system via wake-on-wireless-lan. In an actual wowlan
> event, notify the PM core that we are the current wakeup source.
> This allows the PM core to update the wakeup attributes in /sys.
>
> This was causing wakeup issues on chromeos as the system was
> apparently confused about the wakeup source.
>
> Signed-off-by: Wei-Ning Huang <wnhuang@google.com>
> Signed-off-by: Rajat Jain <rajatja@google.com>
> Tested-by: Wei-Ning Huang <wnhuang@chromium.org>
> Reviewed-by: Eric Caruso <ejcaruso@chromium.org>
> Acked-by: Amitkumar Karwar <akarwar@marvell.com>
Patch applied to wireless-drivers-next.git, thanks.
df566a481ee8 mwifiex: report wakeup for wowlan
--
https://patchwork.kernel.org/patch/9362275/
Documentation about submitting wireless patches and checking status
from patchwork:
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2016-11-17 6:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-27 16:56 [PATCH] mwifiex: report wakeup for wowlan Rajat Jain
2016-09-28 1:41 ` Rajat Jain
2016-09-28 1:45 ` [PATCH v2] " Rajat Jain
2016-09-28 13:59 ` Amitkumar Karwar
2016-10-03 13:04 ` [v2] " Kalle Valo
[not found] ` <20161003130407.4D94161803@smtp.codeaurora.org>
2016-10-04 0:16 ` Rajat Jain
2016-10-04 12:46 ` Kalle Valo
2016-10-04 20:37 ` [PATCH v3] " Rajat Jain
2016-11-17 6:41 ` Kalle Valo [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=20161117064120.5925C61414@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=akarwar@marvell.com \
--cc=briannorris@google.com \
--cc=ejcaruso@chromium.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nishants@marvell.com \
--cc=rajatja@google.com \
--cc=rajatxjain@gmail.com \
--cc=wnhuang@google.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;
as well as URLs for NNTP newsgroup(s).