From: jeffy <jeffy.chen@rock-chips.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: Amitkumar Karwar <akarwar@marvell.com>,
Brian Norris <briannorris@chromium.org>,
Rajat Jain <rajatja@google.com>,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org,
Nishant Sarmukadam <nishants@marvell.com>
Subject: Re: [PATCH 3/3] mwifiex: wake system up when receives a wake irq
Date: Fri, 24 Feb 2017 20:20:55 +0800 [thread overview]
Message-ID: <58B02527.6090400@rock-chips.com> (raw)
In-Reply-To: <87d1e726p5.fsf@codeaurora.org>
Hi Kalle,
On 02/24/2017 07:01 PM, Kalle Valo wrote:
> Jeffy Chen <jeffy.chen@rock-chips.com> writes:
>
>> Currrently we are disabling this wake irq after receiving it. If this
>> happens before we finish suspend and the pm event check is disabled,
>> the system will continue suspending, and this irq would not work again.
>>
>> We may need to abort system suspend to avoid that.
>>
>> Signed-off-by: Jeffy Chen <jeffy.chen@rock-chips.com>
> I only see patch 3 in patchwork. Where are patches 1 and 2?
>
the other two are much like this one, but for bluetooth :)
please check:
https://patchwork.kernel.org/patch/9589455 New [1/3] btusb:
wake system up when receives a wake irq
https://patchwork.kernel.org/patch/9589453 New [2/3] btmrvl:
wake system up when receives a wake irq
https://patchwork.kernel.org/patch/9589457 New [3/3] mwifiex:
wake system up when receives a wake irq
(sorry, this is a resent mail, because the last one was rejected due to
wrong format)
next prev parent reply other threads:[~2017-02-24 12:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1487917471-5501-1-git-send-email-jeffy.chen@rock-chips.com>
2017-02-24 6:24 ` [PATCH 3/3] mwifiex: wake system up when receives a wake irq Jeffy Chen
2017-02-24 11:01 ` Kalle Valo
2017-02-24 12:20 ` jeffy [this message]
2017-03-20 16:44 ` [3/3] " Kalle Valo
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=58B02527.6090400@rock-chips.com \
--to=jeffy.chen@rock-chips.com \
--cc=akarwar@marvell.com \
--cc=briannorris@chromium.org \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nishants@marvell.com \
--cc=rajatja@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).